[SIPForum-discussion] SIP UPDATE and SIP 481
Gyorgy Kovacs
gykovacs.datanet at gmail.com
Wed Dec 4 23:33:17 UTC 2013
Different thread, but here it is:
RFC 3261 10.2.1.1 Setting the Expiration Interval of Contact Addresses
There are two ways in which a client can suggest an expiration
interval for a binding: through an Expires header field or an
"expires" Contact header parameter. The latter allows expiration
intervals to be suggested on a per-binding basis when more than one
binding is given in a single REGISTER request, whereas the former
suggests an expiration interval for all Contact header field values
that do not contain the "expires" parameter.
If neither mechanism for expressing a suggested expiration time is
present in a REGISTER, the client is indicating its desire for the
server to choose.
RFC 3261 10.3 Processing REGISTER Requests
When receiving a REGISTER request, a registrar follows these steps:
[...]
7. The registrar now processes each contact address in the Contact
header field in turn. For each address, it determines the
expiration interval as follows:
- If the field value has an "expires" parameter, that value
MUST be taken as the requested expiration.
- If there is no such parameter, but the request has an
Expires header field, that value MUST be taken as the
requested expiration.
- If there is neither, a locally-configured default value MUST
be taken as the requested expiration.
Regards,
Gyorgy
On Fri, 2013-11-29 at 14:22 +0530, Pravat Panda wrote:
> Hi Guys ,
>
>
> Can you explain me In the REGISTER Request , one header is Expire and
> one parameter also expire which will be in the Contact header.
>
>
> Can you explain on that , expire parameter as well as Expire Header ,
> both are mandatory ?
>
>
> Thanks , waiting for your kind response.
>
>
> On Sat, Nov 23, 2013 at 6:42 PM, srinath <mailingsri at yahoo.co.in>
> wrote:
> Dear Friends,
>
> Is the issue due to PORT difference in UDP of UPDATE
> message?.
>
> User Datagram Protocol, Src Port: 58521 (58521), Dst Port: sip
> (5060)
>
>
> Regards,
>
> Srinath R
>
>
> --------------------------------------------
> On Sat, 23/11/13, Keyur Amin <fossil0681 at yahoo.com> wrote:
>
> Subject: Re: [SIPForum-discussion] SIP UPDATE and SIP 481
>
> To: "Fatih Küçük" <mfatihkucuk at gmail.com>, "Srinivasa Rao
> Kandimalla" <srini.kandimalla at gmail.com>
> Cc: "SIP FORUM" <discussion at sipforum.org>
> Date: Saturday, 23 November, 2013, 12:18 AM
>
> This may be due to
> the CSeq value in UPDATE, causing the 481 response. Section
> 12.2.1.1 from RFC 3261.
> Requests
> within a dialog MUST contain strictly monotonically
> increasing and contiguous CSeq sequence numbers
> (increasing-by-one)
> in each direction (excepting ACK and CANCEL of course,
> whose numbers
> equal the requests being acknowledged or cancelled).
> Therefore, if
> the local sequence number is not empty, the value of the
> local
> sequence number MUST be incremented by one, and this
> value MUST be
> placed into the CSeq header field. If the local
> sequence number is
> empty, an initial value MUST be chosen using the
> guidelines of
> Section 8.1.1.5. The method field in the CSeq header
> field value
> MUST match the method of the
> request. Thanks,Keyur Amin
>
>
> On Wednesday, November 20, 2013 12:07 PM,
> Fatih Küçük <mfatihkucuk at gmail.com> wrote:
> Dear Guys,
> Even though i already explained it
> to Bilal, this is a well known bug of Genband S3 v5.2, once
> upgraded it will be solved. No need to spend your valuable
> time to find out the reason.
>
> Regards,
> Fatih Kücük
>
>
> 2013/11/4 Srinivasa Rao
> Kandimalla <srini.kandimalla at gmail.com>
>
> I am not seeing ACK to 200 OK ( of INVITE ) in
> your traces before UPADTE. It means dialog is not fully
> establish. So, your device is sending UPDATE before dialog
> fully establish. UPDATE is to update the params with in the
> dialog. Please check for why device is sending UPDATE before
> ACK for 200 OK is received. That's why it says, not
> DIALOG exist.
>
>
> --------> INVITE
> ----------><---------183 Session Progress
>
> ----------------- PRACK
> ----------------------><---------- 200 OK
> --------------------
>
>
> <----------- UPDATE coming before ACK below
> Tx----------
> ---------ACK is missing
> --------------->
>
>
>
>
> On Sat, Nov 2, 2013 at 7:20 AM, Bilal Javed
> <bilaljaved1986 at gmail.com>
> wrote:
>
>
> Hi
> Gents,
>
> Please
> describe how to handle SIP UPDATE Message as Device A is
> giving SIP 481 Call Leg/Transaction doesn't exist when
> Device B replied with SIP UPDATE request. After that it is
> SIP 487 request Terminated by Device A.
>
>
>
>
> Please advice how to trouble shoot
> this.
>
>
> Device A: A.A.A.A ( Genband )
> Calling Number : AAAAAAAA
> Device B : B.B.B.B ( Cisco )
> Called Number : BBBBBBBB
>
>
>
>
>
>
>
>
>
>
>
> Below is full trace
>
>
>
> No.
> Time
> Source
> Destination
> Protocol Length Info
> 1
> 0.000000
> A.A.A.A
> B.B.B.B
> SIP/SDP 1190 Request: INVITE
> sip:BBBBBBBBBBBBB at B.B.B.B:5060 |
>
>
>
>
> Frame 1: 1190 bytes on wire (9520 bits),
> 1190 bytes captured (9520 bits)
> Ethernet II,
> Src: Cisco_12:02:00 (58:8d:09:12:02:00), Dst:
> DellEsgP_f8:30:a0 (00:18:8b:f8:30:a0)
> Internet Protocol Version 4, Src: A.A.A.A
> (A.A.A.A), Dst: B.B.B.B (B.B.B.B)
>
>
>
> User Datagram Protocol, Src Port: sip (5060), Dst Port: sip
> (5060)
> Session Initiation Protocol
> (INVITE)
> Request-Line:
> INVITE sip:BBBBBBBBBBBBB at B.B.B.B:5060 SIP/2.0
>
> Method: INVITE
>
> Request-URI: sip:BBBBBBBBBBBBB at B.B.B.B:5060
>
>
>
> [Resent Packet:
> False]
> Message Header
>
> Max-Forwards: 69
>
> Session-Expires: 3600;refresher=uac
>
> Min-SE: 600
>
> Supported: timer, 100rel
> To:
> <sip:BBBBBBBBBBBBB at A.A.A.A:5060>
>
>
>
> From:
> "Test"
> <sip:AAAAAAAAA at A.A.A.A>;tag=3592034893-396218
>
> Remote-Party-Id: "Test"
> <sip:AAAAAAAAA at A.A.A.A>;privacy=off;screen=no
>
> Call-ID: 9172982-3592034893-396212 at fmnt1.voip-termination.net
>
>
>
> CSeq: 1 INVITE
>
> Allow: INVITE, BYE, OPTIONS, CANCEL, ACK, REGISTER, NOTIFY,
> INFO, REFER, SUBSCRIBE, PRACK, UPDATE, MESSAGE, PUBLISH
> Via:
> SIP/2.0/UDP
> A.A.A.A:5060;branch=z9hG4bK5b33d213f44c5363089a303a22ae7647
>
>
>
> Contact:
> <sip:AAAAAAAAA at A.A.A.A:5060;tgrp=trk>
>
> Call-Info:
> <sip:A.A.A.A>;method="NOTIFY;Event=telephone-event;Duration=1000"
>
> Content-Type: application/sdp
>
> Content-Length: 302
>
>
>
> Message Body
>
> No.
> Time
> Source
> Destination
> Protocol Length Info
> 2
> 0.027758
> B.B.B.B
> A.A.A.A
> SIP 481
> Status: 100 Trying |
>
> Frame
> 2: 481 bytes on wire (3848 bits), 481 bytes captured (3848
> bits)
>
>
>
> Ethernet II, Src: IntelCor_28:de:b0 (a0:36:9f:28:de:b0),
> Dst: Cisco_12:02:00 (58:8d:09:12:02:00)
> 802.1Q Virtual LAN, PRI: 0, CFI: 0, ID: 2
> Internet Protocol Version 4, Src: B.B.B.B
> (B.B.B.B), Dst: A.A.A.A (A.A.A.A)
>
>
>
> User Datagram Protocol, Src Port: sip (5060), Dst Port: sip
> (5060)
> Session Initiation Protocol
> (100)
> Status-Line:
> SIP/2.0 100 Trying
>
> Status-Code: 100
>
> [Resent Packet: False]
>
>
>
> [Request Frame:
> 1]
>
> [Response Time (ms): 27]
>
> Message Header
> Via:
> SIP/2.0/UDP
> A.A.A.A:5060;branch=z9hG4bK5b33d213f44c5363089a303a22ae7647
>
> From: "Test"
> <sip:AAAAAAAAA at A.A.A.A>;tag=3592034893-396218
>
>
>
> To:
> <sip:BBBBBBBBBBBBB at A.A.A.A:5060>
>
> Date: Tue, 29 Oct 2013 11:28:13 GMT
>
> Call-ID: 9172982-3592034893-396212 at test.net
>
>
> Server:
> Cisco-SIPGateway/IOS-12.x
>
> CSeq: 1 INVITE
>
> Allow-Events: telephone-event
>
> Content-Length: 0
>
> No.
> Time
> Source
> Destination
> Protocol Length Info
> 3
> 3.914438
> B.B.B.B
> A.A.A.A SIP/SDP
> 1173 Status: 183 Session Progress |
>
>
>
>
> Frame 3: 1173 bytes on wire (9384 bits),
> 1173 bytes captured (9384 bits)
> Ethernet II,
> Src: IntelCor_28:de:b0 (a0:36:9f:28:de:b0), Dst:
> Cisco_12:02:00 (58:8d:09:12:02:00)
> 802.1Q
> Virtual LAN, PRI: 0, CFI: 0, ID: 2
>
>
>
> Internet Protocol Version 4, Src: B.B.B.B (B.B.B.B), Dst:
> A.A.A.A (A.A.A.A)
> User Datagram Protocol,
> Src Port: sip (5060), Dst Port: sip (5060)
> Session Initiation Protocol (183)
> Status-Line: SIP/2.0 183
> Session Progress
>
>
>
> Status-Code:
> 183
>
> [Resent Packet: False]
>
> [Request Frame: 1]
>
> [Response Time (ms): 3915]
> Message Header
> Via:
> SIP/2.0/UDP
> A.A.A.A:5060;branch=z9hG4bK5b33d213f44c5363089a303a22ae7647
>
>
>
> From:
> "Test"
> <sip:AAAAAAAAA at A.A.A.A>;tag=3592034893-396218
> To:
> <sip:BBBBBBBBBBBBB at A.A.A.A:5060>;tag=1E0FD10-179D
>
> Date: Tue, 29 Oct 2013 11:28:13 GMT
>
> Call-ID: 9172982-3592034893-396212 at test.net
>
>
>
> Server:
> Cisco-SIPGateway/IOS-12.x
>
> CSeq: 1 INVITE
>
> Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE,
> REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
>
> Require: 100rel
>
> RSeq: 3061
>
>
>
> Allow-Events:
> telephone-event
>
> Remote-Party-ID:
> <sip:BBBBBBBBBBBBB at B.B.B.B>;party=called;screen=no;privacy=off
>
> Contact: <sip:BBBBBBBBBBBBB at B.B.B.B:5060>
>
> Content-Type: application/sdp
>
>
>
>
> Content-Disposition: session;handling=required
>
> Content-Length: 318
>
> Message Body
>
> No.
> Time
> Source
> Destination
> Protocol Length Info
> 4
> 4.035929
> A.A.A.A
> B.B.B.B
> SIP 640
> Request: PRACK sip:BBBBBBBBBBBBB at B.B.B.B:5060 |
>
>
>
>
> Frame 4: 640 bytes on wire (5120 bits), 640
> bytes captured (5120 bits)
> Ethernet II, Src:
> Cisco_12:02:00 (58:8d:09:12:02:00), Dst: DellEsgP_f8:30:a0
> (00:18:8b:f8:30:a0)
> Internet Protocol
> Version 4, Src: A.A.A.A (A.A.A.A), Dst: B.B.B.B (B.B.B.B)
>
>
>
> User Datagram Protocol, Src Port: sip (5060), Dst Port: sip
> (5060)
> Session Initiation Protocol
> (PRACK)
> Request-Line:
> PRACK sip:BBBBBBBBBBBBB at B.B.B.B:5060 SIP/2.0
>
> Method: PRACK
>
> Request-URI: sip:BBBBBBBBBBBBB at B.B.B.B:5060
>
>
>
> [Resent Packet:
> False]
> Message Header
>
> Max-Forwards: 70
>
> RAck: 3061 1 INVITE
> To:
> <sip:BBBBBBBBBBBBB at A.A.A.A:5060>;tag=1E0FD10-179D
>
> From: "Test"
> <sip:AAAAAAAAA at A.A.A.A>;tag=3592034893-396218
>
>
>
> Call-ID: 9172982-3592034893-396212 at test.net
>
> CSeq: 2 PRACK
>
> Allow: INVITE, BYE, OPTIONS, CANCEL, ACK, REGISTER, NOTIFY,
> INFO, REFER, SUBSCRIBE, PRACK, UPDATE, MESSAGE, PUBLISH
>
>
>
> Via: SIP/2.0/UDP
> A.A.A.A:5060;branch=z9hG4bK56882666de3a53cb7fa4d1ed2eaa857f
>
> Contact: <sip:AAAAAAAAA at A.A.A.A:5060;tgrp=trk>
>
> Content-Length: 0
>
> No.
> Time
> Source
> Destination
> Protocol Length Info
>
>
>
> 5 4.037925
> B.B.B.B
> A.A.A.A
> SIP 462
> Status: 200 OK |
>
> Frame 5:
> 462 bytes on wire (3696 bits), 462 bytes captured (3696
> bits)
> Ethernet II, Src: IntelCor_28:de:b0
> (a0:36:9f:28:de:b0), Dst: Cisco_12:02:00
> (58:8d:09:12:02:00)
>
>
>
> 802.1Q Virtual LAN, PRI: 0, CFI: 0, ID: 2
> Internet Protocol Version 4, Src: B.B.B.B
> (B.B.B.B), Dst: A.A.A.A (A.A.A.A)
> User
> Datagram Protocol, Src Port: sip (5060), Dst Port: sip
> (5060)
> Session Initiation Protocol
> (200)
>
>
>
> Status-Line: SIP/2.0 200 OK
>
> Status-Code: 200
>
> [Resent Packet: False]
>
> [Request Frame: 4]
>
> [Response Time (ms): 1]
>
> Message Header
> Via:
> SIP/2.0/UDP
> A.A.A.A:5060;branch=z9hG4bK56882666de3a53cb7fa4d1ed2eaa857f
>
>
>
> From:
> "Test"
> <sip:AAAAAAAAA at A.A.A.A>;tag=3592034893-396218
> To:
> <sip:BBBBBBBBBBBBB at A.A.A.A:5060>;tag=1E0FD10-179D
>
> Date: Tue, 29 Oct 2013 11:28:17 GMT
>
> Call-ID: 9172982-3592034893-396212 at test.net
>
>
>
> Server:
> Cisco-SIPGateway/IOS-12.x
>
> CSeq: 2 PRACK
>
> Content-Length: 0
>
> No.
> Time
> Source
> Destination
> Protocol Length Info
> 6
> 4.038134
> B.B.B.B
> A.A.A.A
> SIP 674
> Request: UPDATE sip:AAAAAAAAA at A.A.A.A:5060;tgrp=trk |
>
>
>
>
> Frame 6: 674 bytes on wire (5392 bits), 674
> bytes captured (5392 bits)
> Ethernet II, Src:
> IntelCor_28:de:b0 (a0:36:9f:28:de:b0), Dst: Cisco_12:02:00
> (58:8d:09:12:02:00)
> 802.1Q Virtual LAN, PRI:
> 0, CFI: 0, ID: 2
>
>
>
> Internet Protocol Version 4, Src: B.B.B.B (B.B.B.B), Dst:
> A.A.A.A (A.A.A.A)
> User Datagram Protocol,
> Src Port: 58521 (58521), Dst Port: sip (5060)
> Session Initiation Protocol
> (UPDATE)
>
> Request-Line: UPDATE
> sip:AAAAAAAAA at A.A.A.A:5060;tgrp=trk SIP/2.0
>
>
>
> Method: UPDATE
>
> Request-URI: sip:AAAAAAAAA at A.A.A.A:5060;tgrp=trk
>
> [Resent Packet: False]
>
> Message Header
> Via:
> SIP/2.0/UDP B.B.B.B:5060;branch=z9hG4bK11784F
>
> From:
> <sip:BBBBBBBBBBBBB at A.A.A.A:5060>;tag=1E0FD10-179D
>
>
>
> To:
> "Test"
> <sip:AAAAAAAAA at A.A.A.A>;tag=3592034893-396218
>
> Date: Tue, 29 Oct 2013 11:28:17 GMT
>
> Call-ID: 9172982-3592034893-396212 at test.net
>
>
>
> User-Agent:
> Cisco-SIPGateway/IOS-12.x
>
> Max-Forwards: 70
>
> Timestamp: 1383046097
>
> CSeq: 101 UPDATE
>
> Contact: <sip:BBBBBBBBBBBBB at B.B.B.B:5060>
>
> Remote-Party-ID:
> <sip:14421874040755546089 at B.B.B.B>;party=calling;screen=no;privacy=off
>
>
>
> Content-Length:
> 0
>
> No.
> Time
> Source
> Destination
> Protocol Length Info
> 7
> 4.159037
> A.A.A.A
> B.B.B.B
> SIP 390
> Status: 481 CallLeg/Transaction doesnt exist |
>
>
>
>
> Frame 7: 390 bytes on wire (3120 bits), 390
> bytes captured (3120 bits)
> Ethernet II, Src:
> Cisco_12:02:00 (58:8d:09:12:02:00), Dst: DellEsgP_f8:30:a0
> (00:18:8b:f8:30:a0)
> Internet Protocol
> Version 4, Src: A.A.A.A (A.A.A.A), Dst: B.B.B.B (B.B.B.B)
>
>
>
> User Datagram Protocol, Src Port: sip (5060), Dst Port: sip
> (5060)
> Session Initiation Protocol
> (481)
>
> Status-Line: SIP/2.0 481 CallLeg/Transaction doesnt
> exist
>
> Status-Code: 481
>
>
>
> [Resent Packet:
> False]
> Message Header
> Via:
> SIP/2.0/UDP B.B.B.B:5060;branch=z9hG4bK11784F
>
> From:
> <sip:BBBBBBBBBBBBB at A.A.A.A:5060>;tag=1E0FD10-179D
> To:
> "Test"
> <sip:AAAAAAAAA at A.A.A.A>;tag=3592034893-396218
>
>
>
> Call-ID: 9172982-3592034893-396212 at test.net
>
> CSeq: 101 UPDATE
>
> Content-Length: 0
>
> No.
> Time
> Source
> Destination
> Protocol Length Info
>
>
>
> 8 4.160964
> B.B.B.B
> A.A.A.A
> SIP 431
> Status: 487 Request Cancelled |
>
> Frame 8: 431 bytes on wire (3448 bits), 431
> bytes captured (3448 bits)
> Ethernet II, Src:
> IntelCor_28:de:b0 (a0:36:9f:28:de:b0), Dst: Cisco_12:02:00
> (58:8d:09:12:02:00)
>
>
>
> 802.1Q Virtual LAN, PRI: 0, CFI: 0, ID: 2
> Internet Protocol Version 4, Src: B.B.B.B
> (B.B.B.B), Dst: A.A.A.A (A.A.A.A)
> User
> Datagram Protocol, Src Port: sip (5060), Dst Port: sip
> (5060)
> Session Initiation Protocol
> (487)
>
>
>
> Status-Line: SIP/2.0 487 Request
> Cancelled
>
> Status-Code: 487
>
> [Resent Packet: False]
>
> Message Header
> Via:
> SIP/2.0/UDP
> A.A.A.A:5060;branch=z9hG4bK5b33d213f44c5363089a303a22ae7647
>
>
>
> From:
> "Test"
> <sip:AAAAAAAAA at A.A.A.A>;tag=3592034893-396218
> To:
> <sip:BBBBBBBBBBBBB at A.A.A.A:5060>;tag=1E0FD10-179D
>
> Call-ID: 9172982-3592034893-396212 at test.net
>
>
>
> CSeq: 1 INVITE
>
> Reason: Q.850;cause=127
>
> Content-Length: 0
>
> No.
> Time
> Source
> Destination
> Protocol Length Info
> 9
> 4.281920
> A.A.A.A
> B.B.B.B
> SIP 615
> Request: ACK sip:BBBBBBBBBBBBB at B.B.B.B:5060 |
>
>
>
>
> Frame 9: 615 bytes on wire (4920 bits), 615
> bytes captured (4920 bits)
> Ethernet II, Src:
> Cisco_12:02:00 (58:8d:09:12:02:00), Dst: DellEsgP_f8:30:a0
> (00:18:8b:f8:30:a0)
> Internet Protocol
> Version 4, Src: A.A.A.A (A.A.A.A), Dst: B.B.B.B (B.B.B.B)
>
>
>
> User Datagram Protocol, Src Port: sip (5060), Dst Port: sip
> (5060)
> Session Initiation Protocol
> (ACK)
> Request-Line: ACK
> sip:BBBBBBBBBBBBB at B.B.B.B:5060 SIP/2.0
>
> Method: ACK
>
> Request-URI: sip:BBBBBBBBBBBBB at B.B.B.B:5060
>
>
>
> [Resent Packet:
> False]
>
> [Request Frame: 7]
>
> [Response Time (ms): 245]
>
> Message Header
>
> Max-Forwards: 70
> To:
> <sip:BBBBBBBBBBBBB at A.A.A.A:5060>;tag=1E0FD10-179D
>
>
>
> From:
> "Test"
> <sip:AAAAAAAAA at A.A.A.A>;tag=3592034893-396218
>
> Call-ID: 9172982-3592034893-396212 at test.net
>
> CSeq: 1 ACK
>
>
> Allow: INVITE,
> BYE, OPTIONS, CANCEL, ACK, REGISTER, NOTIFY, INFO, REFER,
> SUBSCRIBE, PRACK, UPDATE, MESSAGE, PUBLISH
>
> Via: SIP/2.0/UDP
> A.A.A.A:5060;branch=z9hG4bK5b33d213f44c5363089a303a22ae7647
>
> Contact: <sip:AAAAAAAAA at A.A.A.A:5060;tgrp=trk>
>
> Content-Length: 0
>
>
> Please assist in this matter. Thank you
> and have a nice weekend.
>
>
>
>
> Regards,
> Bilal
>
>
> _______________________________________________
>
> 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 discussion at sipforum.org
>
>
>
>
>
> _______________________________________________
>
> 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 discussion at sipforum.org
>
>
>
>
>
> --
>
> Saygılarımla,
> Fatih Kucuk
>
> _______________________________________________
> 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 discussion at sipforum.org
>
>
>
>
> -----Inline Attachment Follows-----
>
> _______________________________________________
> 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 discussion at sipforum.org
>
>
> _______________________________________________
> 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 discussion at sipforum.org
>
>
>
>
>
> --
> ---
> Best Regards
> Pravat Kumar Panda
> _______________________________________________
> 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 discussion at sipforum.org
More information about the discussion
mailing list