[reSIProcate] Request Line construction problems during shuffle re-invite in Dialog::makerequest()
Robert Sparks
rjsparks at nostrum.com
Fri Nov 17 22:56:16 CST 2006
Bill - it will help if you actually give us the flow messages.
A Contact that looks like
Contact: <sip:10.0.0.1> is quite legal in a 200 to an INVITE.
Are you seeing something that looks like
Contact: <sip:@10.0.0.1>? That one isn't legal.
There are no differences in the requirements for what goes into the
Contact for an initial INVITE
or any subsequent reINVITE in that dialog.
On Nov 17, 2006, at 6:31 PM, Kovar, William ((Bill)) wrote:
> Scott,
>
> In trying to identify who is violating the SIP spec....
> I send an Invite which gets answered with a 200 that has a
> malformed Contact header, i.e. no userinfo part.
> DUM sends the ACK to the malformed URI successfully.
> I Send an re-Invite using provideOffer() and Req-URI for the Invite
> is bad. The Invite times-out.
>
> This is really baffling me as to who is breaking the spec because
> some have told me that the Contact header in this form is OK except
> for the initial invite.
>
> Anybody have an opinion??
>
> Bill Kovar
> bkovar at avaya.com
> Avaya, Inc.
> (732) 852-2609
>
>
> From: Scott Godin [mailto:slgodin at icescape.com]
> Sent: Tuesday, November 07, 2006 8:02 PM
> To: Kovar, William (Bill); resiprocate-devel at list.sipfoundry.org
> Subject: RE: [reSIProcate] Request Line construction problems
> during shuffle re-invite in Dialog::makerequest()
>
> What you are doing sounds fine.
>
>
>
> The request line on your the outbound re-invite is likely from the
> contact header of the 200 from the initial invite – I’m assuming it
> is a server invite session.
>
>
>
> Scott
>
>
>
> From: resiprocate-devel-bounces at list.sipfoundry.org
> [mailto:resiprocate-devel-bounces at list.sipfoundry.org] On Behalf Of
> Kovar, William (Bill)
> Sent: Tuesday, November 07, 2006 6:55 PM
> To: resiprocate-devel at list.sipfoundry.org
> Subject: [reSIProcate] Request Line construction problems during
> shuffle re-invite in Dialog::makerequest()
>
>
>
> All,
>
>
>
> I'm seeing a problem with Dialog::makerequest() when receiving a
> ReInvite. The provideOffer() method attempts to build the INVITE
> message and does so with an invalid Request Line, i.e. INVITE
> sip:domain.com where the user part is missing. Below are snips from
> the log showing the incoming INVITE, the provideOffer(), and the
> subsequent prints in makerequest().
>
>
>
> The complete sequence is shown in the attached trace, but a pair of
> connected sessions, that are being managed by a B2B, is being sent
> a re-invite, which I have to provideOffer() to the other side of
> the B2B. The provideOffer() is being done from within onAnswer()
> within the same DUM and thread instance (but using DumThread and
> StackThread). I put some prints into Dialog::makerequest() and
> found that it was accessing a member variable, mRemoteTarget.Uri,
> within the Dialog. The Re-invite comes in on 1 session, and I'm
> sending the offer on a different session, the call ids are
> different and hence the dialogs should be different.
>
>
>
> I'm on a older version of resip from SVN (circa mar 06) but just
> pulled down the 1.0.1 tarball and didn't see any change to
> Dialog.cxx that would address this.
>
>
>
> Is what I am trying to do legal and if so, any ideas why the
> request line is being built incorrectly?
>
>
>
> Bill Kovar
>
>
>
>
> INVITE sip:55123 at 135.8.116.33:5060 SIP/2.0Via: SIP/2.0/UDP
> 135.8.52.181:5060;branch=z9hG4bKD256464603538333231180b.0Via: SIP/
> 2.0/UDP
> 135.8.52.54:36092;psrrposn=1;received=135.8.52.54;branch=z9hG4bK-
> d87543-7e2466749713bd4c-1--d87543-;rport=36092Max-Forwards:
> 69Record-Route: <sip:135.8.52.181:5060;lr>Contact: <sip:
> 55501 at 135.8.52.54:36092;rinstance=47c2eadfce5cb0e5>To: "IC 7.1
> B2B"<sip:55123 at avaya.com>;tag=87167f3fFrom: <sip:
> 55501 at avaya.com>;tag=d52d576bCall-ID:
> e03e8a100527ad51ZTU2NTMzOTg2ZDMyYzc4MWNiYjc4MzMzMGUwNGJkYWM.CSeq: 3
> INVITEAllow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY,
> MESSAGE, SUBSCRIBE, INFOContent-Type: application/sdpUser-Agent: X-
> Lite release 1003l stamp 30942P-Asserted-Identity: sip:
> 55501 at avaya.comContent-Length: 231 v=0o=- 9 4 IN IP4
> 135.8.52.54s=CounterPath eyeBeam 1.5c=IN IP4 0.0.0.0t=0 0m=audio
> 17010 RTP/AVP 0 127a=fmtp:127 0-15a=rtpmap:127 telephone-event/
> 8000a=sendonlya=x-rtp-session-id:663EBBA451B741909024C82821116262
>
> Fixed SDP (Eyebeam sends an old style Hold with Connection =
> 0.0.0.0 which is problematic for me...)o=- 9 4 IN IP4
> 135.8.52.54s=CounterPath eyeBeam 1.5c=IN IP4 135.8.52.54t=0
> 0m=audio 17010 RTP/AVP 0 127a=fmtp:127 0-15a=rtpmap:127 telephone-
> event/8000a=sendonlya=x-rtp-session-id:
> 663EBBA451B741909024C82821116262 Problematic DUM code:INFO |
> 20061107-180909.164 | SipSwitch | RESIP:DUM | 5064 |
> ServerInviteSession.cxx:154 | InviteSession::Connected: provideOffer
> INFO | 20061107-180909.164 | SipSwitch | RESIP:DUM | 5064 |
> InviteSession.cxx:2032 | Transition InviteSession::Connected ->
> InviteSession::SentReinvite
> DEBUG | 20061107-180909.164 | SipSwitch | RESIP:DUM | 5064 |
> Dialog.cxx:834 | +++++++ mRemoteTarget.Uri = sip:
> 135.8.135.123;transport=tcp
> DEBUG | 20061107-180909.164 | SipSwitch | RESIP:DUM | 5064 |
> Dialog.cxx:836 | +++++++ Rline = INVITE sip:
> 135.8.135.123;transport=tcp SIP/2.0
> DEBUG | 20061107-180909.164 | SipSwitch | RESIP:DUM | 5064 |
> Dialog.cxx:901 | Dialog::makeRequest: INVITE sip:
> 135.8.135.123;transport=tcp SIP/2.0Via: SIP/2.0/ ;branch=z9hG4bK-
> d87543-2a190f6cd355ba15-1--d87543-;rportMax-Forwards: 70Route: <sip:
> 135.8.52.181:5060;lr>Route: <sip:
> 135.8.135.123;lr;transport=tcp>Contact: <sip:
> 55123 at 135.8.116.33:5060;rinstance=013fc72a18699110>To: "Kowen's IPA
> 321"<sip:32100 at avaya.com>;tag=092b1eb9f80db1ee1345461dba00From:
> "55123"<sip:55123 at avaya.com>;tag=fc7a402dCall-ID:
> 092b1eb9f80db1ef1345461dba00CSeq: 2 INVITEAllow: INVITE, ACK,
> CANCEL, OPTIONS, BYE, NOTIFYContent-Length: 0
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel at list.resiprocate.org
> https://list.resiprocate.org/mailman/listinfo/resiprocate-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20061117/55d7347e/attachment.htm>
More information about the resiprocate-devel
mailing list