[SR-Users] How to make BLF work

SamyGo govoiper at gmail.com
Fri May 31 18:47:02 CEST 2013


See the ngrep attached.



On Fri, May 31, 2013 at 9:41 PM, SamyGo <govoiper at gmail.com> wrote:

> Hi again,
>
> Adding SCA doesn't help much here. Please see the ngrep traces attached.
> However I've seen these logs showing up now:
>
> INFO: pua_dialoginfo [dialog_publish.c:386]: CALLING dialog_publish for
> URI sip:4155 at wistle.myvoipdomain.com:5060
> INFO: pua_dialoginfo [dialog_publish.c:386]: CALLING dialog_publish for
> URI sip:4144 at wistle.myvoipdomain.com:5060
>
> Unfortunately I still don't see any lights blinking on my phones.
>
> Any help here will be much appreciated.
>
> BR,
> Sammy
>
>
>
>
>
> On Fri, May 31, 2013 at 11:10 AM, SamyGo <govoiper at gmail.com> wrote:
>
>> Hi again,
>>
>> Yes Vitaliy, that's exactly where I started except it was the page for
>> Kamailio 4.0.
>> Following modules are loaded:
>>
>> loadmodule "presence.so"
>> loadmodule "presence_xml.so"
>> loadmodule "presence_dialoginfo.so"
>> loadmodule "presence_reginfo"
>> loadmodule "pua.so"
>> loadmodule "pua_dialoginfo.so"
>> loadmodule "pua_usrloc.so"
>> loadmodule "pua_reginfo"
>>
>> With following params:
>>
>> modparam("presence", "db_url", DBURL)
>> modparam("presence", "server_address", "sip:A.A.A.A:5060" )
>> modparam("presence", "send_fast_notify", 0)
>> modparam("presence", "db_update_period", 20)
>>
>> # ----- presence_xml params -----
>> modparam("presence_xml", "db_url", DBURL)
>> modparam("presence_xml", "force_active", 0)
>> modparam("presence_xml", "integrated_xcap_server", 1)
>> modparam("presence_dialoginfo", "force_single_dialog", 1)
>> modparam("pua", "db_url", DBURL)
>>
>> modparam("pua_usrloc", "default_domain", "myvoipdomain.com")
>> modparam("pua_usrloc", "branch_flag", 9)
>>
>> modparam("pua_dialoginfo", "include_callid", 1)
>> modparam("pua_reginfo", "server_address", "sip:reginfo at A.A.A.A:5060")
>> modparam("pua_reginfo", "default_domain", "myvoipdomain.com")
>> #!endif
>>
>> I'll try SCA module with these as well in a short while.
>>
>> I appreciate your help guys.
>>
>> --
>> Sammy
>>
>>
>>
>>
>> On Fri, May 31, 2013 at 2:28 AM, Vitaliy Aleksandrov <
>> vitalik.voip at gmail.com> wrote:
>>
>>>  Have you checked presence_dialoginfo documentation ?
>>> http://kamailio.org/docs/modules/devel/modules/presence_dialoginfo.html
>>>
>>> The link above has a description of the way BLF can be implemented on
>>> kamailio and I think it has all the details you need to make it work.
>>> I haven't used this scheme and know about it only from the mentioned
>>> paper, so I can't explain it in more detail.
>>>
>>>  Yes, As OEJ mentioned there were no Dialogs created so had to put the
>>> dlg_manage(); in the cfg and now in kamcmd the dlg.list command displays
>>> call data.
>>> How can I add presence stuff now.
>>>  Vitaliy, please explain further how can I add the PUA component.
>>>
>>>  Thanks,
>>> Sammy
>>>
>>>
>>>
>>>
>>>
>>> On Thu, May 30, 2013 at 6:17 PM, Olle E. Johansson <oej at edvina.net>wrote:
>>>
>>>>
>>>>  30 maj 2013 kl. 13:07 skrev SamyGo <govoiper at gmail.com>:
>>>>
>>>>  Hi again,
>>>>
>>>>  I doubt SCA module will work for me but let me get this a shot
>>>> tonight and get back with a sipgrep trace. Meanwhile I was just thinking if
>>>> the 'skype like service' blog at Asipto<http://kb.asipto.com/kamailio:skype-like-service-in-less-than-one-hour>might work straight away. I really don;t see any difference in my PRESENCE
>>>> route but maybe I've missed anything.
>>>>
>>>>  Let me get back with more working on this.
>>>>
>>>>  Start with making sure that the Dialog module works as expected for
>>>> you. Check with kamcmd that you have active dialogs when you have active
>>>> calls.
>>>> When that works, start with adding presence.
>>>>
>>>>  Cheers,
>>>> /O
>>>>
>>>>
>>>>  Thanks for the reply.
>>>>
>>>>  Sammy Go.
>>>>
>>>>
>>>>
>>>> On Wed, May 29, 2013 at 1:35 PM, Daniel-Constantin Mierla <
>>>> miconda at gmail.com> wrote:
>>>>
>>>>>  Hello,
>>>>>
>>>>> just to say that SCA module might be an alternative, not sure it works
>>>>> for blf, could be only for bla/sla, but worth checking the email.
>>>>>
>>>>> Also, if you post ngrep output (sip traffic as sip), could be easier
>>>>> to review the traces from a device that is not yet capable of installing
>>>>> tcpdump/ngrep/etc ... tools, like tablets, smartphones ... increasing your
>>>>> chance to get more people to an answer.
>>>>>
>>>>> Cheers,
>>>>> Daniel
>>>>>
>>>>>
>>>>> On 5/28/13 11:41 PM, SamyGo wrote:
>>>>>
>>>>> Yeah, I'm getting your point.
>>>>>
>>>>> So now, here are my loaded modules.
>>>>>
>>>>>  #!ifdef WITH_PRESENCE
>>>>> loadmodule "presence.so"
>>>>> loadmodule "presence_xml.so"
>>>>> loadmodule "presence_dialoginfo.so"
>>>>> loadmodule "pua.so"
>>>>>  loadmodule "pua_dialoginfo.so"
>>>>> loadmodule "pua_usrloc.so"
>>>>> #!endif
>>>>>
>>>>>  And of course:
>>>>>
>>>>>  loadmodule "dialog.so"
>>>>>
>>>>>  Attached are the relevant sip traces.
>>>>>
>>>>>
>>>>> On Wed, May 29, 2013 at 2:32 AM, SamyGo <govoiper at gmail.com> wrote:
>>>>>
>>>>>> Yeah, I'm getting your point.
>>>>>>
>>>>>> So now, here are my loaded modules.
>>>>>>
>>>>>>  #!ifdef WITH_PRESENCE
>>>>>> loadmodule "presence.so"
>>>>>> loadmodule "presence_xml.so"
>>>>>> loadmodule "presence_dialoginfo.so"
>>>>>> loadmodule "pua.so"
>>>>>>  loadmodule "pua_dialoginfo.so"
>>>>>> loadmodule "pua_usrloc.so"
>>>>>> #!endif
>>>>>>
>>>>>>  And of course:
>>>>>>
>>>>>>  loadmodule "dialog.so"
>>>>>>
>>>>>>  Attached are the relevant sip traces.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Wed, May 29, 2013 at 1:00 AM, Vitaliy Aleksandrov <
>>>>>> vitalik.voip at gmail.com> wrote:
>>>>>>
>>>>>>>  You didn't receive any NOTIFY requests because you didn't have a
>>>>>>> PUA client. rfc3903 describes what a PUA client is.
>>>>>>>
>>>>>>> To make BLF work you can try to use the next modules:
>>>>>>> 1. dialog - to enable dialog awareness
>>>>>>> 2. pua + pua_dialoginfo - to enable a PUA client based on active
>>>>>>> dialogs information provided by the "dialog" module
>>>>>>> 3. presence + presence_dialoginfo - to handle subscriptions and send
>>>>>>> notifications to phones
>>>>>>>
>>>>>>>   Hi list,
>>>>>>>
>>>>>>>  I've been trying to make my Yealink phone to give BLF indications
>>>>>>> but I haven't been able to achieve this successfully yet so I need some
>>>>>>> expert advise here.
>>>>>>>  My Yealink phone, as soon as it registers to Asterisk, gives me BLF
>>>>>>> lights. The same phone registering to Kamailio sends SUBSCRIBE and nothing
>>>>>>> happens.
>>>>>>>
>>>>>>>  The Presence Handling is enabled in configurations and yet no
>>>>>>> dialog-info+xml NOTIFY is received.
>>>>>>>
>>>>>>>  Please help.
>>>>>>>
>>>>>>>  Best Regards,
>>>>>>> Sammy Go.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>  _______________________________________________
>>>>>>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing listsr-users at lists.sip-router.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
>>>>>>> list
>>>>>>> sr-users at lists.sip-router.org
>>>>>>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing listsr-users at lists.sip-router.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>>>>
>>>>>
>>>>>   --
>>>>> Daniel-Constantin Mierla - http://www.asipto.comhttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
>>>>> Kamailio Advanced Training, San Francisco, USA - June 24-27, 2013
>>>>>   * http://asipto.com/u/katu *
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
>>>>> sr-users at lists.sip-router.org
>>>>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>>>>
>>>>>
>>>>  _______________________________________________
>>>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
>>>> sr-users at lists.sip-router.org
>>>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
>>>> sr-users at lists.sip-router.org
>>>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>>>
>>>>
>>>
>>>
>>> _______________________________________________
>>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing listsr-users at lists.sip-router.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>>
>>>
>>>
>>> _______________________________________________
>>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
>>> sr-users at lists.sip-router.org
>>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20130531/f2d0239c/attachment-0001.html>
-------------- next part --------------




