< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index Next in Thread >

Re: [reSIProcate] Stack sends a 400 Bad Request()


Title: Message
Byron,
 
No, we aren't currently using this pre-processor. I'm happy to turn it on if you think it will help.
 
Regards,
 
Rob.
-----Original Message-----
From: Byron Campen [mailto:bcampen@xxxxxxxxxxxx]
Sent: 13 March 2007 16:09
To: Robert Mansfield
Cc: resiprocate-devel@xxxxxxxxxxxxxxxxxxxx
Subject: Re: [reSIProcate] Stack sends a 400 Bad Request()

I am having a hard time finding a code-path that could be doing this without writing any logs. Did you enable PEDANTIC_STACK by any chance?

Best regards,
Byron Campen


All,
 
Can anyone spot the problem with the received INVITE in this trace? If we use the older 0.9.0 version of the resip stack the INVITE is not rejected. I've tried with resip 1.1-RC2 and this is the result.
 
I'm unsure about the top most Via header but we have tried by-passing this proxy and the result is the same.
 
Regards,
 
Rob.
 
///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
 
DEBUG | 20070313-130236.515 | RT-SIP-00-20-07-5.bb.cc.dd_v02.exe | RESIP:TRANSPORT | 1396 | Transport.cxx:287 | incoming from: [ V4 172.24.4.222:5060 UDP target domain=unspecified received on: Transport: [ V4 0.0.0.0:5060 UDP target domain=unspecified connectionId=0 ] connectionId=0 ]
STACK | 20070313-130236.515 | RT-SIP-00-20-07-5.bb.cc.dd_v02.exe | RESIP:TRANSPORT | 1396 | Transport.cxx:288 |
 
INVITE sip:00447940582913@xxxxxxxxxxxx:5060 SIP/2.0
Via: SIP/2.0/UDP 172.24.4.222;branch=0
Via: SIP/2.0/UDP 172.24.4.161:5060;branch=z9hG4bK-45f69ff0-f8ed78e3-7754
Max-Forwards: 16
Record-Route: <sip:172.24.4.222;ftag=a10418ac-13c4-45f69ff0-f8ed78e3-56a7;lr=on>
Contact: <sip:3334000@xxxxxxxxxxxx>
From: <sip:3334000@xxxxxxxxxxxx>;tag=a10418ac-13c4-45f69ff0-f8ed78e3-56a7
CSeq: 1 INVITE
Session-Expires: 180;refresher=uas
Min-SE: 90
Content-Type: application/SDP
Supported: timer, timer
Content-Length: 269
 
v=0
o=3334000 189350 189350 IN IP4 10.40.0.10
s=ATA186 Call
c=IN IP4 172.24.4.61
t=0 0
m=audio 30000 RTP/AVP 18 8 0
a=fmtp:18 annexb=yes
a=fmtp:101 0-15
a=rtpmap:18 G729/8000/1
a=rtpmap:8 PCMA/8000/1
a=rtpmap:0 PCMU/8000/1
a=rtpmap:101 telephone-event/8000
 

