[SIPForum-discussion] Call with a Invite after 200OK

[Shashank Pandey]

HI All ,

 

              As jyoti said maxptime is increaseased thats correct that what reinvite for .
 
              but why this reinvite  is needed with increased maxptime  increased that needs
              to  taken care ,  
 
        in my view  media dialog in not happening propery with initial invite parameters thats 
        why reinvite is send with increased maxptime . at last we are getting 481 .
 
        So i conculde that issue with only network ( bandwidth).  Thats the reason Re-Invite is send .
 
 Regards,
 Shashank Pandey
 91-9873726499

 

From: JParija at veraznet.com
To: Guillermo.Zuniga at cwpanama.com; discussion at sipforum.org
Date: Wed, 12 May 2010 11:05:23 -0700
Subject: Re: [SIPForum-discussion] Call with a Invite after 200OK







The other INVITE is a Re-INVITE sent with different SDP, in this case the Re-INVITE has only CODEC G729 & maxptime value 20 but it was 10 in the initial INVITE. 
 
Hope this will help.
 
Regards,
Jyoti
 




From: discussion-bounces at sipforum.org [mailto:discussion-bounces at sipforum.org] On Behalf Of Zuñiga, Guillermo
Sent: Wednesday, May 12, 2010 7:23 AM
To: discussion at sipforum.org
Subject: [SIPForum-discussion] Call with a Invite after 200OK
 
Hi Fellows.
 
I have a situation with a specific call peer to peer.
I am seeing that after the call is completed with 200Ok I am sending back another Invite with SDP and after that 
The end-peer is sending me a 500 Server Internal Error.
If someone could help me to detect what could be causing that I have to send another Invite if the call is already completed?
 
I am attaching a sniffer call, with the scenarios.
 
Thanks a lot for your help
  		 	   		  
_________________________________________________________________
South Cinema This Decade
http://entertainment.in.msn.com/southcinemathisdecade/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20100513/5a2c3b5d/attachment-0002.html>