U 2013/05/31 11:15:51.916220 175.110.123.170:62339 -> A.A.A.A:5060

REGISTER sip:wistle.myvoipdomain.com:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.137.115:50687;branch=z9hG4bK1395509258
From: "4144" <sip:4144 at wistle.myvoipdomain.com:5060>;tag=1195320343
To: "4144" <sip:4144 at wistle.myvoipdomain.com:5060>
Call-ID: 1748352519 at 192.168.137.115
CSeq: 1 REGISTER
Contact: <sip:4144 at 192.168.137.115:50687>
Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE
Max-Forwards: 70
User-Agent: Yealink SIP-T26P 6.60.0.120
Expires: 3600
Content-Length: 0


U 2013/05/31 11:15:51.917329 A.A.A.A:5060 -> 175.110.123.170:62339

SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.137.115:50687;branch=z9hG4bK1395509258;rport=62339;received=175.110.123.170
From: "4144" <sip:4144 at wistle.myvoipdomain.com:5060>;tag=1195320343
To: "4144" <sip:4144 at wistle.myvoipdomain.com:5060>;tag=66aa33862dbfa4f1bbc1cebf6c618e8c.2511
Call-ID: 1748352519 at 192.168.137.115
CSeq: 1 REGISTER
WWW-Authenticate: Digest realm="wistle.myvoipdomain.com", nonce="Uai/01Govqe7lVwzHTwUirHeaWnNebEn"
Server: kamailio (4.0.1 (i386/linux))
Content-Length: 0


U 2013/05/31 11:15:52.751038 175.110.123.170:62339 -> A.A.A.A:5060

REGISTER sip:wistle.myvoipdomain.com:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.137.115:50687;branch=z9hG4bK1395509258
From: "4144" <sip:4144 at wistle.myvoipdomain.com:5060>;tag=1195320343
To: "4144" <sip:4144 at wistle.myvoipdomain.com:5060>
Call-ID: 1748352519 at 192.168.137.115
CSeq: 1 REGISTER
Contact: <sip:4144 at 192.168.137.115:50687>
Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE
Max-Forwards: 70
User-Agent: Yealink SIP-T26P 6.60.0.120
Expires: 3600
Content-Length: 0


U 2013/05/31 11:15:52.754889 A.A.A.A:5060 -> 175.110.123.170:62339

SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.137.115:50687;branch=z9hG4bK1395509258;rport=62339;received=175.110.123.170
From: "4144" <sip:4144 at wistle.myvoipdomain.com:5060>;tag=1195320343
To: "4144" <sip:4144 at wistle.myvoipdomain.com:5060>;tag=66aa33862dbfa4f1bbc1cebf6c618e8c.2511
Call-ID: 1748352519 at 192.168.137.115
CSeq: 1 REGISTER
WWW-Authenticate: Digest realm="wistle.myvoipdomain.com", nonce="Uai/1FGovqhH0QSEz1Cn5+Gl+F5/ZlDX"
Server: kamailio (4.0.1 (i386/linux))
Content-Length: 0


U 2013/05/31 11:15:54.756459 175.110.123.170:62339 -> A.A.A.A:5060

REGISTER sip:wistle.myvoipdomain.com:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.137.115:50687;branch=z9hG4bK1701650077
From: "4144" <sip:4144 at wistle.myvoipdomain.com:5060>;tag=1127357442
To: "4144" <sip:4144 at wistle.myvoipdomain.com:5060>
Call-ID: 941968049 at 192.168.137.115
CSeq: 1 REGISTER
Contact: <sip:4144 at 192.168.137.115:50687>
Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE
Max-Forwards: 70
User-Agent: Yealink SIP-T26P 6.60.0.120
Expires: 3600
Content-Length: 0


U 2013/05/31 11:15:54.757723 A.A.A.A:5060 -> 175.110.123.170:62339

SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.137.115:50687;branch=z9hG4bK1701650077;rport=62339;received=175.110.123.170
From: "4144" <sip:4144 at wistle.myvoipdomain.com:5060>;tag=1127357442
To: "4144" <sip:4144 at wistle.myvoipdomain.com:5060>;tag=66aa33862dbfa4f1bbc1cebf6c618e8c.7704
Call-ID: 941968049 at 192.168.137.115
CSeq: 1 REGISTER
WWW-Authenticate: Digest realm="wistle.myvoipdomain.com", nonce="Uai/1lGovqq28gRQCrXQrKe5qe43+xnv"
Server: kamailio (4.0.1 (i386/linux))
Content-Length: 0


U 2013/05/31 11:15:55.206417 175.110.123.170:62339 -> A.A.A.A:5060

REGISTER sip:wistle.myvoipdomain.com:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.137.115:50687;branch=z9hG4bK1269541368
From: "4144" <sip:4144 at wistle.myvoipdomain.com:5060>;tag=1127357442
To: "4144" <sip:4144 at wistle.myvoipdomain.com:5060>
Call-ID: 941968049 at 192.168.137.115
CSeq: 2 REGISTER
Contact: <sip:4144 at 192.168.137.115:50687>
Authorization: Digest username="4144", realm="wistle.myvoipdomain.com", nonce="Uai/1lGovqq28gRQCrXQrKe5qe43+xnv", uri="sip:wistle.myvoipdomain.com:5060", response="627da0934738725a74f641d19eae5462", algorithm=MD5
Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE
Max-Forwards: 70
User-Agent: Yealink SIP-T26P 6.60.0.120
Expires: 3600
Content-Length: 0


U 2013/05/31 11:15:55.210732 A.A.A.A:5060 -> 175.110.123.170:62339

SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.137.115:50687;branch=z9hG4bK1269541368;rport=62339;received=175.110.123.170
From: "4144" <sip:4144 at wistle.myvoipdomain.com:5060>;tag=1127357442
To: "4144" <sip:4144 at wistle.myvoipdomain.com:5060>;tag=66aa33862dbfa4f1bbc1cebf6c618e8c.bf4e
Call-ID: 941968049 at 192.168.137.115
CSeq: 2 REGISTER
Contact: <sip:4144 at 192.168.137.89:50687>;expires=3274;received="sip:175.110.123.170:62334", <sip:4144 at 192.168.137.112:50687>;expires=3433;received="sip:175.110.123.170:62335", <sip:4144 at 192.168.137.115:50687>;expires=3600;received="sip:175.110.123.170:62339"
Server: kamailio (4.0.1 (i386/linux))
Content-Length: 0


U 2013/05/31 11:15:55.921391 175.110.123.170:62339 -> A.A.A.A:5060

REGISTER sip:wistle.myvoipdomain.com:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.137.115:50687;branch=z9hG4bK1269541368
From: "4144" <sip:4144 at wistle.myvoipdomain.com:5060>;tag=1127357442
To: "4144" <sip:4144 at wistle.myvoipdomain.com:5060>
Call-ID: 941968049 at 192.168.137.115
CSeq: 2 REGISTER
Contact: <sip:4144 at 192.168.137.115:50687>
Authorization: Digest username="4144", realm="wistle.myvoipdomain.com", nonce="Uai/1lGovqq28gRQCrXQrKe5qe43+xnv", uri="sip:wistle.myvoipdomain.com:5060", response="627da0934738725a74f641d19eae5462", algorithm=MD5
Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE
Max-Forwards: 70
User-Agent: Yealink SIP-T26P 6.60.0.120
Expires: 3600
Content-Length: 0


U 2013/05/31 11:15:55.923546 A.A.A.A:5060 -> 175.110.123.170:62339

SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.137.115:50687;branch=z9hG4bK1269541368;rport=62339;received=175.110.123.170
From: "4144" <sip:4144 at wistle.myvoipdomain.com:5060>;tag=1127357442
To: "4144" <sip:4144 at wistle.myvoipdomain.com:5060>;tag=66aa33862dbfa4f1bbc1cebf6c618e8c.bf4e
Call-ID: 941968049 at 192.168.137.115
CSeq: 2 REGISTER
Contact: <sip:4144 at 192.168.137.89:50687>;expires=3274;received="sip:175.110.123.170:62334", <sip:4144 at 192.168.137.112:50687>;expires=3433;received="sip:175.110.123.170:62335", <sip:4144 at 192.168.137.115:50687>;expires=3600;received="sip:175.110.123.170:62339"
Server: kamailio (4.0.1 (i386/linux))
Content-Length: 0


U 2013/05/31 11:15:56.187414 175.110.123.170:62340 -> A.A.A.A:5060

SUBSCRIBE sip:4144 at wistle.myvoipdomain.com:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.137.115:5065;rport;branch=z9hG4bK1945944788
From: "4133" <sip:4133 at wistle.myvoipdomain.com:5060>;tag=2053477444
To: <sip:4144 at wistle.myvoipdomain.com:5060>
Call-ID: 2104545828 at 192.168.137.115
CSeq: 1 SUBSCRIBE
Contact: <sip:4133 at 192.168.137.115:5065>
Accept: application/dialog-info+xml
Max-Forwards: 70
User-Agent: Yealink SIP-T26P 6.60.0.120
Expires: 1800
Event: dialog
Content-Length: 0


U 2013/05/31 11:15:56.188449 A.A.A.A:5060 -> 175.110.123.170:62340

SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP 192.168.137.115:5065;rport=62340;branch=z9hG4bK1945944788;received=175.110.123.170
From: "4133" <sip:4133 at wistle.myvoipdomain.com:5060>;tag=2053477444
To: <sip:4144 at wistle.myvoipdomain.com:5060>;tag=66aa33862dbfa4f1bbc1cebf6c618e8c.712a
Call-ID: 2104545828 at 192.168.137.115
CSeq: 1 SUBSCRIBE
Proxy-Authenticate: Digest realm="wistle.myvoipdomain.com", nonce="Uai/2FGovqw4VwuApg+n2k1WfpTc/wOB"
Server: kamailio (4.0.1 (i386/linux))
Content-Length: 0


U 2013/05/31 11:15:56.957277 175.110.123.170:62340 -> A.A.A.A:5060

SUBSCRIBE sip:4144 at wistle.myvoipdomain.com:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.137.115:5065;rport;branch=z9hG4bK1006396917
From: "4133" <sip:4133 at wistle.myvoipdomain.com:5060>;tag=2053477444
To: <sip:4144 at wistle.myvoipdomain.com:5060>
Call-ID: 2104545828 at 192.168.137.115
CSeq: 2 SUBSCRIBE
Contact: <sip:4133 at 192.168.137.115:5065>
Proxy-Authorization: Digest username="4133", realm="wistle.myvoipdomain.com", nonce="Uai/2FGovqw4VwuApg+n2k1WfpTc/wOB", uri="sip:4144 at wistle.myvoipdomain.com:5060", response="91ffe7ad1f1e0e618f01b8b8b9c8ed13", algorithm=MD5
Accept: application/dialog-info+xml
Max-Forwards: 70
User-Agent: Yealink SIP-T26P 6.60.0.120
Expires: 1800
Event: dialog
Content-Length: 0


U 2013/05/31 11:15:56.966041 A.A.A.A:5060 -> 175.110.123.170:62340

SIP/2.0 202 OK
Via: SIP/2.0/UDP 192.168.137.115:5065;rport=62340;branch=z9hG4bK1006396917;received=175.110.123.170
From: "4133" <sip:4133 at wistle.myvoipdomain.com:5060>;tag=2053477444
To: <sip:4144 at wistle.myvoipdomain.com:5060>;tag=414ad63373116e68203e2a5e8b07c824-86d7
Call-ID: 2104545828 at 192.168.137.115
CSeq: 2 SUBSCRIBE
Expires: 1800
Contact: <sip:A.A.A.A:5060>
Server: kamailio (4.0.1 (i386/linux))
Content-Length: 0


U 2013/05/31 11:15:56.969051 A.A.A.A:5060 -> 175.110.123.170:62340

NOTIFY sip:4133 at 175.110.123.170:62340 SIP/2.0
Via: SIP/2.0/UDP A.A.A.A:5060;branch=z9hG4bKff2d.7f017a93.0
To: sip:4133 at wistle.myvoipdomain.com;tag=2053477444
From: sip:4144 at wistle.myvoipdomain.com;tag=414ad63373116e68203e2a5e8b07c824-86d7
CSeq: 2 NOTIFY
Call-ID: 2104545828 at 192.168.137.115
Content-Length: 0
User-Agent: kamailio (4.0.1 (i386/linux))
Max-Forwards: 70
Event: dialog
Contact: <sip:A.A.A.A:5060>
Subscription-State: active;expires=1800


