Bad Address Resolution When Route With ';lr' Parameter Is Set (Doc ID 837753.1)

Last updated on SEPTEMBER 23, 2016

Applies to:

Oracle Communications Converged Application Server - Version 4.0.0 and later
Information in this document applies to any platform.
Checked for relevance on 09-May-2011

Symptoms

When setting the 'Route' destination as below, the message is correctly sent to 127.0.0.1:5060.

SUBSCRIBE sip:io@example.com SIP/2.0
To: sip:io@example.com
CSeq: 1 SUBSCRIBE
Content-Length: 0
Route: <sip:127.0.0.1:5060;lr>
Call-ID: wlss-31b284af-1c11e29e603f031f49300510132a20e5@example1.com
P-Asserted-Identity: sip:me@example.com
Max-Forwards: 70
From: <sip:pippo@example.com>;tag=9f52c31a
Contact:
<sip:example1.com:5060;transport=udp;wlsscid=1ae4479ac6ff71;sipappsessionid=app-1pog8mpwp9saf>
;


But the following error will appear in the log:

<6-mag-2009 9.33.47 CEST> <Warning> <WLSS.Transport> <BEA-330638>
<Unable to resolve route to destination : example.com due to java.net.SocketException:
Unresolved address>

Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms