[Serusers] UAC disapear from "location"

Klaus Darilion klaus.mailinglists at pernau.at
Fri Mar 4 17:49:58 CET 2005


Looks like the contact in the 200 OK response is different as the one in 
the REGISTER message. This might confuse the RTC API.

Probably you use fix_nated_contact from nathelper or fix_contact from 
mediaproxy module. Try to use fix_nated_register from nathelper module 
instead. This will preserve the real contact.

regards,
klaus

braincrew.com wrote:

> I just sniffed the logging and here it is:
> 
> 
> [UDP] source ip: 78.54.32.1:5060, destination ip: 85.2.68.15:1180
> content: SIP/2.0 200 OK
> Via: SIP/2.0/UDP 192.168.2.50:7058;rport=1180;received=85.2.68.15
> From: 
> <sip:257308 at sipdomain.com>;tag=392ee80ede39414f8a1fb7d14630a8e3;epid=562c4da242 
> 
> To: <sip:257308 at sipdomain.com>;tag=774666b140502dfba1196554e4b07600.70c3
> Call-ID: f4fc6c1c2d21445f8ecf673f50bee75e at 192.168.2.50
> CSeq: 4 REGISTER
> Server: Sip EXpress router (0.9.0 (i386/linux))
> Content-Length: 0
> Warning: 392 sipdomain.com:5060 "Noisy feedback tells:  pid=19326 
> req_src_ip=85.2.68.15 req_src_port=1180 in_uri=sip:sipdomain.com 
> out_uri=sip:sipdomain.com via_cnt==1"
> 
> te.com out_uri=sip:sipdomain.com via_cnt==1"
> 
> 373796bda639a80"
> Event: registration
> Allow-Events: presence
> Content-Length: 0
> 
> 
> [UDP] source ip: 85.2.68.15:1180, destination ip: 78.54.32.1:5060
> content: REGISTER sip:sipdomain.com SIP/2.0
> Via: SIP/2.0/UDP 192.168.2.50:7058
> Max-Forwards: 70
> From: 
> <sip:257308 at sipdomain.com>;tag=6a56fb587c454c0385fac21e2d81fc51;epid=3cb7f59823 
> 
> To: <sip:257308 at sipdomain.com>
> Call-ID: c95e5f3242ad4a389ebc68cddbc85c31 at 192.168.2.50
> CSeq: 3 REGISTER
> Contact: <sip:192.168.2.50:7058>;methods="INVITE, MESSAGE, INFO, 
> SUBSCRIBE, OPTIONS, BYE, CANCEL, NOTIFY, ACK, REFER"
> User-Agent: RTC/1.2.4949
> Expires: 0
> Event: registration
> Content-Length: 0
> 
> 
> [UDP] source ip: 78.54.32.1:5060, destination ip: 85.2.68.15:1180
> content: SIP/2.0 401 Unauthorized
> Via: SIP/2.0/UDP 192.168.2.50:7058;rport=1180;received=85.2.68.15
> From: 
> <sip:257308 at sipdomain.com>;tag=6a56fb587c454c0385fac21e2d81fc51;epid=3cb7f59823 
> 
> To: <sip:257308 at sipdomain.com>;tag=774666b140502dfba1196554e4b07600.70c3
> Call-ID: c95e5f3242ad4a389ebc68cddbc85c31 at 192.168.2.50
> CSeq: 3 REGISTER
> WWW-Authenticate: Digest realm="sipdomain.com", 
> nonce="422877f871da7ada13d93a283fe87b6e56c5c22b"
> Server: Sip EXpress router (0.9.0 (i386/linux))
> Content-Length: 0
> Warning: 392 sipdomain.com:5060 "Noisy feedback tells:  pid=19327 
> req_src_ip=85.2.68.15 req_src_port=1180 in_uri=sip:sipdomain.com 
> out_uri=sip:sipdomain.com via_cnt==1"
> 
> 
> [UDP] source ip: 85.2.68.15:1180, destination ip: 78.54.32.1:5060
> content: REGISTER sip:sipdomain.com SIP/2.0
> Via: SIP/2.0/UDP 192.168.2.50:7058
> Max-Forwards: 70
> From: 
> <sip:257308 at sipdomain.com>;tag=a9c7770142084ee78ebd29f7aa599013;epid=468cfb0e02 
> 
> To: <sip:257308 at sipdomain.com>
> Call-ID: 8a2848712761415ab4c29a7998031e0f at 192.168.2.50
> CSeq: 1 REGISTER
> Contact: <sip:192.168.2.50:7058>;methods="INVITE, MESSAGE, INFO, 
> SUBSCRIBE, OPTIONS, BYE, CANCEL, NOTIFY, ACK, REFER"
> User-Agent: RTC/1.2.4949
> Event: registration
> Allow-Events: presence
> Content-Length: 0
> 
> 
> Warning: 392 sipdomain.com:5060 "Noisy feedback tells:  pid=19327 
> req_src_ip=85.2.68.15 req_src_port=1180 in_uri=sip:sipdomain.com 
> out_uri=sip:sipdomain.com via_cnt==1"
> 
> 
> [UDP] source ip: 78.54.32.1:5060, destination ip: 85.2.68.15:1180
> content: SIP/2.0 401 Unauthorized
> Via: SIP/2.0/UDP 192.168.2.50:7058;rport=1180;received=85.2.68.15
> From: 
> <sip:257308 at sipdomain.com>;tag=a9c7770142084ee78ebd29f7aa599013;epid=468cfb0e02 
> 
> To: <sip:257308 at sipdomain.com>;tag=774666b140502dfba1196554e4b07600.70c3
> Call-ID: 8a2848712761415ab4c29a7998031e0f at 192.168.2.50
> CSeq: 1 REGISTER
> WWW-Authenticate: Digest realm="sipdomain.com", 
> nonce="422877f871da7ada13d93a283fe87b6e56c5c22b"
> Server: Sip EXpress router (0.9.0 (i386/linux))
> Content-Length: 0
> Warning: 392 sipdomain.com:5060 "Noisy feedback tells:  pid=19328 
> req_src_ip=85.2.68.15 req_src_port=1180 in_uri=sip:sipdomain.com 
> out_uri=sip:sipdomain.com via_cnt==1"
> 
> 
> [UDP] source ip: 85.2.68.15:1180, destination ip: 78.54.32.1:5060
> content: REGISTER sip:sipdomain.com SIP/2.0
> Via: SIP/2.0/UDP 192.168.2.50:7058
> Max-Forwards: 70
> From: 
> <sip:257308 at sipdomain.com>;tag=6a56fb587c454c0385fac21e2d81fc51;epid=3cb7f59823 
> 
> To: <sip:257308 at sipdomain.com>
> Call-ID: c95e5f3242ad4a389ebc68cddbc85c31 at 192.168.2.50
> CSeq: 4 REGISTER
> Contact: <sip:192.168.2.50:7058>;methods="INVITE, MESSAGE, INFO, 
> SUBSCRIBE, OPTIONS, BYE, CANCEL, NOTIFY, ACK, REFER"
> User-Agent: RTC/1.2.4949
> Authorization: Digest username="257308", realm="sipdomain.com", 
> algorithm=md5, uri="sip:sipdomain.com", 
> nonce="422877f871da7ada13d93a283fe87b6e56c5c22b", 
> response="fba58e1bb7715d0332bafdec3c1b6435"
> Expires: 0
> Event: registration
> Content-Length: 0
> 
> [UDP] source ip: 85.2.68.15:1180, destination ip: 78.54.32.1:5060
> content: REGISTER sip:sipdomain.com SIP/2.0
> Via: SIP/2.0/UDP 192.168.2.50:7058
> Max-Forwards: 70
> From: 
> <sip:257308 at sipdomain.com>;tag=a9c7770142084ee78ebd29f7aa599013;epid=468cfb0e02 
> 
> To: <sip:257308 at sipdomain.com>
> Call-ID: 8a2848712761415ab4c29a7998031e0f at 192.168.2.50
> CSeq: 2 REGISTER
> Contact: <sip:192.168.2.50:7058>;methods="INVITE, MESSAGE, INFO, 
> SUBSCRIBE, OPTIONS, BYE, CANCEL, NOTIFY, ACK, REFER"
> User-Agent: RTC/1.2.4949
> Authorization: Digest username="257308", realm="sipdomain.com", 
> algorithm=md5, uri="sip:sipdomain.com", 
> nonce="422877f871da7ada13d93a283fe87b6e56c5c22b", 
> response="fba58e1bb7715d0332bafdec3c1b6435"
> Event: registration
> Allow-Events: presence
> Content-Length: 0
> 
> ?=
> [UDP] source ip: 78.54.32.1:5060, destination ip: 85.2.68.15:1180
> content: SIP/2.0 200 OK
> Via: SIP/2.0/UDP 192.168.2.50:7058;rport=1180;received=85.2.68.15
> From: 
> <sip:257308 at sipdomain.com>;tag=6a56fb587c454c0385fac21e2d81fc51;epid=3cb7f59823 
> 
> To: <sip:257308 at sipdomain.com>;tag=774666b140502dfba1196554e4b07600.70c3
> Call-ID: c95e5f3242ad4a389ebc68cddbc85c31 at 192.168.2.50
> CSeq: 4 REGISTER
> Server: Sip EXpress router (0.9.0 (i386/linux))
> Content-Length: 0
> Warning: 392 sipdomain.com:5060 "Noisy feedback tells:  pid=19325 
> req_src_ip=85.2.68.15 req_src_port=1180 in_uri=sip:sipdomain.com 
> out_uri=sip:sipdomain.com via_cnt==1"
> 
> 83fe87b6e56c5c22b", response="fba58e1bb7715d0332bafdec3c1b6435"
> Event: registration
> Allow-Events: presence
> Content-Length: 0
> 
> ?=
> [UDP] source ip: 78.54.32.1:5060, destination ip: 85.2.68.15:1180
> content: SIP/2.0 200 OK
> Via: SIP/2.0/UDP 192.168.2.50:7058;rport=1180;received=85.2.68.15
> From: 
> <sip:257308 at sipdomain.com>;tag=a9c7770142084ee78ebd29f7aa599013;epid=468cfb0e02 
> 
> To: <sip:257308 at sipdomain.com>;tag=774666b140502dfba1196554e4b07600.70c3
> Call-ID: 8a2848712761415ab4c29a7998031e0f at 192.168.2.50
> CSeq: 2 REGISTER
> Contact: <sip:85.2.68.15:1180>;expires=3600
> Server: Sip EXpress router (0.9.0 (i386/linux))
> Content-Length: 0
> Warning: 392 sipdomain.com:5060 "Noisy feedback tells:  pid=19327 
> req_src_ip=85.2.68.15 req_src_port=1180 in_uri=sip:sipdomain.com 
> out_uri=sip:sipdomain.com via_cnt==1"
> 
> 2bafdec3c1b6435"
> Event: registration
> Allow-Events: presence
> Content-Length: 0
> 
> ?=
> [UDP] source ip: 85.2.68.15:1180, destination ip: 78.54.32.1:5060
> content: REGISTER sip:sipdomain.com SIP/2.0
> Via: SIP/2.0/UDP 192.168.2.50:7058
> Max-Forwards: 70
> From: 
> <sip:257308 at sipdomain.com>;tag=a9c7770142084ee78ebd29f7aa599013;epid=468cfb0e02 
> 
> To: <sip:257308 at sipdomain.com>
> Call-ID: 8a2848712761415ab4c29a7998031e0f at 192.168.2.50
> CSeq: 3 REGISTER
> Contact: <sip:192.168.2.50:7058>;methods="INVITE, MESSAGE, INFO, 
> SUBSCRIBE, OPTIONS, BYE, CANCEL, NOTIFY, ACK, REFER"
> User-Agent: RTC/1.2.4949
> Expires: 0
> Event: registration
> Content-Length: 0
> 
> rc_ip=217.155.150.227 req_src_port=2891 in_uri=sip:sipdomain.com 
> out_uri=sip:sipdomain.com via_cnt==1"
> 
> ", response="91937554648f3d5bd501e4d64d680f18"
> Event: registration
> Allow-Events: presence
> Content-Length: 0
> 
> 
> [UDP] source ip: 85.2.68.15:1180, destination ip: 78.54.32.1:5060
> content: REGISTER sip:sipdomain.com SIP/2.0
> Via: SIP/2.0/UDP 192.168.2.50:7058
> Max-Forwards: 70
> From: 
> <sip:257308 at sipdomain.com>;tag=ef53ac1df4d7425da595cb8b0857058c;epid=a5606e3513 
> 
> To: <sip:257308 at sipdomain.com>
> Call-ID: da56c003e5954c75bd121ac4ad767b78 at 192.168.2.50
> CSeq: 1 REGISTER
> Contact: <sip:192.168.2.50:7058>;methods="INVITE, MESSAGE, INFO, 
> SUBSCRIBE, OPTIONS, BYE, CANCEL, NOTIFY, ACK, REFER"
> User-Agent: RTC/1.2.4949
> Event: registration
> Allow-Events: presence
> Content-Length: 0
> 
> 
> [UDP] source ip: 78.54.32.1:5060, destination ip: 85.2.68.15:1180
> content: SIP/2.0 401 Unauthorized
> Via: SIP/2.0/UDP 192.168.2.50:7058;rport=1180;received=85.2.68.15
> From: 
> <sip:257308 at sipdomain.com>;tag=a9c7770142084ee78ebd29f7aa599013;epid=468cfb0e02 
> 
> To: <sip:257308 at sipdomain.com>;tag=774666b140502dfba1196554e4b07600.70c3
> Call-ID: 8a2848712761415ab4c29a7998031e0f at 192.168.2.50
> CSeq: 3 REGISTER
> WWW-Authenticate: Digest realm="sipdomain.com", 
> nonce="422877fc9ff0ea2056c113ea605f7b0ebf1db1eb"
> Server: Sip EXpress router (0.9.0 (i386/linux))
> Content-Length: 0
> Warning: 392 sipdomain.com:5060 "Noisy feedback tells:  pid=19326 
> req_src_ip=85.2.68.15 req_src_port=1180 in_uri=sip:sipdomain.com 
> out_uri=sip:sipdomain.com via_cnt==1"
> 
> 
> [UDP] source ip: 78.54.32.1:5060, destination ip: 85.2.68.15:1180
> content: SIP/2.0 401 Unauthorized
> Via: SIP/2.0/UDP 192.168.2.50:7058;rport=1180;received=85.2.68.15
> From: 
> <sip:257308 at sipdomain.com>;tag=ef53ac1df4d7425da595cb8b0857058c;epid=a5606e3513 
> 
> To: <sip:257308 at sipdomain.com>;tag=774666b140502dfba1196554e4b07600.70c3
> Call-ID: da56c003e5954c75bd121ac4ad767b78 at 192.168.2.50
> CSeq: 1 REGISTER
> WWW-Authenticate: Digest realm="sipdomain.com", 
> nonce="422877fc9ff0ea2056c113ea605f7b0ebf1db1eb"
> Server: Sip EXpress router (0.9.0 (i386/linux))
> Content-Length: 0
> Warning: 392 sipdomain.com:5060 "Noisy feedback tells:  pid=19325 
> req_src_ip=85.2.68.15 req_src_port=1180 in_uri=sip:sipdomain.com 
> out_uri=sip:sipdomain.com via_cnt==1"
> 
> 
> [UDP] source ip: 85.2.68.15:1180, destination ip: 78.54.32.1:5060
> content: REGISTER sip:sipdomain.com SIP/2.0
> Via: SIP/2.0/UDP 192.168.2.50:7058
> Max-Forwards: 70
> From: 
> <sip:257308 at sipdomain.com>;tag=a9c7770142084ee78ebd29f7aa599013;epid=468cfb0e02 
> 
> To: <sip:257308 at sipdomain.com>
> Call-ID: 8a2848712761415ab4c29a7998031e0f at 192.168.2.50
> CSeq: 4 REGISTER
> Contact: <sip:192.168.2.50:7058>;methods="INVITE, MESSAGE, INFO, 
> SUBSCRIBE, OPTIONS, BYE, CANCEL, NOTIFY, ACK, REFER"
> User-Agent: RTC/1.2.4949
> Authorization: Digest username="257308", realm="sipdomain.com", 
> algorithm=md5, uri="sip:sipdomain.com", 
> nonce="422877fc9ff0ea2056c113ea605f7b0ebf1db1eb", 
> response="38bb5177a55427b0fb2784f68370321e"
> Expires: 0
> Event: registration
> Content-Length: 0
> 
> 
> [UDP] source ip: 85.2.68.15:1180, destination ip: 78.54.32.1:5060
> content: REGISTER sip:sipdomain.com SIP/2.0
> Via: SIP/2.0/UDP 192.168.2.50:7058
> Max-Forwards: 70
> From: 
> <sip:257308 at sipdomain.com>;tag=ef53ac1df4d7425da595cb8b0857058c;epid=a5606e3513 
> 
> To: <sip:257308 at sipdomain.com>
> Call-ID: da56c003e5954c75bd121ac4ad767b78 at 192.168.2.50
> CSeq: 2 REGISTER
> Contact: <sip:192.168.2.50:7058>;methods="INVITE, MESSAGE, INFO, 
> SUBSCRIBE, OPTIONS, BYE, CANCEL, NOTIFY, ACK, REFER"
> User-Agent: RTC/1.2.4949
> Authorization: Digest username="257308", realm="sipdomain.com", 
> algorithm=md5, uri="sip:sipdomain.com", 
> nonce="422877fc9ff0ea2056c113ea605f7b0ebf1db1eb", 
> response="38bb5177a55427b0fb2784f68370321e"
> Event: registration
> Allow-Events: presence
> Content-Length: 0
> 
> 
> [UDP] source ip: 78.54.32.1:5060, destination ip: 85.2.68.15:1180
> content: SIP/2.0 200 OK
> Via: SIP/2.0/UDP 192.168.2.50:7058;rport=1180;received=85.2.68.15
> From: 
> <sip:257308 at sipdomain.com>;tag=ef53ac1df4d7425da595cb8b0857058c;epid=a5606e3513 
> 
> To: <sip:257308 at sipdomain.com>;tag=774666b140502dfba1196554e4b07600.70c3
> Call-ID: da56c003e5954c75bd121ac4ad767b78 at 192.168.2.50
> CSeq: 2 REGISTER
> Contact: <sip:85.2.68.15:1180>;expires=3600
> Server: Sip EXpress router (0.9.0 (i386/linux))
> Content-Length: 0
> Warning: 392 sipdomain.com:5060 "Noisy feedback tells:  pid=19326 
> req_src_ip=85.2.68.15 req_src_port=1180 in_uri=sip:sipdomain.com 
> out_uri=sip:sipdomain.com via_cnt==1"
> 
> b2784f68370321e"
> Event: registration
> Allow-Events: presence
> Content-Length: 0
> 
> 
> [UDP] source ip: 78.54.32.1:5060, destination ip: 85.2.68.15:1180
> content: SIP/2.0 200 OK
> Via: SIP/2.0/UDP 192.168.2.50:7058;rport=1180;received=85.2.68.15
> From: 
> <sip:257308 at sipdomain.com>;tag=a9c7770142084ee78ebd29f7aa599013;epid=468cfb0e02 
> 
> To: <sip:257308 at sipdomain.com>;tag=774666b140502dfba1196554e4b07600.70c3
> Call-ID: 8a2848712761415ab4c29a7998031e0f at 192.168.2.50
> CSeq: 4 REGISTER
> Server: Sip EXpress router (0.9.0 (i386/linux))
> Content-Length: 0
> Warning: 392 sipdomain.com:5060 "Noisy feedback tells:  pid=19328 
> req_src_ip=80.72.68.187 req_src_port=1180 in_uri=sip:sipdomain.com 
> out_uri=sip:sipdomain.com via_cnt==1"
> 
> te.com out_uri=sip:sipdomain.com via_cnt==1"
> 
> b2784f68370321e"
> Event: registration
> Allow-Events: presence
> Content-Length: 0
> 
> 
> Thanks,
> Steve
> ----- Original Message ----- From: "Klaus Darilion" 
> <klaus.mailinglists at pernau.at>
> To: "Pavel Siderov - Hostmates" <pi at hostmates.com>
> Cc: <serusers at lists.iptel.org>
> Sent: Friday, March 04, 2005 4:46 PM
> Subject: Re: [Serusers] UAC disapear from "location"
> 
> 
>> Before we can fix the problem we have to find the cause. Maybe it is 
>> related to the expires parameter - as you see, a 200 OK response may 
>> include the expires parameter two times:
>> - in the Expires: header
>> - in the Contact: header
>>
>> Maybe this confuses RTC (just a guess). Try playing around with the 
>> expires parameters.
>>
>> regards,
>> klaus
>>
>> SIP/2.0 200 OK
>> Via: SIP/2.0/UDP 
>> 10.10.0.161:7440;branch=z9hG4bK-d87543-113007526-1--d87543-;rport
>> From: Klaus <sip:klaus.darilion at nic.at43.at>;tag=de73fa72
>> To: Klaus <sip:klaus.darilion at nic.at43.at>
>> Call-Id: f15d2f3eb1517811
>> CSeq: 844 REGISTER
>> Expires: 171
>> Contact: <sip:klaus.darilion at 10.10.0.161:7440>;expires=171
>> Content-Length: 0
>>
>> Pavel Siderov - Hostmates wrote:
>>
>>> But I tried many other dialers and all of them work great w/ my sip 
>>> proxy...
>>> so I think that the problem is w/ my client. Any idea how to fix that?
>>>
>>> Thanks,
>>> Steve
>>>
>>> ----- Original Message ----- From: "Klaus Darilion" 
>>> <klaus.mailinglists at pernau.at>
>>> To: "braincrew.com" <somebody at braincrew.com>
>>> Cc: <serusers at lists.iptel.org>
>>> Sent: Friday, March 04, 2005 3:49 PM
>>> Subject: Re: [Serusers] UAC disapear from "location"
>>>
>>>
>>>> Try to use your application with an other SIP proxy - e.g. iptel.org 
>>>> and freeworlddialup.
>>>>
>>>> This way you can find out if your application is wrong or your SIP 
>>>> proxy. Maybe the RTC API does not like the 200 OK messages.
>>>>
>>>> regards,
>>>> klaus
>>>>
>>>> braincrew.com wrote:
>>>>
>>>>> Hi Klaus,
>>>>>
>>>>> all "expire" variables are set to 600 seconds (10 min)
>>>>>
>>>>> modparam("registrar", "default_expires", 600)
>>>>> modparam("registrar", "min_expires", 600)
>>>>> modparam("registrar", "max_expires", 600)
>>>>>
>>>>> I'm using ser v 0.9
>>>>>
>>>>> Thanks,
>>>>> Steve
>>>>>
>>>>> ----- Original Message ----- From: "Klaus Darilion" 
>>>>> <klaus.mailinglists at pernau.at>
>>>>> To: "braincrew.com" <somebody at braincrew.com>
>>>>> Cc: <serusers at lists.iptel.org>
>>>>> Sent: Friday, March 04, 2005 2:41 PM
>>>>> Subject: Re: [Serusers] UAC disapear from "location"
>>>>>
>>>>>
>>>>>> Hi Steve!
>>>>>>
>>>>>> Once I also had this problem with Windows Messenger, but I can't 
>>>>>> remember the problems origin. I think I could solve it by setting 
>>>>>> the default-expires, min-expires and max-expires. Which ser 
>>>>>> version do you use?
>>>>>>
>>>>>> regards,
>>>>>> klaus
>>>>>>
>>>>>> braincrew.com wrote:
>>>>>>
>>>>>>> Hi guys,
>>>>>>>  I'm trying to build sip dialer using microsoft api. It's still 
>>>>>>> in beginning phase but I have problem:
>>>>>>> dialer disapear from the location after some time. I tried to 
>>>>>>> make it re-register after every five
>>>>>>> minutes but sometimes it fails.
>>>>>>> Somebody can help me?
>>>>>>>  Thanks in advance,
>>>>>>> Steve Plawer
>>>>>>>
>>>>>>>
>>>>>>> ------------------------------------------------------------------------ 
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Serusers mailing list
>>>>>>> serusers at lists.iptel.org
>>>>>>> http://lists.iptel.org/mailman/listinfo/serusers
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> Serusers mailing list
>>>> serusers at lists.iptel.org
>>>> http://lists.iptel.org/mailman/listinfo/serusers
>>>>
>>>
>>>
>>
>>
> 
> 




More information about the sr-users mailing list