U 2013/05/31 11:15:57.111321 175.110.123.170:62339 -> A.A.A.A:5060

SUBSCRIBE sip:4133 at wistle.myvoipdomain.com:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.137.115:50687;branch=z9hG4bK1328103369
From: "4144" <sip:4144 at wistle.myvoipdomain.com:5060>;tag=354394453
To: <sip:4133 at wistle.myvoipdomain.com:5060>
Call-ID: 1635558949 at 192.168.137.115
CSeq: 1 SUBSCRIBE
Contact: <sip:4144 at 192.168.137.115:50687>
Accept: application/dialog-info+xml
Max-Forwards: 70
User-Agent: Yealink SIP-T26P 6.60.0.120
Expires: 1800
Event: dialog
Content-Length: 0


U 2013/05/31 11:15:57.112364 A.A.A.A:5060 -> 175.110.123.170:62339

SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP 192.168.137.115:50687;branch=z9hG4bK1328103369;rport=62339;received=175.110.123.170
From: "4144" <sip:4144 at wistle.myvoipdomain.com:5060>;tag=354394453
To: <sip:4133 at wistle.myvoipdomain.com:5060>;tag=66aa33862dbfa4f1bbc1cebf6c618e8c.e453
Call-ID: 1635558949 at 192.168.137.115
CSeq: 1 SUBSCRIBE
Proxy-Authenticate: Digest realm="wistle.myvoipdomain.com", nonce="Uai/2VGovq13Qi8EdCSzMkTiH04tO+Y0"
Server: kamailio (4.0.1 (i386/linux))
Content-Length: 0


U 2013/05/31 11:15:57.876254 175.110.123.170:62339 -> A.A.A.A:5060

SUBSCRIBE sip:4133 at wistle.myvoipdomain.com:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.137.115:50687;branch=z9hG4bK775544357
From: "4144" <sip:4144 at wistle.myvoipdomain.com:5060>;tag=354394453
To: <sip:4133 at wistle.myvoipdomain.com:5060>
Call-ID: 1635558949 at 192.168.137.115
CSeq: 2 SUBSCRIBE
Contact: <sip:4144 at 192.168.137.115:50687>
Proxy-Authorization: Digest username="4144", realm="wistle.myvoipdomain.com", nonce="Uai/2VGovq13Qi8EdCSzMkTiH04tO+Y0", uri="sip:4133 at wistle.myvoipdomain.com:5060", response="6b660899039a3aaaf47ad2e64ef99516", algorithm=MD5
Accept: application/dialog-info+xml
Max-Forwards: 70
User-Agent: Yealink SIP-T26P 6.60.0.120
Expires: 1800
Event: dialog
Content-Length: 0


U 2013/05/31 11:15:57.885048 A.A.A.A:5060 -> 175.110.123.170:62339

SIP/2.0 202 OK
Via: SIP/2.0/UDP 192.168.137.115:50687;branch=z9hG4bK775544357;rport=62339;received=175.110.123.170
From: "4144" <sip:4144 at wistle.myvoipdomain.com:5060>;tag=354394453
To: <sip:4133 at wistle.myvoipdomain.com:5060>;tag=414ad63373116e68203e2a5e8b07c824-d237
Call-ID: 1635558949 at 192.168.137.115
CSeq: 2 SUBSCRIBE
Expires: 1800
Contact: <sip:A.A.A.A:5060>
Server: kamailio (4.0.1 (i386/linux))
Content-Length: 0


U 2013/05/31 11:15:57.885367 A.A.A.A:5060 -> 175.110.123.170:62339

NOTIFY sip:4144 at 175.110.123.170:62339 SIP/2.0
Via: SIP/2.0/UDP A.A.A.A:5060;branch=z9hG4bKdcfd.fef41824.0
To: sip:4144 at wistle.myvoipdomain.com;tag=354394453
From: sip:4133 at wistle.myvoipdomain.com;tag=414ad63373116e68203e2a5e8b07c824-d237
CSeq: 2 NOTIFY
Call-ID: 1635558949 at 192.168.137.115
Content-Length: 0
User-Agent: kamailio (4.0.1 (i386/linux))
Max-Forwards: 70
Event: dialog
Contact: <sip:A.A.A.A:5060>
Subscription-State: active;expires=1800


