Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 2346 by alexander.kozlov.IV: Container adds Route
with "transport" parameter
http://code.google.com/p/mobicents/issues/detail?id=2346
What steps will reproduce the problem?
1. Create INVITE request
2. Add route using req.pushRoute()
3. Send request
What is the expected output?
Message should contains only one Route header that was added by me.
What do you see instead?
I see two Route headers. One added by me, and one added by container
with "transport" parameter.
I'm not sure whether it's good idea to add "transport" at all, but any way
you should add it to existent Route instead of new one.
What version of the product are you using? On what operating system?
Mobicents Sip Servlets #1078 r16815.
Please provide any additional information below.
feb 10 12:22:39,727 [SIP-TCP-Core-PipelineThreadpool-2]
com.avistar.callcontrol.sip.router.AbstractB2BStrategy DEBUG: B2B request
to command: INVITE sip:[email protected]:5066 SIP/2.0
To: <sip:[email protected]>
From:
<sip:[email protected]>;tag=36167004_c71fdaf2_53d4bcb1-6836-41dd-a6ea-122e6b879dd9
CSeq: 1 INVITE
Accept: application/sdp,application/media_control+xml,application/csta+xml
User-Agent: AVSR-C3-ME/2.5.0.44-DEBUG
Max-Forwards: 69
Allow: INVITE,CANCEL,BYE,ACK,INFO,MESSAGE,PUBLISH,SUBSCRIBE,NOTIFY,REFER
Content-Type: application/sdp
Call-ID: [email protected]
Contact:
<sip:[email protected]:5060>;+sip.instance="<urn:uuid:8C830D7D-59CD-11DF-BE5C-5BBF58C16A7E>"
Supported: timer
Require: timer
Session-Expires: 3600;refresher=uac
Avistar-From-Address: 109.254.75.93
Avistar-Call-Control-Originator-URI: sip:[email protected]:5064
Avistar-To-Address: 109.254.75.93
Route: <sip:109.254.75.93:5062;lr>
Route: <sip:109.254.75.93;lr>
Avistar-Call-Control-Linked-Session-Id:
(36167004_c71fdaf2_53d4bcb1-6836-41dd-a6ea-122e6b879dd9:[email protected]:53d4bcb1-6836-41dd-a6ea-122e6b879dd9:Call
Control)
Content-Length: 631
..............
feb 10 12:22:39,761 [SIP-TCP-Core-PipelineThreadpool-2]
org.mobicents.ext.javax.sip.dns.DefaultDNSServerLocator DEBUG: Resolving
109.254.75.93 transport null
feb 10 12:22:39,762 [SIP-TCP-Core-PipelineThreadpool-2]
org.mobicents.ext.javax.sip.dns.DefaultDNSServerLocator DEBUG: host
109.254.75.93 is a numeric IP address, no DNS SRV lookup to be done, using
the hop given in param
feb 10 12:22:39,763 [SIP-TCP-Core-PipelineThreadpool-2]
org.mobicents.servlet.sip.message.SipServletRequestImpl DEBUG: session
transport is null
feb 10 12:22:39,771 [SIP-TCP-Core-PipelineThreadpool-2]
org.mobicents.servlet.sip.core.SipApplicationDispatcherImpl DEBUG: the
triplet host/port/transport : 109.254.75.93/5062/UDP is external : true
feb 10 12:22:39,772 [SIP-TCP-Core-PipelineThreadpool-2]
org.mobicents.servlet.sip.message.SipServletRequestImpl DEBUG: Adding next
hop found by RFC 3263 lookups as route headerRoute:
<sip:109.254.75.93:5062;lr;transport=udp>
feb 10 12:22:39,772 [SIP-TCP-Core-PipelineThreadpool-2]
org.mobicents.servlet.sip.message.SipServletRequestImpl DEBUG: Added via
HeaderVia: SIP/2.0/UDP 109.254.75.93:5060
feb 10 12:22:39,773 [SIP-TCP-Core-PipelineThreadpool-2]
org.mobicents.servlet.sip.message.SipServletRequestImpl DEBUG: The found
transport for sending request is 'UDP'
feb 10 12:22:39,773 [SIP-TCP-Core-PipelineThreadpool-2]
org.mobicents.servlet.sip.router.DefaultApplicationRouter DEBUG:
org.mobicents.servlet.sip.router.DefaultApplicationRouter@178dc08 checking
for next application for request INVITE sip:[email protected]:5066 SIP/2.0
To: <sip:[email protected]>
From:
<sip:[email protected]>;tag=36167004_c71fdaf2_53d4bcb1-6836-41dd-a6ea-122e6b879dd9
CSeq: 1 INVITE
Accept: application/sdp,application/media_control+xml,application/csta+xml
User-Agent: AVSR-C3-ME/2.5.0.44-DEBUG
Max-Forwards: 69
Allow: INVITE,CANCEL,BYE,ACK,INFO,MESSAGE,PUBLISH,SUBSCRIBE,NOTIFY,REFER
Content-Type: application/sdp
Call-ID: [email protected]
Contact:
<sip:[email protected]:5060>;+sip.instance="<urn:uuid:8C830D7D-59CD-11DF-BE5C-5BBF58C16A7E>"
Supported: timer
Require: timer
Session-Expires: 3600;refresher=uac
Avistar-From-Address: 109.254.75.93
Avistar-Call-Control-Originator-URI: sip:[email protected]:5064
Avistar-To-Address: 109.254.75.93
Route: <sip:109.254.75.93:5062;lr;transport=udp>
Route: <sip:109.254.75.93:5062;lr>
Route: <sip:109.254.75.93;lr>
Avistar-Call-Control-Linked-Session-Id:
(36167004_c71fdaf2_53d4bcb1-6836-41dd-a6ea-122e6b879dd9:[email protected]:53d4bcb1-6836-41dd-a6ea-122e6b879dd9:Call
Control)
Via: SIP/2.0/UDP
109.254.75.93:5060;branch=z9hG4bK53d4bcb1-6836-41dd-a6ea-122e6b879dd9_c71fdaf2_24051653
Content-Length: 631
.................
