Re: [OpenSIPS-Users] BLF lights on Linksys 942/962 get stuck in "off-hook" state
On Thu, Aug 6, 2009 at 7:27 AM, Anca Vamanu 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 x to yy (I've also >> attached it as a text file): >> >> open.sips.ip:5060 -> phone.nat.ip:1024 >> NOTIFY sip:xxx...@phone.nat.ip:1024 SIP/2.0..Via: SIP/2.0/UDP >> open.sips.ip;branch=z9hG4bK47c6.54ba3b12.0..To: >> ;tag=2bc2391ca644f0b4..From: >> > .90.184.6>;tag=89c56fdf6f5b6f30be24c8867d74b34a-50ee..CSeq: 135 >> NOTIFY..Call-ID: d3c20f3c-6cca1...@192.168.1.103..content-length: >> 577..User-Agent: OpenSIPS (1.5.2-notls (x86_64/linux))..Max-For >> wards: 70..Event: dialog..Contact: >> ..Subscription-State: >> active;expires=201..Content-Type: application/dialog-info+xml> version="1.0"?>.> entity="yyy...@open.sips.ip">. > id="6dc6f1db-3e4e1...@192.168.1.103" >> call-id="6dc6f1db-3e4e1...@192.168.1.103" di >> rection="recipient">. confirmed. . >> sip:xxx...@open.sips.ip. > uri="sip:xxx...@open.sips.ip"/>. . >> . sip:yyy...@open.sips.ip. >> . . >> .. >> # >> U phone.nat.ip:1024 -> open.sips.ip:5060 >> SIP/2.0 200 OK..To: >> ;tag=2bc2391ca644f0b4..From: >> >> ;tag=89c56fdf6f5b6f30be24c8867d74b34a-50ee..Call-ID: >> d3c20f3c-6cca1...@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: >> ;tag=2bc2391ca644f0b4..From: >> >> ;tag=89c56fdf6f5b6f30be24c8867d74b34a-50ee..Call-ID: >> d3c20f3c-6cca1...@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:yyy...@208.90.184.3:5060 SIP/2.0..Via: SIP/2.0/UDP >> 192.168.1.103:5060;branch=z9hG4bK-91d3e74f..From: >> ;tag=d73256a35148bf4do0..To: "" >> ;tag=as07ecc712..Call-ID: >> 6dc6f1db-3e4e1...@192.168.1.103..cseq: 102 ACK..Max-Forwards: >> 70..Route: > ec43>..Proxy-Authorization: Digest >> >> username="xx",realm="asterisk",nonce="0309612d",uri="sip:yyy...@open.sips.ip",algorithm=MD5,response="1ff12fede7922f355cfabb7ec82203c6"..Contact: >> ..User-Agent: >> Linksys/SPA962-6.1.5(a)..Content-Length: 0 >> # >> U open.sips.ip:5060 -> phone.nat.ip:1024 >> NOTIFY sip:xxx...@phone.nat.ip:1024 SIP/2.0..Via: SIP/2.0/UDP >> open.sips.ip;branch=z9hG4bK17c6.c007f975.0..To: >> ;tag=2bc2391ca644f0b4..From: >> > .90.184.6>;tag=89c56fdf6f5b6f30be24c8867d74b34a-50ee..CSeq: 136 >> NOTIFY..Call-ID: d3c20f3c-6cca1...@192.168.1.103..content-length: >> 577..User-Agent: OpenSIPS (1.5.2-notls (x86_64/linux))..Max-For >> wards: 70..Event: dialog..Contact: >> ..Subscription-State: >> active;expires=201..Content-Type: application/dialog-info+xml> version="1.0"?>.> entity="yyy...@open.sips.ip">. > id="6dc6f1db-3e4e1...@192.168.1.103" >> call-id="6dc6f1db-3e4e1...@192.168.1.103" di >> rection="recipient">. confirmed. . >> sip:xxx...@open.sips.ip. > uri="sip:xxx...@open.sips.ip"/>. . >> . sip:yyy...@open.sips.ip. >> . . >> .. >> # >> U phone.nat.ip:1024 -> open.sips.ip:5060 >> SIP/2.0 200 OK..To: >> ;tag=2bc2391ca644f0b4..From: >> >> ;tag=89c56fdf6f5b6f30be24c8867d74b34a-50ee..Call-ID: >> d3c20f3c-6cca1...@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: >> ;tag=2bc2391ca644f0b4..From: >> >> ;tag=89c56fdf6f5b6f30be24c8867d74b34a-50ee..Call-ID: >> d3c20f3c-6cca1...@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:xxx...@208.90.184.3 SIP/2.0..Via: SIP/2.0/UDP >> >> 192.168.1.100;rport;branch=z9hG4bKc0a8016401474a7ae2c03ea459e40300..Content-Length: >> 0..Call-ID: 42c13197719b598a2929f377272812f >> �...@208.90.184.3..cseq: 1 BYE..From: >> "unknown";tag=4026907261829170..Max-Forwards: >> 70..Route: ..To: >> > 923...@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
Re: [OpenSIPS-Users] BLF lights on Linksys 942/962 get stuck in "off-hook" state
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. 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 x to yy (I've also > attached it as a text file): > > open.sips.ip:5060 -> phone.nat.ip:1024 > NOTIFY sip:xxx...@phone.nat.ip:1024 SIP/2.0..Via: SIP/2.0/UDP > open.sips.ip;branch=z9hG4bK47c6.54ba3b12.0..To: > ;tag=2bc2391ca644f0b4..From: >.90.184.6>;tag=89c56fdf6f5b6f30be24c8867d74b34a-50ee..CSeq: 135 > NOTIFY..Call-ID: d3c20f3c-6cca1...@192.168.1.103..content-length: > 577..User-Agent: OpenSIPS (1.5.2-notls (x86_64/linux))..Max-For > wards: 70..Event: dialog..Contact: > ..Subscription-State: > active;expires=201..Content-Type: application/dialog-info+xml version="1.0"?>. entity="yyy...@open.sips.ip">. id="6dc6f1db-3e4e1...@192.168.1.103" > call-id="6dc6f1db-3e4e1...@192.168.1.103" di > rection="recipient">.confirmed.. > sip:xxx...@open.sips.ip. uri="sip:xxx...@open.sips.ip"/>.. > . sip:yyy...@open.sips.ip. > .. > .. > # > U phone.nat.ip:1024 -> open.sips.ip:5060 > SIP/2.0 200 OK..To: > ;tag=2bc2391ca644f0b4..From: > ;tag=89c56fdf6f5b6f30be24c8867d74b34a-50ee..Call-ID: > d3c20f3c-6cca1...@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: > ;tag=2bc2391ca644f0b4..From: > ;tag=89c56fdf6f5b6f30be24c8867d74b34a-50ee..Call-ID: > d3c20f3c-6cca1...@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:yyy...@208.90.184.3:5060 SIP/2.0..Via: SIP/2.0/UDP > 192.168.1.103:5060;branch=z9hG4bK-91d3e74f..From: > ;tag=d73256a35148bf4do0..To: "" > ;tag=as07ecc712..Call-ID: > 6dc6f1db-3e4e1...@192.168.1.103..cseq: 102 ACK..Max-Forwards: > 70..Route:ec43>..Proxy-Authorization: Digest > username="xx",realm="asterisk",nonce="0309612d",uri="sip:yyy...@open.sips.ip",algorithm=MD5,response="1ff12fede7922f355cfabb7ec82203c6"..Contact: > ..User-Agent: > Linksys/SPA962-6.1.5(a)..Content-Length: 0 > # > U open.sips.ip:5060 -> phone.nat.ip:1024 > NOTIFY sip:xxx...@phone.nat.ip:1024 SIP/2.0..Via: SIP/2.0/UDP > open.sips.ip;branch=z9hG4bK17c6.c007f975.0..To: > ;tag=2bc2391ca644f0b4..From: >.90.184.6>;tag=89c56fdf6f5b6f30be24c8867d74b34a-50ee..CSeq: 136 > NOTIFY..Call-ID: d3c20f3c-6cca1...@192.168.1.103..content-length: > 577..User-Agent: OpenSIPS (1.5.2-notls (x86_64/linux))..Max-For > wards: 70..Event: dialog..Contact: > ..Subscription-State: > active;expires=201..Content-Type: application/dialog-info+xml version="1.0"?>. entity="yyy...@open.sips.ip">. id="6dc6f1db-3e4e1...@192.168.1.103" > call-id="6dc6f1db-3e4e1...@192.168.1.103" di > rection="recipient">.confirmed.. > sip:xxx...@open.sips.ip. uri="sip:xxx...@open.sips.ip"/>.. > . sip:yyy...@open.sips.ip. > .. > .. > # > U phone.nat.ip:1024 -> open.sips.ip:5060 > SIP/2.0 200 OK..To: > ;tag=2bc2391ca644f0b4..From: > ;tag=89c56fdf6f5b6f30be24c8867d74b34a-50ee..Call-ID: > d3c20f3c-6cca1...@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: > ;tag=2bc2391ca644f0b4..From: > ;tag=89c56fdf6f5b6f30be24c8867d74b34a-50ee..Call-ID: > d3c20f3c-6cca1...@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:xxx...@208.90.184.3 SIP/2.0..Via: SIP/2.0/UDP > 192.168.1.100;rport;branch=z9hG4bKc0a8016401474a7ae2c03ea459e40300..Content-Length: > 0..Call-ID: 42c13197719b598a2929f377272812f > b...@208.90.184.3..cseq: 1 BYE..From: > "unknown";tag=4026907261829170..Max-Forwards: > 70..Route: ..To: >923...@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=z9hG4bKc0a8016401474a7ae2c03ea459e40300..From: > "unknown";tag=402690 > 7261829170..To: > ;tag=as4d72f491..Call-ID: > 42c13197719b598a2929f37727281...@208.90.184.3..cseq: 1 > BYE
Re: [OpenSIPS-Users] BLF lights on Linksys 942/962 get stuck in "off-hook" state
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 x to yy (I've also attached it as a text file): open.sips.ip:5060 -> phone.nat.ip:1024 NOTIFY sip:xxx...@phone.nat.ip:1024 SIP/2.0..Via: SIP/2.0/UDP open.sips.ip;branch=z9hG4bK47c6.54ba3b12.0..To: ;tag=2bc2391ca644f0b4..From: ;tag=89c56fdf6f5b6f30be24c8867d74b34a-50ee..CSeq: 135 NOTIFY..Call-ID: d3c20f3c-6cca1...@192.168.1.103..content-length: 577..User-Agent: OpenSIPS (1.5.2-notls (x86_64/linux))..Max-For wards: 70..Event: dialog..Contact: ..Subscription-State: active;expires=201..Content-Type: application/dialog-info+xml.. .confirmed.. sip:xxx...@open.sips.ip. .. . sip:yyy...@open.sips.ip. .. .. # U phone.nat.ip:1024 -> open.sips.ip:5060 SIP/2.0 200 OK..To: ;tag=2bc2391ca644f0b4..From: ;tag=89c56fdf6f5b6f30be24c8867d74b34a-50ee..Call-ID: d3c20f3c-6cca1...@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: ;tag=2bc2391ca644f0b4..From: ;tag=89c56fdf6f5b6f30be24c8867d74b34a-50ee..Call-ID: d3c20f3c-6cca1...@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:yyy...@208.90.184.3:5060 SIP/2.0..Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK-91d3e74f..From: ;tag=d73256a35148bf4do0..To: "" ;tag=as07ecc712..Call-ID: 6dc6f1db-3e4e1...@192.168.1.103..cseq: 102 ACK..Max-Forwards: 70..Route: ..Proxy-Authorization: Digest username="xx",realm="asterisk",nonce="0309612d",uri="sip:yyy...@open.sips.ip",algorithm=MD5,response="1ff12fede7922f355cfabb7ec82203c6"..Contact: ..User-Agent: Linksys/SPA962-6.1.5(a)..Content-Length: 0 # U open.sips.ip:5060 -> phone.nat.ip:1024 NOTIFY sip:xxx...@phone.nat.ip:1024 SIP/2.0..Via: SIP/2.0/UDP open.sips.ip;branch=z9hG4bK17c6.c007f975.0..To: ;tag=2bc2391ca644f0b4..From: ;tag=89c56fdf6f5b6f30be24c8867d74b34a-50ee..CSeq: 136 NOTIFY..Call-ID: d3c20f3c-6cca1...@192.168.1.103..content-length: 577..User-Agent: OpenSIPS (1.5.2-notls (x86_64/linux))..Max-For wards: 70..Event: dialog..Contact: ..Subscription-State: active;expires=201..Content-Type: application/dialog-info+xml.. .confirmed.. sip:xxx...@open.sips.ip. .. . sip:yyy...@open.sips.ip. .. .. # U phone.nat.ip:1024 -> open.sips.ip:5060 SIP/2.0 200 OK..To: ;tag=2bc2391ca644f0b4..From: ;tag=89c56fdf6f5b6f30be24c8867d74b34a-50ee..Call-ID: d3c20f3c-6cca1...@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: ;tag=2bc2391ca644f0b4..From: ;tag=89c56fdf6f5b6f30be24c8867d74b34a-50ee..Call-ID: d3c20f3c-6cca1...@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:xxx...@208.90.184.3 SIP/2.0..Via: SIP/2.0/UDP 192.168.1.100;rport;branch=z9hG4bKc0a8016401474a7ae2c03ea459e40300..Content-Length: 0..Call-ID: 42c13197719b598a2929f377272812f b...@208.90.184.3..cseq: 1 BYE..From: "unknown";tag=4026907261829170..Max-Forwards: 70..Route: ..To: ;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=z9hG4bKc0a8016401474a7ae2c03ea459e40300..From: "unknown";tag=402690 7261829170..To: ;tag=as4d72f491..Call-ID: 42c13197719b598a2929f37727281...@208.90.184.3..cseq: 1 BYE..User-Agent: Asterisk PBX..Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY..Supported: replaces..Contact: ..Content-Length: 0 U open.sips.ip:5060 -> phone.nat.ip:1024 NOTIFY sip:xxx...@phone.nat.ip:1024 SIP/2.0..Via: SIP/2.0/UDP open.sips.ip;branch=z9hG4bK27c6.1b56a874.0..To: ;tag=2bc2391ca644f0b4..From: ;tag=89c56fdf6f5b6f30be24c8867d74b34a-50ee..CSeq: 137 NOTIFY..Call-ID: d3c20f3c-6cca1...@192.168.1.103..content-length: 616..User-Agent: OpenSIPS (1.5.2-notls (x86_64/linux))..Max-For wards: 70..Event: dialog..Contact: ..Subscription-State: active;expires=200..Content-Type: application/dialog-info+xml.. . terminated.. sip:xxx...@open.sips.ip. ... sip:yyy...@open.sips.ip. .. .. # U open.sips.ip:5060 -> phone.nat.ip:1024 NOTIFY sip:xxx...@ph
Re: [OpenSIPS-Users] BLF lights on Linksys 942/962 get stuck in "off-hook" state
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 wrote:
> I am using 1.5.2
>
> --James
>
> On Jul 28, 2009, at 1:48, Anca Vamanu 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:s...@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:s...@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:s...@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@lists.opensips.org
>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>
>>>
>>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] BLF lights on Linksys 942/962 get stuck in "off-hook" state
Hi Piotr and James,
I have just committed a fix in trunk. Could you please update and test?
If everything is ok I will port the change in 1.5 branch.
regards,
Anca
Piotr Sobolewski wrote:
> I can confirm that problems with off-hook or rather "early state" are
> reproducible on OpensipS bran 1.5 Rev 5916.
> There is Reply 412 Conditional request failed for PUBLISH that has
> early in message body.
> This happens only when call is made by watched user to SPA942 that is
> watching that user.
>
> I have SIP traces and debug 9 for that scenario.
> Can I send them to you?
>
>
>
> On Tue, Jul 28, 2009 at 10:48 AM, Anca Vamanu 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:s...@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:s...@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:s...@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@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] BLF lights on Linksys 942/962 get stuck in "off-hook" state
I can confirm that problems with off-hook or rather "early state" are
reproducible on OpensipS bran 1.5 Rev 5916.
There is Reply 412 Conditional request failed for PUBLISH that has
early in message body.
This happens only when call is made by watched user to SPA942 that is
watching that user.
I have SIP traces and debug 9 for that scenario.
Can I send them to you?
On Tue, Jul 28, 2009 at 10:48 AM, Anca Vamanu 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:s...@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:s...@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:s...@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
--
Piotr Sobolewski
sobolew...@gmail.com
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] BLF lights on Linksys 942/962 get stuck in "off-hook" state
I am using 1.5.2
--James
On Jul 28, 2009, at 1:48, Anca Vamanu 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:s...@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:s...@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:s...@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@lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] BLF lights on Linksys 942/962 get stuck in "off-hook" state
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:s...@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:s...@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:s...@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@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] BLF lights on Linksys 942/962 get stuck in "off-hook" state
2009/7/28 James Lamanna : > 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. When I tested it (long time ago) the pua_dialoginfo wan't generate all the required PUBLISH. It could occur due to the dialog module... What you could do is inspect the SIP trace and find out which request (PUBLISH, NOTIFY) is missing. -- Iñaki Baz Castillo ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] BLF lights on Linksys 942/962 get stuck in "off-hook" state
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:s...@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:s...@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:s...@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@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