U 2013/05/31 11:15:58.368102 A.A.A.A:5060 -> 175.110.123.170:62339

NOTIFY sip:4144 at 175.110.123.170:62339 SIP/2.0
Via: SIP/2.0/UDP A.A.A.A:5060;branch=z9hG4bKdcfd.fef41824.0
To: sip:4144 at wistle.myvoipdomain.com;tag=354394453
From: sip:4133 at wistle.myvoipdomain.com;tag=414ad63373116e68203e2a5e8b07c824-d237
CSeq: 2 NOTIFY
Call-ID: 1635558949 at 192.168.137.115
Content-Length: 0
User-Agent: kamailio (4.0.1 (i386/linux))
Max-Forwards: 70
Event: dialog
Contact: <sip:A.A.A.A:5060>
Subscription-State: active;expires=1800





U 2013/05/31 11:35:57.442619 175.110.123.170:62340 -> A.A.A.A:5060

SUBSCRIBE sip:A.A.A.A:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.137.115:5065;rport;branch=z9hG4bK172715904
From: "4133" <sip:4133 at wistle.myvoipdomain.com:5060>;tag=2053477444
To: <sip:4144 at wistle.myvoipdomain.com:5060>;tag=414ad63373116e68203e2a5e8b07c824-86d7
Call-ID: 2104545828 at 192.168.137.115
CSeq: 3 SUBSCRIBE
Contact: <sip:4133 at 192.168.137.115:5065>
Proxy-Authorization: Digest username="4133", realm="wistle.myvoipdomain.com", nonce="Uai/2FGovqw4VwuApg+n2k1WfpTc/wOB", uri="sip:A.A.A.A:5060", response="ccadd112e522aafb5ab0d836fec38c1a", algorithm=MD5
Accept: application/dialog-info+xml
Max-Forwards: 70
User-Agent: Yealink SIP-T26P 6.60.0.120
Expires: 1800
Event: dialog
Content-Length: 0


U 2013/05/31 11:35:57.452017 A.A.A.A:5060 -> 175.110.123.170:62340

SIP/2.0 202 OK
Via: SIP/2.0/UDP 192.168.137.115:5065;rport=62340;branch=z9hG4bK172715904;received=175.110.123.170
From: "4133" <sip:4133 at wistle.myvoipdomain.com:5060>;tag=2053477444
To: <sip:4144 at wistle.myvoipdomain.com:5060>;tag=414ad63373116e68203e2a5e8b07c824-86d7
Call-ID: 2104545828 at 192.168.137.115
CSeq: 3 SUBSCRIBE
Expires: 1800
Contact: <sip:A.A.A.A:5060>
Server: kamailio (4.0.1 (i386/linux))
Content-Length: 0


U 2013/05/31 11:35:57.452239 A.A.A.A:5060 -> 175.110.123.170:62340

NOTIFY sip:4133 at 175.110.123.170:62340 SIP/2.0
Via: SIP/2.0/UDP A.A.A.A:5060;branch=z9hG4bK003d.91459973.0
To: sip:4133 at wistle.myvoipdomain.com;tag=2053477444
From: sip:4144 at wistle.myvoipdomain.com;tag=414ad63373116e68203e2a5e8b07c824-86d7
CSeq: 3 NOTIFY
Call-ID: 2104545828 at 192.168.137.115
Content-Length: 0
User-Agent: kamailio (4.0.1 (i386/linux))
Max-Forwards: 70
Event: dialog
Contact: <sip:A.A.A.A:5060>
Subscription-State: active;expires=1800


U 2013/05/31 11:35:58.426384 175.110.123.170:62339 -> A.A.A.A:5060

SUBSCRIBE sip:A.A.A.A:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.137.115:50687;branch=z9hG4bK1035835526
From: "4144" <sip:4144 at wistle.myvoipdomain.com:5060>;tag=354394453
To: <sip:4133 at wistle.myvoipdomain.com:5060>;tag=414ad63373116e68203e2a5e8b07c824-d237
Call-ID: 1635558949 at 192.168.137.115
CSeq: 3 SUBSCRIBE
Contact: <sip:4144 at 192.168.137.115:50687>
Proxy-Authorization: Digest username="4144", realm="wistle.myvoipdomain.com", nonce="Uai/2VGovq13Qi8EdCSzMkTiH04tO+Y0", uri="sip:A.A.A.A:5060", response="aa23dea2bdb2e355b38638f4460612af", algorithm=MD5
Accept: application/dialog-info+xml
Max-Forwards: 70
User-Agent: Yealink SIP-T26P 6.60.0.120
Expires: 1800
Event: dialog
Content-Length: 0


