search

JohnFord / sipservlets

Automatically exported from code.google.com/p/sipservlets
0 stars 0 forks source link

Extra Route header added on INVITE #251

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Send SIP INVITE with three route headers
2. Add three Route headers using req.pushRoute(..)
3. Container adds and extra Route header

What is the expected output? What do you see instead?
I expect a 200 OK from SIP INVITE instead I see a 'SIP/2.0 404 Not found'

What version of the product are you using? On what operating system?
mss-3.0.0-SNAPSHOT-jboss-as-7.1.3.Final

Please provide any additional information below.

Hi,

My issue is similar to this one from 2011.

https://code.google.com/p/mobicents/issues/detail?id=2346

My code adds three Route headers using req.pushRoute(..)

But mobicents is adding a fourth one that contains the loopback address.

INVITE sip:90878544417@ccmm-tg-021.bingo.com:5060;transport=tcp SIP/2.0
Call-ID: a4d8a2c3cd9b17671ebd78a307d573f6@127.0.0.1
CSeq: 1 INVITE
From: 
<sip:81384718@ccmm-tg-021.bingo.com:5060>;tag=36575269_3f394085_5411fa07-9251-40
c6-81a4-47abedc9f64a
To: <sip:90878544417@ccmm-tg-021.bingo.com:5060>
Max-Forwards: 70
Contact: <sip:81384718@127.0.0.1:5081;transport=tls>
Via: SIP/2.0/TLS 
localhost:5081;branch=z9hG4bK5411fa07-9251-40c6-81a4-47abedc9f64a_3f394085_13898
22401936213000;received=127.0.0.1;rport=5081
Content-Type: application/sdp
Expires: 180
Route: 
<sip:127.0.0.1:5081;transport=tls;lr;directive=NEW;previousappname=com.bingo.ser
ver.bla.poc.Papp;previousappid=5411fa07-9251-40c6-81a4-47abedc9f64a>
Route: <sip:lal-bingo-vcse2.bingo.com;transport=tls;lr>
Route: <sip:10.50.179.6:5061;transport=tls;zone-id=9;directed;lr>
Route: <sip:ccmm-tg-021.bingo.com;transport=tcp;lr>
Content-Length: 1694

This etra Route header gets added outside my control, but only on one of my 
machines and causes INVITE to fail with a SIP/2.0 404 Not found

Route: 
<sip:127.0.0.1:5081;transport=tls;lr;directive=NEW;previousappname=com.cisco.wx2
.server.sla.poc.SlaPocApplication;previousappid=5411fa07-9251-40c6-81a4-47abedc9
f64a>

Original issue reported on code.google.com by emann...@gmail.com on 15 Jan 2014 at 9:59

GoogleCodeExporter commented 8 years ago 
This is happening on my MacBook Pro 10.8.5.

Original comment by emann...@gmail.com on 15 Jan 2014 at 10:05

GoogleCodeExporter commented 8 years ago 
Please provide full server log at DEBUG level so we can investigate

Original comment by jean.deruelle on 16 Jan 2014 at 8:42

GoogleCodeExporter commented 8 years ago 
I attached server.log    There are only three Routes added for REGISTER which 
is correct, but then there are four added for INVITE.

Thanks you.

Original comment by emann...@gmail.com on 16 Jan 2014 at 2:34

Attachments:

GoogleCodeExporter commented 8 years ago 
Just some more background.  Here we are developing a proof of concept using MSS 
as a server side UAC to an existing very widely deployed UAS.  So far the POC 
is looking good but an issue like this is a potential blocker.  If this POC is 
a success then this could lead to a large deployment of MSS.

Original comment by emann...@gmail.com on 17 Jan 2014 at 1:29

GoogleCodeExporter commented 8 years ago 
To resolve I needed to set up my Application Routing in my management console 
which I failed to do when I set up my new machine.  Must study docs better.

This can be closed, I think.

Original comment by emann...@gmail.com on 20 Jan 2014 at 11:12

GoogleCodeExporter commented 8 years ago 
OK :)

Original comment by jean.deruelle on 21 Jan 2014 at 8:40

GoogleCodeExporter commented 8 years ago

Original comment by jean.der...@telestax.com on 25 Aug 2014 at 10:53