Send discussion mailing list submissions to
discussion sipforum.org
To subscribe or unsubscribe via the World Wide Web, visit
http:
//sipforum.org/mailman/listinfo/discussion
or, via email, send a message with subject or body 'help'
to
discussion-requestsipforum.org
You can reach the person managing the list at
discussion-ownersipforum.org
When replying, please edit your Subject line so it is more
specific
than "Re: Contents of discussion digest..."
Today's Topics:
1. [Fwd: 408 response during registration] (Andrew Yu)
2. Re: Incorrect register request (Andrew Yu)
3. Re: A question on SIP Registration Interval (Andrew
Yu)
------------------------------------------------------------
----------
Message: 1
Date: Sat, 16 Jun 2007 00:12:54 +0800
From: Andrew Yu <andrewasiatel.com.sg>
Subject: [SIPForum-discussion] [Fwd: 408 response during
registration]
To: anilkrishna mantena <anilkrishnamanthenayahoo.com>
Cc: discussionsipforum.org
Message-ID: <4672BA86.5060404asiatel.com.sg>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Hi Anikrishna,
It will be helpful if you could show us your settings.
--
Cheers,
Asiatel Singapore Pte Ltd
Andrew Yu
19 Jalan Kilang Barat
#06-01, Acetech Centre
Singapore 159361
Tel: +65 6271 8233
Fax: +65 6274 4266
-------- Original Message --------
Subject: [SIPForum-discussion] 408 response during
registration
Date: Fri, 15 Jun 2007 04:41:14 -0700 (PDT)
From: anilkrishna mantena <anilkrishnamanthenayahoo.com>
To: discussionsipforum.org
Hi all,
I'm using X-Lite to connect to one of my VoIP
accounts. In the past it worked fine, since couple of
days it is not working for any voip accounts except
"Gizmo" i.e., sipphone.com. My system is
connected
through LAN to Internet. I tested this X-Lite
application by downloading once again, it is giving
the same response that "408 - request timed out".
I
tested the same at internet cafe and in my home, and
it is working well over there. Why this X-Lite is not
working in my office. I am sure that no firewalls are
blocking my SIP requests. I tested VoipStunt,
VoipCheap, VoipDiscount accounts in x-lite, these all
are in vein. Please provide me the solution.
Thanks in advance.
Regards
Anilkrishna Manthena
____________________________________________________________
________________________
Be a better Globetrotter. Get better travel answers from
someone who knows. Yahoo! Answers - Check it out.
http://answers.yahoo.com/dir/?link=list&sid=3965454
69
_______________________________________________
This is the SIP Forum discussion mailing list
TO UNSUBSCRIBE, or edit your delivery options, please visit
http:
//sipforum.org/mailman/listinfo/discussion
Post to the list at discussionsipforum.org
__________ NOD32 2331 (20070615) Information __________
This message was checked by NOD32 antivirus system.
http://www.eset.com
------------------------------
Message: 2
Date: Sat, 16 Jun 2007 00:17:12 +0800
From: Andrew Yu <andrewasiatel.com.sg>
Subject: Re: [SIPForum-discussion] Incorrect register
request
To: andrewasiatel.com.sg, discussionsipforum.org
Message-ID: <4672BB88.4090600asiatel.com.sg>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Dear Members,
I'm appealing for more advices & comment on this issue
that I'm facing.
Thank you.
--
Cheers,
Asiatel Singapore Pte Ltd
Andrew Yu
19 Jalan Kilang Barat
#06-01, Acetech Centre
Singapore 159361
Tel: +65 6271 8233
Fax: +65 6274 4266
Andrew Yu wrote:
> Hi Lun & Vivek,
>
> All these transmissions are send at different timing
meaning that
> these are 3 separated requests, though the requests
looks like resent.
> There are no response from the sip server and and
finally 504 from the
> sbc to the UAC. Response from Ondo will have the server
header, those
> responses without server header are from sbc.
>
> Here's what I've identified for RFC3261 violations:
>
> 1. CSeq is always 3
> 2. Max-Forwards should be 70, 10 is too simply short!
I've not see
> any UAC sending 10 for max-forward, this can cause
the packets to
> be unintentionally dropped.
> 3. Branch-IDs in Via is not always unique, and it has
been reused in
> previous register requests. (Is it alright toreuse
branch-id from
> previous register request?)
>
> For your comments & advice please for any
unidentified RFC violations
> on my part.
>
> And as requested, the full capture of the register
request:
>
> User Datagram Protocol, Src Port: 5060 (5060), Dst
Port: 5060 (5060)
> Session Initiation Protocol
> Request-Line: REGISTER sip:sip.abc.com SIP/2.0
> Method: REGISTER
> Message Header
> From: 12345678
> <sip:12345678proxy.abc.com>;tag=e2ffc017e8f818109f1cafec866a1c9
f
> To: sip:12345678proxy.abc.com
> Via: SIP/2.0/UDP
>
192.168.1.250:5060;iid=4033;branch=z9hG4bK170cc117e8f818109f
1cafec866a1c9f;uas-addr=sip.abc.com;rport
>
> CSeq: 2 REGISTER
> Call-ID: e2ffc017-e8f8-1810-8cb1-afec866a1c9f
> Contact: "12345678"
> <sip:12345678192.168.1.250:5060;transport=udp>
> User-Agent: OpenSIPStack-1.1.6-134
> Expires: 60
> Max-Forwards: 10
> Allow: INVITE, BYE, ACK, REFER, MESSAGE, INFO,
NOTIFY, OPTIONS
> Content-Length: 0
>
> User Datagram Protocol, Src Port: 5060 (5060), Dst
Port: 5060 (5060)
> Session Initiation Protocol
> Status-Line: SIP/2.0 100 Trying
> Status-Code: 100
> Message Header
> From: 12345678
> <sip:12345678sip.abc.com>;tag=e2ffc017e8f818109f1cafec866a1c9f
> To: <sip:12345678sip.abc.com>
> Call-ID: e2ffc017-e8f8-1810-8cb1-afec866a1c9f
> CSeq: 2 REGISTER
> Content-Length: 0
> Via: SIP/2.0/UDP
>
192.168.1.250:5060;iid=4033;branch=z9hG4bK170cc117e8f818109f
1cafec866a1c9f
>
>
> User Datagram Protocol, Src Port: 5060 (5060), Dst
Port: 5060 (5060)
> Session Initiation Protocol
> Status-Line: SIP/2.0 100 Trying
> Status-Code: 100
> Message Header
> From: 12345678
> <sip:12345678sip.abc.com>;tag=e2ffc017e8f818109f1cafec866a1c9f
> To: <sip:12345678sip.abc.com>
> Call-ID: e2ffc017-e8f8-1810-8cb1-afec866a1c9f
> CSeq: 2 REGISTER
> Server: Brekeke OnDO SIP Server (rev.172)
> Content-Length: 0
> Via: SIP/2.0/UDP
>
192.168.1.250:5060;iid=4033;branch=z9hG4bK170cc117e8f818109f
1cafec866a1c9f
>
>
> User Datagram Protocol, Src Port: 5060 (5060), Dst
Port: 5060 (5060)
> Session Initiation Protocol
> Status-Line: SIP/2.0 401 Unauthorized
> Status-Code: 401
> Message Header
> From: 12345678
> <sip:12345678sip.abc.com>;tag=e2ffc017e8f818109f1cafec866a1c9f
> To: <sip:12345678sip.abc.com>;tag=1181637698218-108102351
> Call-ID: e2ffc017-e8f8-1810-8cb1-afec866a1c9f
> CSeq: 2 REGISTER
> Server: Brekeke OnDO SIP Server (rev.172)
> WWW-Authenticate: Digest
>
realm="ABC-SIP",nonce="1f2d068b25fb75ab021e4e
d6d34e56a987bbc5f5"
> Content-Length: 0
> Via: SIP/2.0/UDP
>
192.168.1.250:5060;iid=4033;branch=z9hG4bK170cc117e8f818109f
1cafec866a1c9f
>
>
> User Datagram Protocol, Src Port: 5060 (5060), Dst
Port: 5060 (5060)
> Session Initiation Protocol
> Request-Line: REGISTER sip:sip.abc.com SIP/2.0
> Method: REGISTER
> Message Header
> From: 12345678
> <sip:12345678proxy.abc.com>;tag=3a4fc117e8f818109f1cafec866a1c9
f
> To: sip:12345678proxy.abc.com
> Via: SIP/2.0/UDP
>
192.168.1.250:5060;iid=4033;branch=z9hG4bK3a4fc117e8f818109f
1dafec866a1c9f;uas-addr=sip.abc.com;rport
>
> CSeq: 3 REGISTER
> Call-ID: e2ffc017-e8f8-1810-8cb1-afec866a1c9f
> Contact: "12345678"
> <sip:12345678192.168.1.250:5060;transport=udp>
> User-Agent: OpenSIPStack-1.1.6-134
> Expires: 60
> Max-Forwards: 10
> Authorization: Digest
username="12345678", realm="ABC-SIP",
>
nonce="1f2d068b25fb75ab021e4ed6d34e56a987bbc5f5",
> uri="sip:sip.abc.com",
response="8c563dd4d6cd556ad3696616fa53891c",
> algorithm=MD5
> Allow: INVITE, BYE, ACK, REFER, MESSAGE, INFO,
NOTIFY, OPTIONS
> Content-Length: 0
>
> User Datagram Protocol, Src Port: 5060 (5060), Dst
Port: 5060 (5060)
> Session Initiation Protocol
> Status-Line: SIP/2.0 100 Trying
> Status-Code: 100
> Message Header
> From: 12345678
> <sip:12345678sip.abc.com>;tag=3a4fc117e8f818109f1cafec866a1c9f
> To: <sip:12345678sip.abc.com>
> Call-ID: e2ffc017-e8f8-1810-8cb1-afec866a1c9f
> CSeq: 3 REGISTER
> Content-Length: 0
> Via: SIP/2.0/UDP
>
192.168.1.250:5060;iid=4033;branch=z9hG4bK3a4fc117e8f818109f
1dafec866a1c9f
>
>
> User Datagram Protocol, Src Port: 5060 (5060), Dst
Port: 5060 (5060)
> Session Initiation Protocol
> Status-Line: SIP/2.0 200 OK
> Status-Code: 200
> Message Header
> From: 12345678
> <sip:12345678sip.abc.com>;tag=3a4fc117e8f818109f1cafec866a1c9f
> To: <sip:12345678sip.abc.com>;tag=1181637698359-777144072
> Call-ID: e2ffc017-e8f8-1810-8cb1-afec866a1c9f
> CSeq: 3 REGISTER
> Server: Brekeke OnDO SIP Server (rev.172)
> Content-Length: 0
> Contact: <sip:12345678220.255.131.59:57880>;expires=59;q=1.0
> Via: SIP/2.0/UDP
>
192.168.1.250:5060;iid=4033;branch=z9hG4bK3a4fc117e8f818109f
1dafec866a1c9f
>
>
> User Datagram Protocol, Src Port: 5060 (5060), Dst
Port: 5060 (5060)
> Session Initiation Protocol
> Request-Line: REGISTER sip:sip.abc.com SIP/2.0
> Method: REGISTER
> Message Header
> From: 12345678
> <sip:12345678proxy.abc.com>;tag=e2ffc017e8f818109f1cafec866a1c9
f
> To: sip:12345678proxy.abc.com
> Via: SIP/2.0/UDP
>
192.168.1.250:5060;iid=4033;branch=z9hG4bK170cc117e8f818109f
1cafec866a1c9f;uas-addr=sip.abc.com;rport
>
> CSeq: 3 REGISTER
> Call-ID: e2ffc017-e8f8-1810-8cb1-afec866a1c9f
> Contact: "12345678"
> <sip:12345678192.168.1.250:5060;transport=udp>
> User-Agent: OpenSIPStack-1.1.6-134
> Expires: 60
> Max-Forwards: 10
> Allow: INVITE, BYE, ACK, REFER, MESSAGE, INFO,
NOTIFY, OPTIONS
> Content-Length: 0
>
> User Datagram Protocol, Src Port: 5060 (5060), Dst
Port: 5060 (5060)
> Session Initiation Protocol
> Status-Line: SIP/2.0 200 OK
> Status-Code: 200
> Message Header
> Via: SIP/2.0/UDP
>
192.168.1.250:5060;iid=4033;branch=z9hG4bK170cc117e8f818109f
1cafec866a1c9f;uas-addr=sip.abc.com;rport
>
> From: 12345678
> <sip:12345678sip.abc.com>;tag=e2ffc017e8f818109f1cafec866a1c9f
> To: <sip:12345678sip.abc.com>
> Call-ID: e2ffc017-e8f8-1810-8cb1-afec866a1c9f
> CSeq: 3 REGISTER
> Expires: 60
> Contact: "12345678"
> <sip:12345678220.255.131.59:57880;transport=udp>
> Content-Length: 0
>
> User Datagram Protocol, Src Port: 5060 (5060), Dst
Port: 5060 (5060)
> Session Initiation Protocol
> Request-Line: REGISTER sip:sip.abc.com SIP/2.0
> Method: REGISTER
> Message Header
> From: 12345678
> <sip:12345678proxy.abc.com>;tag=e2ffc017e8f818109f1cafec866a1c9
f
> To: sip:12345678proxy.abc.com
> Via: SIP/2.0/UDP
>
192.168.1.250:5060;iid=4033;branch=z9hG4bK170cc117e8f818109f
1cafec866a1c9f;uas-addr=sip.abc.com;rport
>
> CSeq: 3 REGISTER
> Call-ID: e2ffc017-e8f8-1810-8cb1-afec866a1c9f
> Contact: "12345678"
> <sip:12345678192.168.1.250:5060;transport=udp>
> User-Agent: OpenSIPStack-1.1.6-134
> Expires: 60
> Max-Forwards: 10
> Allow: INVITE, BYE, ACK, REFER, MESSAGE, INFO,
NOTIFY, OPTIONS
> Content-Length: 0
>
> User Datagram Protocol, Src Port: 5060 (5060), Dst
Port: 5060 (5060)
> Session Initiation Protocol
> Status-Line: SIP/2.0 200 OK
> Status-Code: 200
> Message Header
> Via: SIP/2.0/UDP
>
192.168.1.250:5060;iid=4033;branch=z9hG4bK170cc117e8f818109f
1cafec866a1c9f;uas-addr=sip.abc.com;rport
>
> From: 12345678
> <sip:12345678sip.abc.com>;tag=e2ffc017e8f818109f1cafec866a1c9f
> To: <sip:12345678sip.abc.com>
> Call-ID: e2ffc017-e8f8-1810-8cb1-afec866a1c9f
> CSeq: 3 REGISTER
> Expires: 60
> Contact: "12345678"
> <sip:12345678220.255.131.59:57880;transport=udp>
> Content-Length: 0
>
> User Datagram Protocol, Src Port: 5060 (5060), Dst
Port: 5060 (5060)
> Session Initiation Protocol
> Request-Line: REGISTER sip:sip.abc.com SIP/2.0
> Method: REGISTER
> Message Header
> From: 12345678
> <sip:12345678proxy.abc.com>;tag=e2ffc017e8f818109f1cafec866a1c9
f
> To: sip:12345678proxy.abc.com
> Via: SIP/2.0/UDP
>
192.168.1.250:5060;iid=4033;branch=z9hG4bK170cc117e8f818109f
1cafec866a1c9f;uas-addr=sip.abc.com;rport
>
> CSeq: 3 REGISTER
> Call-ID: e2ffc017-e8f8-1810-8cb1-afec866a1c9f
> Contact: "12345678"
> <sip:12345678192.168.1.250:5060;transport=udp>
> User-Agent: OpenSIPStack-1.1.6-134
> Expires: 60
> Max-Forwards: 10
> Allow: INVITE, BYE, ACK, REFER, MESSAGE, INFO,
NOTIFY, OPTIONS
> Content-Length: 0
>
> User Datagram Protocol, Src Port: 5060 (5060), Dst
Port: 5060 (5060)
> Session Initiation Protocol
> Status-Line: SIP/2.0 100 Trying
> Status-Code: 100
> Message Header
> From: 12345678
> <sip:12345678sip.abc.com>;tag=e2ffc017e8f818109f1cafec866a1c9f
> To: <sip:12345678sip.abc.com>
> Call-ID: e2ffc017-e8f8-1810-8cb1-afec866a1c9f
> CSeq: 3 REGISTER
> Content-Length: 0
> Via: SIP/2.0/UDP
>
192.168.1.250:5060;iid=4033;branch=z9hG4bK170cc117e8f818109f
1cafec866a1c9f
>
>
> User Datagram Protocol, Src Port: 5060 (5060), Dst
Port: 5060 (5060)
> Session Initiation Protocol
> Status-Line: SIP/2.0 100 Trying
> Status-Code: 100
> Message Header
> From: 12345678
> <sip:12345678sip.abc.com>;tag=e2ffc017e8f818109f1cafec866a1c9f
> To: <sip:12345678sip.abc.com>
> Call-ID: e2ffc017-e8f8-1810-8cb1-afec866a1c9f
> CSeq: 3 REGISTER
> Server: Brekeke OnDO SIP Server (rev.172)
> Content-Length: 0
> Via: SIP/2.0/UDP
>
192.168.1.250:5060;iid=4033;branch=z9hG4bK170cc117e8f818109f
1cafec866a1c9f
>
>
> User Datagram Protocol, Src Port: 5060 (5060), Dst
Port: 5060 (5060)
> Session Initiation Protocol
> Status-Line: SIP/2.0 401 Unauthorized
> Status-Code: 401
> Message Header
> From: 12345678
> <sip:12345678sip.abc.com>;tag=e2ffc017e8f818109f1cafec866a1c9f
> To: <sip:12345678sip.abc.com>;tag=1181637845812-299361820
> Call-ID: e2ffc017-e8f8-1810-8cb1-afec866a1c9f
> CSeq: 3 REGISTER
> Server: Brekeke OnDO SIP Server (rev.172)
> WWW-Authenticate: Digest
>
realm="ABC-SIP",nonce="d3aedb4f94b5767d4a8112
c4bce1b76787bbc5f5"
> Content-Length: 0
> Via: SIP/2.0/UDP
>
192.168.1.250:5060;iid=4033;branch=z9hG4bK170cc117e8f818109f
1cafec866a1c9f
>
>
> User Datagram Protocol, Src Port: 5060 (5060), Dst
Port: 5060 (5060)
> Session Initiation Protocol
> Request-Line: REGISTER sip:sip.abc.com SIP/2.0
> Method: REGISTER
> Message Header
> From: 12345678
> <sip:12345678proxy.abc.com>;tag=55c09d18e8f818109f1dafec866a1c9
f
> To: sip:12345678proxy.abc.com
> Via: SIP/2.0/UDP
>
192.168.1.250:5060;iid=4033;branch=z9hG4bK55c09d18e8f818109f
1eafec866a1c9f;uas-addr=sip.abc.com;rport
>
> CSeq: 3 REGISTER
> Call-ID: e2ffc017-e8f8-1810-8cb1-afec866a1c9f
> Contact: "12345678"
> <sip:12345678192.168.1.250:5060;transport=udp>
> User-Agent: OpenSIPStack-1.1.6-134
> Expires: 60
> Max-Forwards: 10
> Authorization: Digest
username="12345678", realm="ABC-SIP",
>
nonce="d3aedb4f94b5767d4a8112c4bce1b76787bbc5f5",
> uri="sip:sip.abc.com",
response="2e56ae47e95e1c23c792899b93c3480c",
> algorithm=MD5
> Allow: INVITE, BYE, ACK, REFER, MESSAGE, INFO,
NOTIFY, OPTIONS
> Content-Length: 0
>
> User Datagram Protocol, Src Port: 5060 (5060), Dst
Port: 5060 (5060)
> Session Initiation Protocol
> Status-Line: SIP/2.0 100 Trying
> Status-Code: 100
> Message Header
> From: 12345678
> <sip:12345678sip.abc.com>;tag=55c09d18e8f818109f1dafec866a1c9f
> To: <sip:12345678sip.abc.com>
> Call-ID: e2ffc017-e8f8-1810-8cb1-afec866a1c9f
> CSeq: 3 REGISTER
> Content-Length: 0
> Via: SIP/2.0/UDP
>
192.168.1.250:5060;iid=4033;branch=z9hG4bK55c09d18e8f818109f
1eafec866a1c9f
>
>
> User Datagram Protocol, Src Port: 5060 (5060), Dst
Port: 5060 (5060)
> Session Initiation Protocol
> Request-Line: REGISTER sip:sip.abc.com SIP/2.0
> Method: REGISTER
> Message Header
> From: 12345678
> <sip:12345678proxy.abc.com>;tag=e2ffc017e8f818109f1cafec866a1c9
f
> To: sip:12345678proxy.abc.com
> Via: SIP/2.0/UDP
>
192.168.1.250:5060;iid=4033;branch=z9hG4bK170cc117e8f818109f
1cafec866a1c9f;uas-addr=sip.abc.com;rport
>
> CSeq: 3 REGISTER
> Call-ID: e2ffc017-e8f8-1810-8cb1-afec866a1c9f
> Contact: "12345678"
> <sip:12345678192.168.1.250:5060;transport=udp>
> User-Agent: OpenSIPStack-1.1.6-134
> Expires: 60
> Max-Forwards: 10
> Allow: INVITE, BYE, ACK, REFER, MESSAGE, INFO,
NOTIFY, OPTIONS
> Content-Length: 0
>
> User Datagram Protocol, Src Port: 5060 (5060), Dst
Port: 5060 (5060)
> Session Initiation Protocol
> Status-Line: SIP/2.0 100 Trying
> Status-Code: 100
> Message Header
> From: 12345678
> <sip:12345678sip.abc.com>;tag=e2ffc017e8f818109f1cafec866a1c9f
> To: <sip:12345678sip.abc.com>
> Call-ID: e2ffc017-e8f8-1810-8cb1-afec866a1c9f
> CSeq: 3 REGISTER
> Content-Length: 0
> Via: SIP/2.0/UDP
>
192.168.1.250:5060;iid=4033;branch=z9hG4bK170cc117e8f818109f
1cafec866a1c9f
>
>
> User Datagram Protocol, Src Port: 5060 (5060), Dst
Port: 5060 (5060)
> Session Initiation Protocol
> Status-Line: SIP/2.0 100 Trying
> Status-Code: 100
> Message Header
> From: 12345678
> <sip:12345678sip.abc.com>;tag=e2ffc017e8f818109f1cafec866a1c9f
> To: <sip:12345678sip.abc.com>
> Call-ID: e2ffc017-e8f8-1810-8cb1-afec866a1c9f
> CSeq: 3 REGISTER
> Server: Brekeke OnDO SIP Server (rev.172)
> Content-Length: 0
> Via: SIP/2.0/UDP
>
192.168.1.250:5060;iid=4033;branch=z9hG4bK170cc117e8f818109f
1cafec866a1c9f
>
>
> User Datagram Protocol, Src Port: 5060 (5060), Dst
Port: 5060 (5060)
> Session Initiation Protocol
> Status-Line: SIP/2.0 401 Unauthorized
> Status-Code: 401
> Message Header
> From: 12345678
> <sip:12345678sip.abc.com>;tag=e2ffc017e8f818109f1cafec866a1c9f
> To: <sip:12345678sip.abc.com>;tag=1181637895359-733449722
> Call-ID: e2ffc017-e8f8-1810-8cb1-afec866a1c9f
> CSeq: 3 REGISTER
> Server: Brekeke OnDO SIP Server (rev.172)
> WWW-Authenticate: Digest
>
realm="ABC-SIP",nonce="a0a60cf1077568e0e0cc5b
fb7e15434a87bbc5f5"
> Content-Length: 0
> Via: SIP/2.0/UDP
>
192.168.1.250:5060;iid=4033;branch=z9hG4bK170cc117e8f818109f
1cafec866a1c9f
>
>
> User Datagram Protocol, Src Port: 5060 (5060), Dst
Port: 5060 (5060)
> Session Initiation Protocol
> Request-Line: REGISTER sip:sip.abc.com SIP/2.0
> Method: REGISTER
> Message Header
> From: 12345678
> <sip:12345678proxy.abc.com>;tag=3bf8e618e8f818109f1eafec866a1c9
f
> To: sip:12345678proxy.abc.com
> Via: SIP/2.0/UDP
>
192.168.1.250:5060;iid=4033;branch=z9hG4bK3bf8e618e8f818109f
1fafec866a1c9f;uas-addr=sip.abc.com;rport
>
> CSeq: 3 REGISTER
> Call-ID: e2ffc017-e8f8-1810-8cb1-afec866a1c9f
> Contact: "12345678"
> <sip:12345678192.168.1.250:5060;transport=udp>
> User-Agent: OpenSIPStack-1.1.6-134
> Expires: 60
> Max-Forwards: 10
> Authorization: Digest
username="12345678", realm="ABC-SIP",
>
nonce="a0a60cf1077568e0e0cc5bfb7e15434a87bbc5f5",
> uri="sip:sip.abc.com",
response="399329b9b96fec0dd29e87ef13035270",
> algorithm=MD5
> Allow: INVITE, BYE, ACK, REFER, MESSAGE, INFO,
NOTIFY, OPTIONS
> Content-Length: 0
>
> User Datagram Protocol, Src Port: 5060 (5060), Dst
Port: 5060 (5060)
> Session Initiation Protocol
> Status-Line: SIP/2.0 100 Trying
> Status-Code: 100
> Message Header
> From: 12345678
> <sip:12345678sip.abc.com>;tag=3bf8e618e8f818109f1eafec866a1c9f
> To: <sip:12345678sip.abc.com>
> Call-ID: e2ffc017-e8f8-1810-8cb1-afec866a1c9f
> CSeq: 3 REGISTER
> Content-Length: 0
> Via: SIP/2.0/UDP
>
192.168.1.250:5060;iid=4033;branch=z9hG4bK3bf8e618e8f818109f
1fafec866a1c9f
>
>
> User Datagram Protocol, Src Port: 5060 (5060), Dst
Port: 5060 (5060)
> Session Initiation Protocol
> Status-Line: SIP/2.0 504 Server Time-out
> Status-Code: 504
> Message Header
> From: 12345678
> <sip:12345678sip.abc.com>;tag=3bf8e618e8f818109f1eafec866a1c9f
> To: <sip:12345678sip.abc.com>
> Call-ID: e2ffc017-e8f8-1810-8cb1-afec866a1c9f
> CSeq: 3 REGISTER
> Content-Length: 0
> Via: SIP/2.0/UDP
>
192.168.1.250:5060;iid=4033;branch=z9hG4bK3bf8e618e8f818109f
1fafec866a1c9f
>
>
>
> lun Tong wrote:
>> Hi, Andrew:
>>
>> Regarding to your 3 questions, I think,
>>
>> 1. The reason CSeq is not changing is because they
are
>> re-transmissions. That also explains why Branch-ID
is not changing.
>> (Though I am not sure if it is required that the
Branch-ID should be
>> unique for different CSeqs. ) Did you see 200OK
sent back? Even if
>> 200OK was sent back, can you make sure that the UAC
got it?
>>
>> 2. Max-Forward could be any number less than 70.
>>
>> Regards.
>> Lun
>
>
> vivek krishna wrote:
>> Hi,
>> Can you please say what is the exact error
which
>> you get.Whether this request is rejected by the
server
>> or something else.
>>
>> Also are the 3 messages a retransmission or 3
separate
>> requests ???
>>
>> Can you send the complete log of the call.
>>
>> Regards,
>> vivek
>> --- Andrew Yu <andrewasiatel.com.sg> wrote:
>>
>>
>>> Dear Members,
>>>
>>> I need your kind assistance to point out in
what way
>>> this UAC is sending register request in
violation of RFC3261
>>> requirements. This UAC is using opensipstack
1.1.6.134.
>>>
>>> Here's what I've identified for violations:
>>>
>>> 1. CSeq is always 3
>>> 2. Max-Forwards should be 70
>>> 3. Branch-IDs in Via is not always unique,
and it
>>> has been reused in
>>> previous register requests. (Is it
alright to
>>> reuse branch-id from
>>> previous register request?)
>>>
>>> User Datagram Protocol, Src Port: 5060 (5060),
Dst
>>> Port: 5060 (5060)
>>> Session Initiation Protocol
>>> Request-Line: REGISTER sip:sip.abc.com
SIP/2.0
>>> Method: REGISTER
>>> Message Header
>>> From: 12345678
>>>
>> <sip:12345678proxy.abc.com>;tag=3bf8e618e8f818109f1eafec866a1c9
f
>>
>>> To: sip:12345678proxy.abc.com
>>> Via: SIP/2.0/UDP
>>>
>>
192.168.1.250:5060;iid=4033;branch=z9hG4bK3bf8e618e8f818109f
1fafec866a1c9f;uas-addr=sip.abc.com;rport
>>
>>
>>> CSeq: 3 REGISTER
>>> Call-ID:
>>> e2ffc017-e8f8-1810-8cb1-afec866a1c9f
>>> Contact: "12345678"
>>> <sip:12345678192.168.1.250:5060;transport=udp>
>>> User-Agent: OpenSIPStack-1.1.6-134
>>> Expires: 60
>>> Max-Forwards: 10
>>> Authorization: Digest
username="12345678",
>>> realm="ABC-SIP",
nonce="a0a60cf1077568e0e0cc5bfb7e15434a87bbc5f5",
>>> uri="sip:sip.abc.com",
response="399329b9b96fec0dd29e87ef13035270",
>>> algorithm=MD5
>>> Allow: INVITE, BYE, ACK, REFER,
MESSAGE,
>>> INFO, NOTIFY, OPTIONS
>>> Content-Length: 0
>>>
>>> User Datagram Protocol, Src Port: 5060 (5060),
Dst
>>> Port: 5060 (5060)
>>> Session Initiation Protocol
>>> Request-Line: REGISTER sip:sip.abc.com
SIP/2.0
>>> Method: REGISTER
>>> Message Header
>>> From: 12345678
>>>
>> <sip:12345678proxy.abc.com>;tag=e2ffc017e8f818109f1cafec866a1c9
f
>>
>>> To: sip:12345678proxy.abc.com
>>> Via: SIP/2.0/UDP
>>>
>>
192.168.1.250:5060;iid=4033;branch=z9hG4bK170cc117e8f818109f
1cafec866a1c9f;uas-addr=sip.abc.com;rport
>>
>>
>>> CSeq: 3 REGISTER
>>> Call-ID:
>>> e2ffc017-e8f8-1810-8cb1-afec866a1c9f
>>> Contact: "12345678"
>>> <sip:12345678192.168.1.250:5060;transport=udp>
>>> User-Agent: OpenSIPStack-1.1.6-134
>>> Expires: 60
>>> Max-Forwards: 10
>>> Allow: INVITE, BYE, ACK, REFER,
MESSAGE,
>>> INFO, NOTIFY, OPTIONS
>>> Content-Length: 0
>>>
>>> User Datagram Protocol, Src Port: 5060 (5060),
Dst
>>> Port: 5060 (5060)
>>> Session Initiation Protocol
>>> Request-Line: REGISTER sip:sip.abc.com
SIP/2.0
>>> Method: REGISTER
>>> Message Header
>>> From: 12345678
>>>
>> <sip:12345678proxy.smtelsip.com>;tag=e2ffc017e8f818109f1cafec86
6a1c9f
>>
>>> To: sip:12345678proxy.abc.com
>>> Via: SIP/2.0/UDP
>>>
>>
192.168.1.250:5060;iid=4033;branch=z9hG4bK170cc117e8f818109f
1cafec866a1c9f;uas-addr=sip.abc.com;rport
>>
>>
>>> CSeq: 3 REGISTER
>>> Call-ID:
>>> e2ffc017-e8f8-1810-8cb1-afec866a1c9f
>>> Contact: "12345678"
>>> <sip:12345678192.168.1.250:5060;transport=udp>
>>> User-Agent: OpenSIPStack-1.1.6-134
>>> Expires: 60
>>> Max-Forwards: 10
>>> Allow: INVITE, BYE, ACK, REFER,
MESSAGE,
>>> INFO, NOTIFY, OPTIONS
>>> Content-Length: 0
>>>
>>> --
>>> Cheers,
>>>
>>> Asiatel Singapore Pte Ltd
>>> Andrew Yu
>>>
>>> 19 Jalan Kilang Barat
>>> #06-01, Acetech Centre
>>> Singapore 159361
>>>
>>> Tel: +65 6271 8233
>>> Fax: +65 6274 4266
>>>
>>>
_______________________________________________
>>> This is the SIP Forum discussion mailing list
>>> TO UNSUBSCRIBE, or edit your delivery options,
>>> please visit
>>> http:
//sipforum.org/mailman/listinfo/discussion
>>> Post to the list at discussionsipforum.org
>>>
>>>
>>
>>
>>
>>
>>
____________________________________________________________
________________________
>>
>> Get the Yahoo! toolbar and be alerted to new email
wherever you're
>> surfing.
>> http://new.toolbar.yahoo.com/toolbar/features/mail/i
ndex.php
>>
>> __________ NOD32 2329 (20070614) Information
__________
>>
>> This message was checked by NOD32 antivirus
system.
>> http://www.eset.com
>>
>>
>>
>>
>
>
------------------------------
Message: 3
Date: Sat, 16 Jun 2007 00:21:49 +0800
From: Andrew Yu <andrewasiatel.com.sg>
Subject: Re: [SIPForum-discussion] A question on SIP
Registration
Interval
To: andrewasiatel.com.sg, discussionsipforum.org
Message-ID: <4672BC9D.6030704asiatel.com.sg>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Dear Member,
I'm appealing for advice & comments on this issue that
I'm facing.
Are the any precedence rules for SIP registeration
interval?
Which comes first?
1. Registrar dictated expiration interval or,
2. UAC configured expiration interval
Thanks.
--
Cheers,
Asiatel Singapore Pte Ltd
Andrew Yu
19 Jalan Kilang Barat
#06-01, Acetech Centre
Singapore 159361
Tel: +65 6271 8233
Fax: +65 6274 4266
Kaushik V Shah wrote:
I guess both are right. But first option has a side effect
that you just
mentioned.
Regards,
Kaushik
Andrew Yu wrote:
Hi Kaushik,
You're correct to point this out, the UA is carrying the new
expiration
interval set by the registrar everytime it is
re-registering. Is the UA
right to use the value dictated by the registrar or it
should registered
with same "configured" expiration value during
every re-registering?
Thanks.
kaushikncoretech.com wrote:
Hi Andrew,
I think the problem is related to REGISTER carrying
new expires value everytime it is Re-Registering.
If you can make device / client register with same
"configured"
expires value during every Re-Registering then it will
solve
your problem.
Regards,
Kaushik
Andrew Yu wrote:
> Hi Vijay & Onur,
>
> My appreciation for your kind response.
>
> Dear Members,
>
> Actually, I'm facing a problem where the sbc reduces
the requested
> expiration interval by 1sec until the UA expiration
interval reaches 1
> and deregister itself at expiration interval at 0. The
problem
> surfaced after a software upgrade was done on the sbc,
the vendor
> insist that there was nothing wrong and the UA should
re-register
> itself based on the configured re-register expiration
interval of the
> UA. Am I misunderstanding something? The weirdest thing
is that this
> does not affect linksys devices like PAP2. They just
re-register
> itself at its own pre-configured value.
>
> My appreciation if any nextone & cisco/linksys
trained engineers could
> response to my questions. The sbc is from nextone.
Thanks alot!
>
> User Datagram Protocol, Src Port: 5698 (5698), Dst
Port: 5060 (5060)
> Session Initiation Protocol
> Request-Line: REGISTER sip:sip.abc.com SIP/2.0
> Method: REGISTER
> [Resent Packet: False]
> Message Header
> Via: SIP/2.0/UDP
> 10.0.0.130:5698;branch=z9hG4bK0a0000825698-1470;rport
> From: sip:12345678sip.abc.com;tag=0A0000821642-805261B80
> To: sip:12345678sip.abc.com
> Call-ID: 1805261b82954a000082
> CSeq: 72 REGISTER
> User-Agent: SIP-6328-2Re-v8.0.3-12345678/v2.0
Enabled
> Contact:
"12345678"<sip:1234567810.0.0.130:5698>
> Expires: 2
> Max-Forwards: 70
> Content-Length: 0
>
> User Datagram Protocol, Src Port: 5060 (5060), Dst
Port: 5698 (5698)
> Session Initiation Protocol
> Status-Line: SIP/2.0 200 OK
> Status-Code: 200
> [Resent Packet: False]
> Message Header
> Via: SIP/2.0/UDP
>
10.0.0.130:5698;received=210.24.99.168;branch=z9hG4bK0a00008
25698-1470;rport
>
> From: <sip:12345678sip.abc.com>;tag=0A0000821642-805261B80
> To: <sip:12345678sip.abc.com>
> Call-ID: 1805261b82954a000082
> CSeq: 72 REGISTER
> Expires: 1
> Contact: "12345678"
<sip:6826769110.0.0.130:5698>
> Content-Length: 0
>
------------------------------
_______________________________________________
This is the SIP Forum discussion mailing list
TO UNSUBSCRIBE, or edit your delivery options, please visit
http:
//sipforum.org/mailman/listinfo/discussion
Post to the list at discussionsipforum.org
End of discussion Digest, Vol 23, Issue 23
******************************************
|