U 2013/05/31 11:35:58.432627 A.A.A.A:5060 -> 175.110.123.170:62339

SIP/2.0 202 OK
Via: SIP/2.0/UDP 192.168.137.115:50687;branch=z9hG4bK1035835526;rport=62339;received=175.110.123.170
From: "4144" <sip:4144 at wistle.myvoipdomain.com:5060>;tag=354394453
To: <sip:4133 at wistle.myvoipdomain.com:5060>;tag=414ad63373116e68203e2a5e8b07c824-d237
Call-ID: 1635558949 at 192.168.137.115
CSeq: 3 SUBSCRIBE
Expires: 1800
Contact: <sip:A.A.A.A:5060>
Server: kamailio (4.0.1 (i386/linux))
Content-Length: 0


U 2013/05/31 11:35:58.432829 A.A.A.A:5060 -> 175.110.123.170:62339

NOTIFY sip:4144 at 175.110.123.170:62339 SIP/2.0
Via: SIP/2.0/UDP A.A.A.A:5060;branch=z9hG4bKecfd.715845d7.0
To: sip:4144 at wistle.myvoipdomain.com;tag=354394453
From: sip:4133 at wistle.myvoipdomain.com;tag=414ad63373116e68203e2a5e8b07c824-d237
CSeq: 3 NOTIFY
Call-ID: 1635558949 at 192.168.137.115
Content-Length: 0
User-Agent: kamailio (4.0.1 (i386/linux))
Max-Forwards: 70
Event: dialog
Contact: <sip:A.A.A.A:5060>
Subscription-State: active;expires=1800


U 2013/05/31 11:40:39.493644 A.A.A.A:5060 -> 175.110.123.170:62334

NOTIFY sip:4144 at 175.110.123.170:62334 SIP/2.0
Via: SIP/2.0/UDP A.A.A.A:5060;branch=z9hG4bK1841.b932ebf5.0
To: sip:4144 at wistle.myvoipdomain.com;tag=70274778
From: sip:4133 at wistle.myvoipdomain.com;tag=414ad63373116e68203e2a5e8b07c824-98e4
CSeq: 3 NOTIFY
Call-ID: 445864632 at 192.168.137.89
Content-Length: 0
User-Agent: kamailio (4.0.1 (i386/linux))
Max-Forwards: 70
Event: dialog
Contact: <sip:A.A.A.A:5060>
Subscription-State: terminated;reason=timeout


U 2013/05/31 11:40:39.493895 A.A.A.A:5060 -> 175.110.123.170:62333

NOTIFY sip:4133 at 175.110.123.170:62333 SIP/2.0
Via: SIP/2.0/UDP A.A.A.A:5060;branch=z9hG4bK196d.fd35cb22.0
To: sip:4133 at wistle.myvoipdomain.com;tag=1487617686
From: sip:4144 at wistle.myvoipdomain.com;tag=414ad63373116e68203e2a5e8b07c824-176a
CSeq: 3 NOTIFY
Call-ID: 2073093363 at 192.168.137.89
Content-Length: 0
User-Agent: kamailio (4.0.1 (i386/linux))
Max-Forwards: 70
Event: dialog
Contact: <sip:A.A.A.A:5060>
Subscription-State: terminated;reason=timeout


U 2013/05/31 11:40:39.993103 A.A.A.A:5060 -> 175.110.123.170:62334

NOTIFY sip:4144 at 175.110.123.170:62334 SIP/2.0
Via: SIP/2.0/UDP A.A.A.A:5060;branch=z9hG4bK1841.b932ebf5.0
To: sip:4144 at wistle.myvoipdomain.com;tag=70274778
From: sip:4133 at wistle.myvoipdomain.com;tag=414ad63373116e68203e2a5e8b07c824-98e4
CSeq: 3 NOTIFY
Call-ID: 445864632 at 192.168.137.89
Content-Length: 0
User-Agent: kamailio (4.0.1 (i386/linux))
Max-Forwards: 70
Event: dialog
Contact: <sip:A.A.A.A:5060>
Subscription-State: terminated;reason=timeout




More information about the sr-users mailing list