[reSIProcate] How to handle Re-Invite after Connected

[Scott Godin]

This is likely happening due to Session Timers.  All you need to do is call provideAnswer and give it the same SDP answer you gave it the first time (the local sdp can also be retrieved from the invite session - getLocalSdp()).
 
Scott

________________________________

From: resiprocate-devel-bounces at list.sipfoundry.org on behalf of Kovar, William (Bill)
Sent: Wed 8/16/2006 2:05 PM
To: resiprocate-devel at list.sipfoundry.org
Subject: [reSIProcate] How to handle Re-Invite after Connected


All,
 
I'm trying to understand what I can do in DUM when a RE-INVITE is sent after InviteSession::Connected.
 
I see a transition from InviteSession::Connected to InviteSession::ReceivedReinvite and the OnOffer(...) callback is called. However, I'm not sure what I can/should do in response to that Re-Invite. Additionally, the SDP is not different. Attached are the 2 INVITE msgs:
 
INVITE
 
INVITE sip:55123 at 135.8.116.33:5060;rinstance=eb0e202c08725b7f SIP/2.0
Via: SIP/2.0/UDP 135.8.52.133:5060;branch=z9hG4bK8383830303035656564f53.0
Via: SIP/2.0/TCP 135.8.135.123;psrrposn=2;branch=z9hG4bK80ecc1811538db1ff4a43dca41500
Max-Forwards: 69
Record-Route: <sip:135.8.52.133:5060;transport=udp;lr>
Record-Route: <sip:135.8.135.123;lr;transport=tcp>
Contact: "55001"<sip:55001 at 135.8.135.123;transport=tcp>
To: sip:55123 at 135.8.52.133
From: "Kowen's IPA 321" <sip:anonymous.invalid>;tag=80ecc1811538db1fd4a43dca41500
Call-ID: 80ecc1811538db1fe4a43dca41500
CSeq: 1 INVITE
Session-Expires: 240;refresher=uac
Min-SE: 240
Allow: INVITE, CANCEL, BYE, ACK, PRACK, SUBSCRIBE, NOTIFY, REFER, OPTIONS
Content-Type: application/sdp
Supported: 100rel, timer, replaces, join, histinfo
User-Agent: Avaya CM/R013x.01.0.628.2
Referred-By: <sip:55001 at 135.8.116.33:5060;rinstance=f82579222b76062c>
Content-Length: 158
UUI: 44e32dcb0000000087083436233e0002-55002 at 135.8.52.133
History-Info: <sip:avaya.com>;index=1, <sip:avaya.com>;index=1.1
 
v=0
o=- 1 1 IN IP4 135.8.135.123
s=-
c=IN IP4 135.8.135.124
t=0 0
m=audio 2220 RTP/AVP 0 127
a=rtpmap:0 PCMU/8000
a=rtpmap:127 telephone-event/8000
 
 
Re-INVITE
 
INVITE sip:55123 at 135.8.116.33:5060;rinstance=eb0e202c08725b7f SIP/2.0
Via: SIP/2.0/UDP 135.8.52.133:5060;branch=z9hG4bK838383030303565656775a.0
Via: SIP/2.0/TCP 135.8.135.123;psrrposn=1;branch=z9hG4bK80ecc1811538db144b43dca41500
Max-Forwards: 69
Record-Route: <sip:135.8.52.133:5060;transport=udp;lr>
Contact: "Kowen's IPA 32100"<sip:32100 at 135.8.135.123;transport=tcp>
To: <sip:55123 at 135.8.52.133>;tag=950fd07f
From: "Kowen's IPA 321"<sip:anonymous.invalid>;tag=80ecc1811538db1fd4a43dca41500
Call-ID: 80ecc1811538db1fe4a43dca41500
CSeq: 2 INVITE
Session-Expires: 240;refresher=uac
Min-SE: 240
Allow: INVITE, CANCEL, BYE, ACK, PRACK, SUBSCRIBE, NOTIFY, REFER, OPTIONS
Content-Type: application/sdp
Supported: 100rel, timer, replaces, join, histinfo
User-Agent: Avaya CM/R013x.01.0.628.2
P-Asserted-Identity: "Kowen's IPA 32100"<sip:32100 at avaya.com>
Content-Length: 158
 
v=0
o=- 1 1 IN IP4 135.8.135.123
s=-
c=IN IP4 135.8.135.124
t=0 0
m=audio 2220 RTP/AVP 0 127
a=rtpmap:0 PCMU/8000
a=rtpmap:127 telephone-event/8000
 
Any suggestions??
 
Bill Kovar
Avaya Inc.
(732) 852-2609
bkovar at avaya.com
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20060816/7a32f30c/attachment.htm>