[SIPForum-discussion] getting 481 after sending bye msgg

[dhananjay.sahoo at wipro.com]

481 response is sent when request and response fall out of a common transaction:
 
You can check if the to tag and from tag in BYE is the same as 200 ok or not. Additionally you could also look at the cseq of BYE.
 
-Thanks,
Dhananjay
 

________________________________

From: discussion-bounces at sipforum.org [mailto:discussion-bounces at sipforum.org] On Behalf Of ajay more
Sent: Sunday, June 15, 2008 10:16 PM
To: Andrea Puddu
Cc: discussion at sipforum.org
Subject: Re: [SIPForum-discussion] getting 481 after sending bye msgg


in same case if a party disconnecting call then call realesed with OK. But if b party disconects call, getting error 481 in reply.
 
kindly comment.


On Sun, Jun 15, 2008 at 10:01 PM, ajay more <etrx.ajay at gmail.com> wrote:


	yes i am using same call id in all massages.
	 
	then what will be the reason?
	 
	Rgds,
	Ajay
	
	
	On Sun, Jun 15, 2008 at 7:10 PM, Andrea Puddu <androjoker at hotmail.com> wrote:
	

		Hello,
		
		In the BYE request make sure you are using the same Call-id , used in INVITE, 180 Ringing ....
		
		Regards,
		
		Andrea
		
		
		

________________________________

			Date: Sun, 15 Jun 2008 18:01:51 +0530
			From: etrx.ajay at gmail.com
			To: discussion at sipforum.org
			Subject: [SIPForum-discussion] getting 481 after sending bye msgg 



			Dear all,
			 
			        We are facing the problem while disconnecting call. When call is disconnected from B party i.e from our side (we are sending req: Bye),
			instead of getting OK, we are getting status: 481 transaction id not found.
			 
			what will be this problem?
			 
			 
			kindly comment.
			 
			thanks,
			Ajay


________________________________

		Windows Live Mail Controlla i tuoi account di posta con un unico programma, è GRATIS! <http://get.live.com/wlmail/overview> 



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20080616/611b94fb/attachment-0002.html>