On Thu, Aug 6, 2009 at 7:27 AM, Anca Vamanu<[email protected]> wrote: > Hi James, > > I have made a fixed in pua that should fix this problem. It is both in 1.5.x > baranch and trunk. Please update and test now.
Thanks! I will start testing this and let you know what I find right away. -- James > > regards, > Anca > > James Lamanna wrote: >> >> 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:[email protected]:1024 SIP/2.0..Via: SIP/2.0/UDP >> open.sips.ip;branch=z9hG4bK47c6.54ba3b12.0..To: >> <sip:[email protected]>;tag=2bc2391ca644f0b4..From: >> <sip:yyyyyyy...@208 >> .90.184.6>;tag=89c56fdf6f5b6f30be24c8867d74b34a-50ee..CSeq: 135 >> NOTIFY..Call-ID: [email protected]: >> 577..User-Agent: OpenSIPS (1.5.2-notls (x86_64/linux))..Max-For >> wards: 70..Event: dialog..Contact: >> <sip:[email protected]: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="[email protected]">. <dialog >> id="[email protected]" >> call-id="[email protected]" di >> rection="recipient">. <state>confirmed</state>. <remote>. >> <identity>sip:[email protected]</identity>. <target >> uri="sip:[email protected]"/>. </remote>. <local> >> . <identity>sip:[email protected]</identity>. >> <target uri="sip:[email protected]"/>. </local>. >> </dialog>.</dialog-info>. >> # >> U phone.nat.ip:1024 -> open.sips.ip:5060 >> SIP/2.0 200 OK..To: >> <sip:[email protected]>;tag=2bc2391ca644f0b4..From: >> >> <sip:[email protected]>;tag=89c56fdf6f5b6f30be24c8867d74b34a-50ee..Call-ID: >> [email protected].. >> 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:[email protected]>;tag=2bc2391ca644f0b4..From: >> >> <sip:[email protected]>;tag=89c56fdf6f5b6f30be24c8867d74b34a-50ee..Call-ID: >> [email protected].. >> 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:[email protected]:5060 SIP/2.0..Via: SIP/2.0/UDP >> 192.168.1.103:5060;branch=z9hG4bK-91d3e74f..From: >> <sip:[email protected]>;tag=d73256a35148bf4do0..To: "" >> <sip:[email protected]>;tag=as07ecc712..Call-ID: >> [email protected]: 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:[email protected]",algorithm=MD5,response="1ff12fede7922f355cfabb7ec82203c6"..Contact: >> <sip:[email protected]:5060>..User-Agent: >> Linksys/SPA962-6.1.5(a)..Content-Length: 0.... >> # >> U open.sips.ip:5060 -> phone.nat.ip:1024 >> NOTIFY sip:[email protected]:1024 SIP/2.0..Via: SIP/2.0/UDP >> open.sips.ip;branch=z9hG4bK17c6.c007f975.0..To: >> <sip:[email protected]>;tag=2bc2391ca644f0b4..From: >> <sip:yyyyyyy...@208 >> .90.184.6>;tag=89c56fdf6f5b6f30be24c8867d74b34a-50ee..CSeq: 136 >> NOTIFY..Call-ID: [email protected]: >> 577..User-Agent: OpenSIPS (1.5.2-notls (x86_64/linux))..Max-For >> wards: 70..Event: dialog..Contact: >> <sip:[email protected]: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="[email protected]">. <dialog >> id="[email protected]" >> call-id="[email protected]" di >> rection="recipient">. <state>confirmed</state>. <remote>. >> <identity>sip:[email protected]</identity>. <target >> uri="sip:[email protected]"/>. </remote>. <local> >> . <identity>sip:[email protected]</identity>. >> <target uri="sip:[email protected]"/>. </local>. >> </dialog>.</dialog-info>. >> # >> U phone.nat.ip:1024 -> open.sips.ip:5060 >> SIP/2.0 200 OK..To: >> <sip:[email protected]>;tag=2bc2391ca644f0b4..From: >> >> <sip:[email protected]>;tag=89c56fdf6f5b6f30be24c8867d74b34a-50ee..Call-ID: >> [email protected].. >> 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:[email protected]>;tag=2bc2391ca644f0b4..From: >> >> <sip:[email protected]>;tag=89c56fdf6f5b6f30be24c8867d74b34a-50ee..Call-ID: >> [email protected].. >> 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:[email protected] SIP/2.0..Via: SIP/2.0/UDP >> >> 192.168.1.100;rport;branch=z9hG4bKc0a80164000001474a7ae2c03ea459e400000300..Content-Length: >> 0..Call-ID: 42c13197719b598a2929f377272812f >> �[email protected]: 1 BYE..From: >> "unknown"<sip:[email protected]>;tag=4026907261829170..Max-Forwards: >> 70..Route: <sip:open.sips.ip;lr=on;ftag=as4d72f491;did=7b3.68605493>..To: >> <sip:9498 >> [email protected]>;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:[email protected]>;tag=402690 >> 7261829170..To: >> <sip:[email protected]>;tag=as4d72f491..Call-ID: >> [email protected]: 1 >> BYE..User-Agent: Asterisk PBX..Allow: INVITE, ACK, CANCEL, OPTIONS, >> BYE, REFER, SUBSCRIBE, NOTIFY..Supported: replaces..Contact: >> <sip:[email protected]:5060>..Content-Length: 0.... >> U open.sips.ip:5060 -> phone.nat.ip:1024 >> NOTIFY sip:[email protected]:1024 SIP/2.0..Via: SIP/2.0/UDP >> open.sips.ip;branch=z9hG4bK27c6.1b56a874.0..To: >> <sip:[email protected]>;tag=2bc2391ca644f0b4..From: >> <sip:yyyyyyy...@208 >> .90.184.6>;tag=89c56fdf6f5b6f30be24c8867d74b34a-50ee..CSeq: 137 >> NOTIFY..Call-ID: [email protected]: >> 616..User-Agent: OpenSIPS (1.5.2-notls (x86_64/linux))..Max-For >> wards: 70..Event: dialog..Contact: >> <sip:[email protected]: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="[email protected]">. <dialog >> id="[email protected]" >> call-id="E65465A8-1DD1-11 >> [email protected]" direction="initiator">. >> <state>terminated</state>. <remote>. >> <identity>sip:[email protected]</identity>. <target >> uri="sip:xxxxxxx...@20 >> 8.90.184.6"/>. </remote>. <local>. >> <identity>sip:[email protected]</identity>. <target >> uri="sip:[email protected]"/>. </local>. >> </dialog>.</dialog-info>. >> # >> U open.sips.ip:5060 -> phone.nat.ip:1024 >> NOTIFY sip:[email protected]:1024 SIP/2.0..Via: SIP/2.0/UDP >> open.sips.ip;branch=z9hG4bK08c6.b93e7173.0..To: >> <sip:[email protected]>;tag=2bc2391ca644f0b4..From: >> <sip:yyyyyyy...@208 >> .90.184.6>;tag=89c56fdf6f5b6f30be24c8867d74b34a-50ee..CSeq: 138 >> NOTIFY..Call-ID: [email protected]: >> 577..User-Agent: OpenSIPS (1.5.2-notls (x86_64/linux))..Max-For >> wards: 70..Event: dialog..Contact: >> <sip:[email protected]: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="[email protected]">. <dialog >> id="[email protected]" >> call-id="[email protected]" di >> rection="recipient">. <state>confirmed</state>. <remote>. >> <identity>sip:[email protected]</identity>. <target >> uri="sip:[email protected]"/>. </remote>. <local> >> . <identity>sip:[email protected]</identity>. >> <target uri="sip:[email protected]"/>. </local>. >> </dialog>.</dialog-info>. >> # >> U phone.nat.ip:1024 -> open.sips.ip:5060 >> SIP/2.0 200 OK..To: >> <sip:[email protected]>;tag=d73256a35148bf4do0..From: "" >> <sip:[email protected]>;tag=as07ecc712..Call-ID: >> [email protected] >> ..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:[email protected]>;tag=2bc2391ca644f0b4..From: >> >> <sip:[email protected]>;tag=89c56fdf6f5b6f30be24c8867d74b34a-50ee..Call-ID: >> [email protected].. >> 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:[email protected]>;tag=2bc2391ca644f0b4..From: >> >> <sip:[email protected]>;tag=89c56fdf6f5b6f30be24c8867d74b34a-50ee..Call-ID: >> [email protected].. >> 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<[email protected]> 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<[email protected]> >>> wrote: >>> >>>> >>>> I am using 1.5.2 >>>> >>>> --James >>>> >>>> On Jul 28, 2009, at 1:48, Anca Vamanu <[email protected]> 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:[email protected]: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:[email protected]: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:[email protected]: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 >>>>>> [email protected] >>>>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >>>>>> >>>>>> >>>>>> > > _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
