<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Ok, <br>
I have found it in the sources of mod_sofia.<br>
<br>
In function sofia_update_callee_id the function parses the call ID
only from the P-asserted-identity, so RPID is ignored.<br>
Can be this posted to Jira as feature request?<br>
<br>
Thank you,<br>
Thomas<br>
<br>
<div class="moz-cite-prefix">On 22.05.2015 11:17, Tomáš Boros wrote:<br>
</div>
<blockquote cite="mid:555EF439.4070501@vmtele.com" type="cite">
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
Hello,<br>
<br>
we have the following problem.<br>
<br>
On profile, which connects to the provider we use
P-Asserted-Identity for identification. <br>
In the internal line, we use Remote-Party-ID for identification.<br>
<br>
The following problem occurs:<br>
When doing calls, Invites are correctly translated from PAI to
RPID, but when a 200 OK arrives from our Internal network, it has
a Remote-Party-ID and is translated to a P-Asserted-Identity, but
the number is changed.<br>
<br>
I am attaching SIP messages:<br>
<br>
recv 1167 bytes from udp/[192.168.5.17]:5060 at 10:26:06.319229:<br>
------------------------------------------------------------------------<br>
SIP/2.0 200 OK<br>
Via: SIP/2.0/UDP
192.168.5.97;rport=5060;branch=z9hG4bK5mNSKt220vF5K<br>
Record-Route:
<sip:192.168.5.66;lr=on;ftag=m29tUHH087vFr;did=01a.d76><br>
Record-Route: <sip:192.168.5.18;lr=on;did=01a.bf7><br>
From: "00421800123993" <a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:sip:00421800123993@192.168.5.97"><sip:00421800123993@192.168.5.97></a>;tag=m29tUHH087vFr<br>
To: <a moz-do-not-send="true" class="moz-txt-link-rfc2396E"
href="mailto:sip:307000421221028600@192.168.5.17"><sip:307000421221028600@192.168.5.17></a>;tag=p9D7Npj3amv3j<br>
Call-ID: 953485a8-d9b6-4c36-a54d-01fab395ad48<br>
CSeq: 75805518 INVITE<br>
Contact: <a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:sip:307000421221028600@192.168.5.94:5060;transport=udp"><sip:307000421221028600@192.168.5.94:5060;transport=udp></a><br>
User-Agent: VMTele-SBC<br>
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO,
UPDATE, REGISTER, REFER, NOTIFY<br>
Supported: timer, path, replaces<br>
Allow-Events: talk, hold, conference, refer<br>
Content-Type: application/sdp<br>
Content-Disposition: session<br>
Content-Length: 278<br>
X-FS-Support: update_display,send_info<br>
<b>Remote-Party-ID:
<a moz-do-not-send="true" class="moz-txt-link-rfc2396E"
href="mailto:sip:+421221028600@212.232.17.77"><sip:+421221028600@212.232.17.77></a>;party=calling;screen=yes;privacy=off</b><br>
<br>
v=0<br>
o=VMTele-SBC 1432264463 1432264464 IN IP4 192.168.5.94<br>
s=VMTele-SBC<br>
c=IN IP4 192.168.5.94<br>
t=0 0<br>
m=audio 18702 RTP/AVP 8 101 13<br>
a=rtpmap:8 PCMA/8000<br>
a=rtpmap:101 telephone-event/8000<br>
a=fmtp:101 0-16<br>
a=rtpmap:13 CN/8000<br>
a=ptime:20<br>
a=rtcp:18703 IN IP4 192.168.5.94<br>
<br>
In debug logs I can see:<br>
2015-05-22 10:26:06.328812 [ALERT] sofia.c:1198
sofia/core-profile/307000421221028600 Same Callee ID "Outbound
Call" <307000421221028600><br>
<br>
send 1030 bytes to udp/[212.232.17.60]:5060 at 10:26:06.340758:<br>
------------------------------------------------------------------------<br>
SIP/2.0 200 OK<br>
Via: SIP/2.0/UDP
212.232.17.60:5060;branch=z9hG4bK4365798a;rport=5060<br>
From: <a moz-do-not-send="true" class="moz-txt-link-rfc2396E"
href="mailto:sip:+421800123993@212.232.17.60"><sip:+421800123993@212.232.17.60></a>;tag=as703def00<br>
To: <a moz-do-not-send="true" class="moz-txt-link-rfc2396E"
href="mailto:sip:+421221028600@212.232.17.77"><sip:+421221028600@212.232.17.77></a>;tag=XB02p6tZSjvFN<br>
Call-ID: <a moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:2598c37260ec91283d70ac220f32c5cf@212.232.17.60:5060">2598c37260ec91283d70ac220f32c5cf@212.232.17.60:5060</a><br>
CSeq: 102 INVITE<br>
Contact: <a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:sip:+421221028600@212.232.17.77:5060;transport=udp"><sip:+421221028600@212.232.17.77:5060;transport=udp></a><br>
User-Agent: VMTelecomSBC<br>
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO,
UPDATE, REGISTER, REFER, PRACK, NOTIFY<br>
Require: timer<br>
Supported: precondition, 100rel, timer, path, replaces<br>
Allow-Events: talk, hold, conference, refer<br>
Session-Expires: 800;refresher=uac<br>
Content-Type: application/sdp<br>
Content-Disposition: session<br>
Content-Length: 257<br>
<b>P-Asserted-Identity: "VIPTel" <a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:sip:307000421221028600@212.232.17.77"><sip:307000421221028600@212.232.17.77></a></b><br>
<br>
v=0<br>
o=VMTele-SBC 1432250761 1432250762 IN IP4 212.232.17.77<br>
s=VMTele-SBC<br>
c=IN IP4 212.232.17.77<br>
t=0 0<br>
m=audio 32404 RTP/AVP 0 101<br>
a=rtpmap:0 PCMU/8000<br>
a=rtpmap:101 telephone-event/8000<br>
a=fmtp:101 0-16<br>
a=ptime:20<br>
a=rtcp:32405 IN IP4 212.232.17.77<br>
<br>
<br>
I have made tests with PAI<-> PAI too, I mean I have used
P-Asserted-Identity instead of Remote-Party-ID in 200 OK, and in
such a case it worked correctly. Received number and name was
forwarded to the other leg.<br>
<br>
The problem only occurs, when the RPID is in the incoming 200 OK.<br>
<br>
Do you think its a bug? I have pass-callee-id set to true on both
profiles and I use pai and rpid as in sip_cid_type accordingly.<br>
<br>
<div class="moz-signature">-- <br>
<font style="font-family:'Tahoma', sans-serif; font-size: 9pt;
color:#333;"> <font style="font-weight:bolder; color:#333333;
font-size:11pt;">Tomáš Boros</font><br>
</font> </div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_________________________________________________________________________
Professional FreeSWITCH Consulting Services:
<a class="moz-txt-link-abbreviated" href="mailto:consulting@freeswitch.org">consulting@freeswitch.org</a>
<a class="moz-txt-link-freetext" href="http://www.freeswitchsolutions.com">http://www.freeswitchsolutions.com</a>
Official FreeSWITCH Sites
<a class="moz-txt-link-freetext" href="http://www.freeswitch.org">http://www.freeswitch.org</a>
<a class="moz-txt-link-freetext" href="http://confluence.freeswitch.org">http://confluence.freeswitch.org</a>
<a class="moz-txt-link-freetext" href="http://www.cluecon.com">http://www.cluecon.com</a>
FreeSWITCH-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a>
<a class="moz-txt-link-freetext" href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a>
UNSUBSCRIBE:<a class="moz-txt-link-freetext" href="http://lists.freeswitch.org/mailman/options/freeswitch-users">http://lists.freeswitch.org/mailman/options/freeswitch-users</a>
<a class="moz-txt-link-freetext" href="http://www.freeswitch.org">http://www.freeswitch.org</a></pre>
</blockquote>
<br>
<div class="moz-signature"><br>
</div>
</body>
</html>