[SIPForum-discussion] What all the SIP error codes can be sent before 180 ringing and after 180 ringing.

Sun Jan 8 16:47:14 UTC 2012

See if the attached trace helps you. I took a trace locally in my PC where
the call was made b/w 2 UAs from sip:192.168.1.2:5061 to sip:
192.168.1.2:5060.

Regards,
Rudra

On Sun, Jan 8, 2012 at 8:24 PM, vinay jain <vinjainv at gmail.com> wrote:

> Hi Rudra
>
>  THe scenerio u describe below is possible but here the response is 3xx .
> How 3xx  will be consider as a client /server error.  can U  define a
> scenerio  where a error code  4xx/5xx ( no 487 as this possible )  is
> possible after 180 ??
>
> Thanks
>
>
> On Wed, Jan 4, 2012 at 2:01 PM, Rudra Kant Kanth <rudra.k1 at gmail.com>wrote:
>
>> Hi Aniella,
>>
>> I was curious, what would happen in a situation when UAS is ready to
>> answer the call but has a Voice-Mail configured for it. So, assuming after
>> 3 or 4 riings, the call should go to the VM. In such a case, wouldn't there
>> be a 180 Ringing and then, a 3xx Redirect; thereafter this transaction
>> would be closed and finally a new INVITE being sent to the VM?
>> I couldn't test it immediately to see what all the messages are
>> exchanged, so thought of asking.
>>
>> Regards,
>> Rudra
>>
>>
>> On Wed, Jan 4, 2012 at 4:32 AM, Aniella Juverdeanu <
>> Aniella.Juverdeanu at telus.com> wrote:
>>
>>> Theoretically it might look possible when you read the overview in
>>> section 13.1 of RFC 3261 but when you read further you can see in section
>>> 13.2.2 that  actually 180 followed by non-2XX final response doesn’t make
>>> sense. Better be an early dialog followed by a non-2XX (like 183 with SDP
>>> when the caller can hear an announcement and then the call can be release
>>> with SIP error).****
>>>
>>> Also logically, when you would look at such trace it would look strange.
>>> If 180 was sent by UAS it should mean that it found the destination ready
>>> to receive the call. Eventually there would be ring no answer when a timer
>>> would be started and what node has a smaller timer could terminate this
>>> call setup.****
>>>
>>> If actually 180 is followed by a non-2XX final answer, I would have the
>>> UAS that serves the destination check this signaling – it doesn’t look
>>> right, it makes no telephony sense.****
>>>
>>> ** **
>>>
>>> Thanks,****
>>>
>>> Aniella ****
>>>
>>> ** **
>>>
>>> *From:* discussion-bounces at sipforum.org [mailto:
>>> discussion-bounces at sipforum.org] *On Behalf Of *Keyur Amin
>>> *Sent:* December 24, 2011 10:41 AM
>>> *To:* Rudra Kant Kanth; kondareddy godlaveety
>>> *Cc:* discussion at sipforum.org
>>>
>>> *Subject:* Re: [SIPForum-discussion] What all the SIP error codes can
>>> be sent before 180 ringing and after 180 ringing.****
>>>
>>> ** **
>>>
>>> I dont believe there is any restrictions on error responses followed by
>>> 180. I think, you can have any 4xx, 5xx or 6xx messages except for 487.*
>>> ***
>>>
>>>  ****
>>>
>>> *Thanks,*****
>>>
>>> *Keyur** **Amin*****
>>> ------------------------------
>>>
>>>  ****
>>>
>>>  ****
>>>
>>> ** **
>>> ------------------------------
>>>
>>> *From:* Rudra Kant Kanth <rudra.k1 at gmail.com>
>>> *To:* kondareddy godlaveety <kondareddi24 at gmail.com>
>>> *Cc:* discussion at sipforum.org
>>> *Sent:* Wednesday, December 21, 2011 9:26 PM
>>> *Subject:* Re: [SIPForum-discussion] What all the SIP error codes can
>>> be sent before 180 ringing and after 180 ringing.****
>>>
>>> After 180 Ringing, if the Callee rejects the call, you would see "*486
>>> Busy Here*". Attached is a sample trace for it.****
>>>
>>> ** **
>>>
>>> Regards,****
>>>
>>> Rudra****
>>>
>>> ** **
>>>
>>> ** **
>>>
>>> ** **
>>>
>>> On Wed, Dec 21, 2011 at 12:49 PM, kondareddy godlaveety <
>>> kondareddi24 at gmail.com> wrote:****
>>>
>>> Hi,****
>>>
>>>  ****
>>>
>>> Can any one help me out with the follwing scenario.****
>>>
>>>  ****
>>>
>>>  ****
>>>
>>> can we send 4xx client error codes after sending 180 ringing?****
>>>
>>>  ****
>>>
>>> 1. if so what all the 4xx SIP error codes can be sent before SIP:180 and
>>> after SIP:180?****
>>>
>>>  ****
>>>
>>> Can we send 5xx server Error codes after seding 180 ringing?****
>>>
>>>  ****
>>>
>>> 2. if so what all the 5xx SIP error codes can be sent before SIP:180
>>> ringing and after SIP:180?****
>>>
>>>  ****
>>>
>>> Can we send 6xx Global error codes after 180 ringing?****
>>>
>>>  ****
>>>
>>> 3. If so what all the 6xx error codes can be sent before 180 ringing and
>>> after SIP:180 ringing?****
>>>
>>>  ****
>>>
>>>  ****
>>>
>>> Regards,****
>>>
>>> Kondareddy****
>>>
>>>
>>> _______________________________________________
>>> 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
>>>
>>> ****
>>>
>>
>>
>> _______________________________________________
>> 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
>>
>>
>
>
> --
> Vinay Kumar Jain
> Bangalore
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20120108/c88797dc/attachment-0002.html>
-------------- next part --------------
22:12:49.156 : INVITE : sip:192.168.1.2:5060
Outgoing Message.

