<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>Hello Nick,<br>
<br>
As the P-Asserted-Id hdr is an name-addr like header (like FROM,
TO, Contact), you should do:<br>
<br>
append_hf("P-Asserted-Identity: \"Test User\" <<a
moz-do-not-send="true"
href="mailto:sip%3A15453387463@test.server.com">sip:15453387463@test.server.com</a>>;user=phone\r\n",
"Call-ID");<br>
<br>
where "Test User" is the display name - but depends on the end
devices if they do display it or not.<br>
</tt><tt><br>
Regards,<br>
</tt>
<pre class="moz-signature" cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a class="moz-txt-link-freetext" href="http://www.opensips-solutions.com">http://www.opensips-solutions.com</a></pre>
<br>
On 04/29/2013 02:19 AM, Nick Khamis wrote:
<blockquote
cite="mid:CAGWRaZbn=uvV2809geSffZ5J3-XZoOa4zLB1RGkM-nQi5ZHqUQ@mail.gmail.com"
type="cite">
<div dir="ltr">Hello Everyone,
<div><br>
</div>
<div style="">Is it possible to pass a meaningful caller name
along with the caller id given the carrier supports CLI?</div>
<div style="">Before asking the carrier, I was doing some tests.</div>
<div style=""><br>
</div>
<div style="">I know that append_hf("P-Asserted-Identity: <<a
moz-do-not-send="true"
href="mailto:sip%3A15453387463@test.server.com">sip:15453387463@test.server.com</a>>;
user=phone\r\n", "Call-ID") works</div>
<div style="">fine for the phone number alone (i.e.,
15453387463) however, append_hf("P-Asserted-Identity: From: \"
Test User \" <<a moz-do-not-send="true"
href="mailto:sip%3A15453387463@test.server.com">sip:15453387463@test.server.com</a>>;
user=phone\r\n", "Call-ID") generates a meaningless CID.</div>
<div style=""><br>
</div>
<div style="">The SIP Trace: P-Asserted-Identity: From: "Mike
Peer" <<a moz-do-not-send="true"
href="mailto:sip%3A15453387463@test.server.com">sip:15453387463@test.server.com</a>>;
user=phone.</div>
<div style=""><br>
</div>
<div style="">Once I know what is accepted for PAI, I plan on
assigning subscriber.rpid that value. To load rpid for a
specific caller and INVITE,<br>
</div>
<div style="">I have added the following code:</div>
<div style=""><br>
</div>
<div style="">
<div>modparam("auth_db", "load_credentials", "rpid")</div>
<div>modparam("auth", "rpid_avp", "$avp(rpid)")</div>
<div><br>
</div>
<div style="">Testing from branch route, $avp(rpid) is NULL.
We do not allow users to REGISTER. Any way we can get
subscriber.rpid for INVITES? Finally, is branch_route and
failure_routes, the safest place to append the PAI?</div>
<div><br>
</div>
</div>
<div style="">Thanks in Advance,</div>
<div style=""><br>
</div>
<div style="">Nick</div>
</div>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a>
<a class="moz-txt-link-freetext" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
</body>
</html>