DEBUG | 20070313-130236.515 | RT-SIP-00-20-07-5.bb.cc.dd_v02.exe | RESIP | 1396 | Helper.cxx:372 | Helper::makeResponse(SipReq:  INVITE 00447940582913@xxxxxxxxxxxx:5060 tid=189e606d40c252a4780a9a7f1a4cee91 cseq=INVITE contact=3334000@xxxxxxxxxxxx / 1 from(wire) code=400 reason=
DEBUG | 20070313-130236.515 | RT-SIP-00-20-07-5.bb.cc.dd_v02.exe | RESIP:TRANSPORT | 1396 | TransportSelector.cxx:521 | Looked up source for destination: [ V4 172.24.4.222:5060 UDP target domain=unspecified received on: Transport: [ V4 0.0.0.0:5060 UDP target domain=unspecified connectionId=0 ] connectionId=0 ] -> [ V4 172.24.4.220:0 UDP target domain=unspecified received on: Transport: [ V4 0.0.0.0:5060 UDP target domain=unspecified connectionId=0 ] connectionId=0 ] sent-by=172.24.4.222 sent-port=0
DEBUG | 20070313-130236.515 | RT-SIP-00-20-07-5.bb.cc.dd_v02.exe | RESIP:TRANSPORT | 1396 | TransportSelector.cxx:879 | Transmitting to [ V4 172.24.4.222:5060 UDP target domain=unspecified received on: Transport: [ V4 0.0.0.0:5060 UDP target domain=unspecified connectionId=0 ] connectionId=0 ] tlsDomain= via [ V4 172.24.4.220:5060 UDP target domain=unspecified received on: Transport: [ V4 0.0.0.0:5060 UDP target domain=unspecified connectionId=0 ] connectionId=0 ]
 
SIP/2.0 400 Bad Request()
Via: SIP/2.0/UDP 172.24.4.222;branch=0
Via: SIP/2.0/UDP 172.24.4.161:5060;branch=z9hG4bK-45f69ff0-f8ed78e3-7754
To: <sip:00447940582913@xxxxxxxxxxxx:5060>;tag=a143a02a
From: <sip:3334000@xxxxxxxxxxxx>;tag=a10418ac-13c4-45f69ff0-f8ed78e3-56a7
CSeq: 1 INVITE
Content-Length: 0
 
 
 

DEBUG | 20070313-130236.515 | RT-SIP-00-20-07-5.bb.cc.dd_v02.exe | RESIP:TRANSPORT | 1396 | Transport.cxx:213 | Adding message to tx buffer to: [ V4 172.24.4.222:5060 UDP target domain=unspecified received on: Transport: [ V4 0.0.0.0:5060 UDP target domain=unspecified connectionId=0 ] connectionId=0 ]
DEBUG | 20070313-130236.531 | RT-SIP-00-20-07-5.bb.cc.dd_v02.exe | RESIP:TRANSPORT | 1396 | Transport.cxx:287 | incoming from: [ V4 172.24.4.222:5060 UDP target domain=unspecified received on: Transport: [ V4 0.0.0.0:5060 UDP target domain=unspecified connectionId=0 ] connectionId=0 ]
STACK | 20070313-130236.531 | RT-SIP-00-20-07-5.bb.cc.dd_v02.exe | RESIP:TRANSPORT | 1396 | Transport.cxx:288 |
 
ACK sip:00447940582913@xxxxxxxxxxxx:5060 SIP/2.0
Via: SIP/2.0/UDP 172.24.4.222;branch=0
Via: SIP/2.0/UDP 172.24.4.161:5060;branch=z9hG4bK-45f69ff0-f8ed78e3-7754
Max-Forwards: 16
Record-Route: <sip:172.24.4.222;ftag=a10418ac-13c4-45f69ff0-f8ed78e3-56a7;lr=on>
Contact: <sip:3334000@xxxxxxxxxxxx>
To: <sip:00447940582913@xxxxxxxxxxxx:5060>;tag=a143a02a
From: <sip:3334000@xxxxxxxxxxxx>;tag=a10418ac-13c4-45f69ff0-f8ed78e3-56a7
CSeq: 1 ACK
Content-Length: 0
 
 
 
 
 

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

Robert Mansfield

Senior Software Engineer

Redwood Technologies Limited

The Redwood Building, Broad Lane, Bracknell, Berkshire, RG12 9GU, U.K.

Registered in England No. 2817863

T +[44] (0)1344 304 344

F +[44] (0)1344 304 345

E rjm@xxxxxxxxxxxxxxx  

W www.redwoodtech.com

=====

Email Disclaimer

The information in this email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this email by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. When addressed to our clients any opinions or advice contained in this email are subject to the limitations of Redwood Technologies Limited's standard terms and conditions of contract.

 
_______________________________________________
resiprocate-devel mailing list