[OpenSIPS-Users] BLF lights on Linksys 942/962 get stuck in "off-hook" state
James Lamanna
jlamanna at gmail.com
Thu Aug 6 16:15:25 CEST 2009
Hi,
I've managed to get a SIP trace of what happens when the light gets stuck on.
Apparently opensips sends the "terminated" state correctly, but then
for some reason immediately follows it up with a "confirmed".
Any help would be greatly appreciated because this issue is preventing
me from moving to Opensips as a UA.
Here is the end of the call from xxxxxxxxx to yyyyyyyyyy (I've also
attached it as a text file):
open.sips.ip:5060 -> phone.nat.ip:1024
NOTIFY sip:xxxxxxxxxx at phone.nat.ip:1024 SIP/2.0..Via: SIP/2.0/UDP
open.sips.ip;branch=z9hG4bK47c6.54ba3b12.0..To:
<sip:xxxxxxxxxx at open.sips.ip>;tag=2bc2391ca644f0b4..From:
<sip:yyyyyyyyyy at 208
.90.184.6>;tag=89c56fdf6f5b6f30be24c8867d74b34a-50ee..CSeq: 135
NOTIFY..Call-ID: d3c20f3c-6cca1114 at 192.168.1.103..Content-Length:
577..User-Agent: OpenSIPS (1.5.2-notls (x86_64/linux))..Max-For
wards: 70..Event: dialog..Contact:
<sip:sa at open.sips.ip:5060>..Subscription-State:
active;expires=201..Content-Type: application/dialog-info+xml....<?xml
version="1.0"?>.<dialog-info xmlns="urn
:ietf:params:xml:ns:dialog-info" version="119" state="full"
entity="yyyyyyyyyy at open.sips.ip">. <dialog
id="6dc6f1db-3e4e1d75 at 192.168.1.103"
call-id="6dc6f1db-3e4e1d75 at 192.168.1.103" di
rection="recipient">. <state>confirmed</state>. <remote>.
<identity>sip:xxxxxxxxxx at open.sips.ip</identity>. <target
uri="sip:xxxxxxxxxx at open.sips.ip"/>. </remote>. <local>
. <identity>sip:yyyyyyyyyy at open.sips.ip</identity>.
<target uri="sip:yyyyyyyyyy at open.sips.ip"/>. </local>.
</dialog>.</dialog-info>.
#
U phone.nat.ip:1024 -> open.sips.ip:5060
SIP/2.0 200 OK..To:
<sip:xxxxxxxxxx at open.sips.ip>;tag=2bc2391ca644f0b4..From:
<sip:yyyyyyyyyy at open.sips.ip>;tag=89c56fdf6f5b6f30be24c8867d74b34a-50ee..Call-ID:
d3c20f3c-6cca1114 at 192.168.1.103..
CSeq: 133 NOTIFY..Via: SIP/2.0/UDP
open.sips.ip;branch=z9hG4bK67c6.d79cd0b1.0..Server:
Linksys/SPA962-6.1.5(a)..Content-Length: 0....
#
U phone.nat.ip:1024 -> open.sips.ip:5060
SIP/2.0 200 OK..To:
<sip:xxxxxxxxxx at open.sips.ip>;tag=2bc2391ca644f0b4..From:
<sip:yyyyyyyyyy at open.sips.ip>;tag=89c56fdf6f5b6f30be24c8867d74b34a-50ee..Call-ID:
d3c20f3c-6cca1114 at 192.168.1.103..
CSeq: 134 NOTIFY..Via: SIP/2.0/UDP
open.sips.ip;branch=z9hG4bK37c6.cebb6d83.0..Server:
Linksys/SPA962-6.1.5(a)..Content-Length: 0....
#
U phone.nat.ip:1024 -> open.sips.ip:5060
ACK sip:yyyyyyyyyy at 208.90.184.3:5060 SIP/2.0..Via: SIP/2.0/UDP
192.168.1.103:5060;branch=z9hG4bK-91d3e74f..From:
<sip:xxxxxxxxxx at open.sips.ip>;tag=d73256a35148bf4do0..To: ""
<sip:yyyyyyyyyy at open.sips.ip>;tag=as07ecc712..Call-ID:
6dc6f1db-3e4e1d75 at 192.168.1.103..CSeq: 102 ACK..Max-Forwards:
70..Route: <sip:open.sips.ip;lr=on;ftag=d73256a35148bf4do0;did=75e.7a38
ec43>..Proxy-Authorization: Digest
username="xxxxxxxxxx",realm="asterisk",nonce="0309612d",uri="sip:yyyyyyyyyy at open.sips.ip",algorithm=MD5,response="1ff12fede7922f355cfabb7ec82203c6"..Contact:
<sip:xxxxxxxxxx at 192.168.1.103:5060>..User-Agent:
Linksys/SPA962-6.1.5(a)..Content-Length: 0....
#
U open.sips.ip:5060 -> phone.nat.ip:1024
NOTIFY sip:xxxxxxxxxx at phone.nat.ip:1024 SIP/2.0..Via: SIP/2.0/UDP
open.sips.ip;branch=z9hG4bK17c6.c007f975.0..To:
<sip:xxxxxxxxxx at open.sips.ip>;tag=2bc2391ca644f0b4..From:
<sip:yyyyyyyyyy at 208
.90.184.6>;tag=89c56fdf6f5b6f30be24c8867d74b34a-50ee..CSeq: 136
NOTIFY..Call-ID: d3c20f3c-6cca1114 at 192.168.1.103..Content-Length:
577..User-Agent: OpenSIPS (1.5.2-notls (x86_64/linux))..Max-For
wards: 70..Event: dialog..Contact:
<sip:sa at open.sips.ip:5060>..Subscription-State:
active;expires=201..Content-Type: application/dialog-info+xml....<?xml
version="1.0"?>.<dialog-info xmlns="urn
:ietf:params:xml:ns:dialog-info" version="120" state="full"
entity="yyyyyyyyyy at open.sips.ip">. <dialog
id="6dc6f1db-3e4e1d75 at 192.168.1.103"
call-id="6dc6f1db-3e4e1d75 at 192.168.1.103" di
rection="recipient">. <state>confirmed</state>. <remote>.
<identity>sip:xxxxxxxxxx at open.sips.ip</identity>. <target
uri="sip:xxxxxxxxxx at open.sips.ip"/>. </remote>. <local>
. <identity>sip:yyyyyyyyyy at open.sips.ip</identity>.
<target uri="sip:yyyyyyyyyy at open.sips.ip"/>. </local>.
</dialog>.</dialog-info>.
#
U phone.nat.ip:1024 -> open.sips.ip:5060
SIP/2.0 200 OK..To:
<sip:xxxxxxxxxx at open.sips.ip>;tag=2bc2391ca644f0b4..From:
<sip:yyyyyyyyyy at open.sips.ip>;tag=89c56fdf6f5b6f30be24c8867d74b34a-50ee..Call-ID:
d3c20f3c-6cca1114 at 192.168.1.103..
CSeq: 135 NOTIFY..Via: SIP/2.0/UDP
open.sips.ip;branch=z9hG4bK47c6.54ba3b12.0..Server:
Linksys/SPA962-6.1.5(a)..Content-Length: 0....
#
U phone.nat.ip:1024 -> open.sips.ip:5060
SIP/2.0 200 OK..To:
<sip:xxxxxxxxxx at open.sips.ip>;tag=2bc2391ca644f0b4..From:
<sip:yyyyyyyyyy at open.sips.ip>;tag=89c56fdf6f5b6f30be24c8867d74b34a-50ee..Call-ID:
d3c20f3c-6cca1114 at 192.168.1.103..
CSeq: 136 NOTIFY..Via: SIP/2.0/UDP
open.sips.ip;branch=z9hG4bK17c6.c007f975.0..Server:
Linksys/SPA962-6.1.5(a)..Content-Length: 0....
#
U phone.nat.ip:5060 -> open.sips.ip:5060
BYE sip:xxxxxxxxxx at 208.90.184.3 SIP/2.0..Via: SIP/2.0/UDP
192.168.1.100;rport;branch=z9hG4bKc0a80164000001474a7ae2c03ea459e400000300..Content-Length:
0..Call-ID: 42c13197719b598a2929f377272812f
b at 208.90.184.3..CSeq: 1 BYE..From:
"unknown"<sip:yyyyyyyyyy at open.sips.ip>;tag=4026907261829170..Max-Forwards:
70..Route: <sip:open.sips.ip;lr=on;ftag=as4d72f491;did=7b3.68605493>..To:
<sip:9498
923388 at 208.90.184.3>;tag=as4d72f491..User-Agent: SJphone/1.60.299a/L
(SJ Labs)....
#
U open.sips.ip:5060 -> phone.nat.ip:5060
SIP/2.0 200 OK..Via: SIP/2.0/UDP
192.168.1.100;received=phone.nat.ip;rport=5060;branch=z9hG4bKc0a80164000001474a7ae2c03ea459e400000300..From:
"unknown"<sip:yyyyyyyyyy at open.sips.ip>;tag=402690
7261829170..To:
<sip:xxxxxxxxxx at 208.90.184.3>;tag=as4d72f491..Call-ID:
42c13197719b598a2929f377272812fb at 208.90.184.3..CSeq: 1
BYE..User-Agent: Asterisk PBX..Allow: INVITE, ACK, CANCEL, OPTIONS,
BYE, REFER, SUBSCRIBE, NOTIFY..Supported: replaces..Contact:
<sip:xxxxxxxxxx at 208.90.184.3:5060>..Content-Length: 0....
U open.sips.ip:5060 -> phone.nat.ip:1024
NOTIFY sip:xxxxxxxxxx at phone.nat.ip:1024 SIP/2.0..Via: SIP/2.0/UDP
open.sips.ip;branch=z9hG4bK27c6.1b56a874.0..To:
<sip:xxxxxxxxxx at open.sips.ip>;tag=2bc2391ca644f0b4..From:
<sip:yyyyyyyyyy at 208
.90.184.6>;tag=89c56fdf6f5b6f30be24c8867d74b34a-50ee..CSeq: 137
NOTIFY..Call-ID: d3c20f3c-6cca1114 at 192.168.1.103..Content-Length:
616..User-Agent: OpenSIPS (1.5.2-notls (x86_64/linux))..Max-For
wards: 70..Event: dialog..Contact:
<sip:sa at open.sips.ip:5060>..Subscription-State:
active;expires=200..Content-Type: application/dialog-info+xml....<?xml
version="1.0"?>.<dialog-info xmlns="urn
:ietf:params:xml:ns:dialog-info" version="121" state="full"
entity="yyyyyyyyyy at open.sips.ip">. <dialog
id="E65465A8-1DD1-11B2-AF7D-CB1F690F2247 at 192.168.1.100"
call-id="E65465A8-1DD1-11
B2-AF7D-CB1F690F2247 at 192.168.1.100" direction="initiator">.
<state>terminated</state>. <remote>.
<identity>sip:xxxxxxxxxx at open.sips.ip</identity>. <target
uri="sip:xxxxxxxxxx at 20
8.90.184.6"/>. </remote>. <local>.
<identity>sip:yyyyyyyyyy at open.sips.ip</identity>. <target
uri="sip:yyyyyyyyyy at open.sips.ip"/>. </local>.
</dialog>.</dialog-info>.
#
U open.sips.ip:5060 -> phone.nat.ip:1024
NOTIFY sip:xxxxxxxxxx at phone.nat.ip:1024 SIP/2.0..Via: SIP/2.0/UDP
open.sips.ip;branch=z9hG4bK08c6.b93e7173.0..To:
<sip:xxxxxxxxxx at open.sips.ip>;tag=2bc2391ca644f0b4..From:
<sip:yyyyyyyyyy at 208
.90.184.6>;tag=89c56fdf6f5b6f30be24c8867d74b34a-50ee..CSeq: 138
NOTIFY..Call-ID: d3c20f3c-6cca1114 at 192.168.1.103..Content-Length:
577..User-Agent: OpenSIPS (1.5.2-notls (x86_64/linux))..Max-For
wards: 70..Event: dialog..Contact:
<sip:sa at open.sips.ip:5060>..Subscription-State:
active;expires=200..Content-Type: application/dialog-info+xml....<?xml
version="1.0"?>.<dialog-info xmlns="urn
:ietf:params:xml:ns:dialog-info" version="121" state="full"
entity="yyyyyyyyyy at open.sips.ip">. <dialog
id="6dc6f1db-3e4e1d75 at 192.168.1.103"
call-id="6dc6f1db-3e4e1d75 at 192.168.1.103" di
rection="recipient">. <state>confirmed</state>. <remote>.
<identity>sip:xxxxxxxxxx at open.sips.ip</identity>. <target
uri="sip:xxxxxxxxxx at open.sips.ip"/>. </remote>. <local>
. <identity>sip:yyyyyyyyyy at open.sips.ip</identity>.
<target uri="sip:yyyyyyyyyy at open.sips.ip"/>. </local>.
</dialog>.</dialog-info>.
#
U phone.nat.ip:1024 -> open.sips.ip:5060
SIP/2.0 200 OK..To:
<sip:xxxxxxxxxx at open.sips.ip>;tag=d73256a35148bf4do0..From: ""
<sip:yyyyyyyyyy at open.sips.ip>;tag=as07ecc712..Call-ID:
6dc6f1db-3e4e1d75 at 192.168.1.103
..CSeq: 102 BYE..Via: SIP/2.0/UDP
open.sips.ip;branch=z9hG4bKff24.832383a.0..Via: SIP/2.0/UDP
208.90.184.3:5060;received=208.90.184.3;branch=z9hG4bK3baecd2f;rport=5060..Server:
Linksys/SPA962-6
.1.5(a)..Content-Length: 0....
#
U phone.nat.ip:1024 -> open.sips.ip:5060
SIP/2.0 200 OK..To:
<sip:xxxxxxxxxx at open.sips.ip>;tag=2bc2391ca644f0b4..From:
<sip:yyyyyyyyyy at open.sips.ip>;tag=89c56fdf6f5b6f30be24c8867d74b34a-50ee..Call-ID:
d3c20f3c-6cca1114 at 192.168.1.103..
CSeq: 137 NOTIFY..Via: SIP/2.0/UDP
open.sips.ip;branch=z9hG4bK27c6.1b56a874.0..Server:
Linksys/SPA962-6.1.5(a)..Content-Length: 0....
#
U phone.nat.ip:1024 -> open.sips.ip:5060
SIP/2.0 200 OK..To:
<sip:xxxxxxxxxx at open.sips.ip>;tag=2bc2391ca644f0b4..From:
<sip:yyyyyyyyyy at open.sips.ip>;tag=89c56fdf6f5b6f30be24c8867d74b34a-50ee..Call-ID:
d3c20f3c-6cca1114 at 192.168.1.103..
CSeq: 138 NOTIFY..Via: SIP/2.0/UDP
open.sips.ip;branch=z9hG4bK08c6.b93e7173.0..Server:
Linksys/SPA962-6.1.5(a)..Content-Length: 0....
On Mon, Aug 3, 2009 at 10:59 AM, James Lamanna<jlamanna at gmail.com> wrote:
> Hi Anca,
> I tried the latest trunk of Opensips and presence seems to be
> completely broken for my Linksys phones.
> The lights now flash orange, which I believe means that they are not subscribed.
> I will say I have to have the ServerType on the phone set to
> "Asterisk" because I have parking
> lines that still need the BLF directly from the Asterisk server.
>
> And as an aside, does anyone know if Asterisk 1.6 implements RFC4235 correctly?
>
> Thanks.
>
> -- James
>
> On Tue, Jul 28, 2009 at 10:53 AM, James Lamanna<jlamanna at gmail.com> wrote:
>> I am using 1.5.2
>>
>> --James
>>
>> On Jul 28, 2009, at 1:48, Anca Vamanu <anca at opensips.org> wrote:
>>
>>> Hi James,
>>>
>>> What OpenSIPS version are you using?
>>>
>>> Anca
>>>
>>> James Lamanna wrote:
>>>>
>>>> Hi,
>>>> I have some SPA942 and 962 phones that I'm trying to get BLF to work
>>>> properly with.
>>>> I've found it works correctly most of the time, however on occasion,
>>>> the BLF lights will get stuck as RED
>>>> (someone on a call) even though that person has hung up.
>>>>
>>>> Relevant parts of config:
>>>>
>>>> modparam("presence", "server_address", "sip:sa at xxx.xxx.xxx.xxx:5060")
>>>> modparam("presence", "expires_offset", 10)
>>>> modparam("presence_xml", "force_active", 1)
>>>>
>>>> modparam("presence_dialoginfo", "force_single_dialog", 1)
>>>> modparam("pua_dialoginfo", "presence_server",
>>>> "sip:sa at xxx.xxx.xxx.xxx:5060")
>>>> modparam("pua_dialoginfo", "include_callid", 1)
>>>> modparam("pua_dialoginfo", "include_tags", 1)
>>>> modparam("pua_dialoginfo", "caller_confirmed", 1)
>>>>
>>>> modparam("pua_usrloc", "default_domain", "xxx.xxx.xxx.xxx")
>>>> modparam("pua_usrloc", "presence_server", "sip:sa at xxx.xxx.xxx.xxx:5060")
>>>>
>>>> ...
>>>>
>>>> if(is_method("PUBLISH")) {
>>>> if ($hdr(Sender) != NULL)
>>>> handle_publish("$hdr(Sender)");
>>>> else
>>>> handle_publish();
>>>> }
>>>> else if( is_method("SUBSCRIBE")) {
>>>> handle_subscribe();
>>>> }
>>>>
>>>> ....
>>>>
>>>> Thanks.
>>>>
>>>> -- James
>>>>
>>>> _______________________________________________
>>>> Users mailing list
>>>> Users at lists.opensips.org
>>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>>
>>>>
>>>
>>
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: broken_blfs.log
Type: application/octet-stream
Size: 10749 bytes
Desc: not available
Url : http://lists.opensips.org/pipermail/users/attachments/20090806/505ad52a/attachment-0001.obj
More information about the Users
mailing list