UDP (reliable=false): ip=192.168.1.2, port=5060, plugin=null, forceUDP=false, TTL=1

INVITE sip:192.168.1.2:5060 SIP/2.0
Call-ID: 1315240936266959332 at 192.168.1.2
Content-Length: 118
Content-Type: application/sdp
To: sip:192.168.1.2:5060
From: sip:sip:148;tag=1409967444
Contact: sip:192.168.1.2:5061
CSeq: 1 INVITE
Max-Forwards: 70
Via: SIP/2.0/UDP 192.168.1.2:5061;branch=z9hG4bKC0A80102BADF00D00000134BE32E7994

v=0
o=- 1326040969140 1326040969140 IN IP4 192.168.1.2
s=-
c=IN IP4 192.168.1.2
t=0 0
m=audio 51980 RTP/AVP 8 0

========================================

22:12:49.281 : SIP/2.0 100 Trying
Incoming Message.

UDP (reliable=false): ip=192.168.1.2, port=4554, plugin=null, forceUDP=false, TTL=1

SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.1.2:5061;branch=z9hG4bKC0A80102BADF00D00000134BE32E7994
To: sip:192.168.1.2:5060
From: sip:sip:148;tag=1409967444
Call-ID: 1315240936266959332 at 192.168.1.2
CSeq: 1 INVITE
Server:  
Content-Length: 0

========================================

22:12:49.343 : SIP/2.0 180 Ringing
Incoming Message.

UDP (reliable=false): ip=192.168.1.2, port=4555, plugin=null, forceUDP=false, TTL=1

SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 192.168.1.2:5061;branch=z9hG4bKC0A80102BADF00D00000134BE32E7994
To: sip:192.168.1.2:5060;tag=-674725534
From: sip:sip:148;tag=1409967444
Call-ID: 1315240936266959332 at 192.168.1.2
CSeq: 1 INVITE
Content-Type: application/sdp
Contact: sip:192.168.1.2:5060
Server:  
Content-Length: 0

========================================

22:12:55.140 : SIP/2.0 486 Busy Here
Incoming Message.

UDP (reliable=false): ip=192.168.1.2, port=4553, plugin=null, forceUDP=false, TTL=1

SIP/2.0 486 Busy Here
Via: SIP/2.0/UDP 192.168.1.2:5061;branch=z9hG4bKC0A80102BADF00D00000134BE32E7994
To: sip:192.168.1.2:5060;tag=-674725534
From: sip:sip:148;tag=1409967444
Call-ID: 1315240936266959332 at 192.168.1.2
CSeq: 1 INVITE
Content-Type: application/sdp
Contact: sip:192.168.1.2:5060
Server:  
Content-Length: 0

========================================

22:12:55.172 : ACK : sip:192.168.1.2:5060
Outgoing Message.

UDP (reliable=false): ip=192.168.1.2, port=5060, plugin=null, forceUDP=false, TTL=1

ACK sip:192.168.1.2:5060 SIP/2.0
To: sip:192.168.1.2:5060;tag=-674725534
From: sip:sip:148;tag=1409967444
Call-ID: 1315240936266959332 at 192.168.1.2
CSeq: 1 ACK
Max-Forwards: 70
Content-Length: 0
Via: SIP/2.0/UDP 192.168.1.2:5061;branch=z9hG4bKC0A80102BADF00D00000134BE32E7994

========================================