Hello Nick,
As the P-Asserted-Id hdr is an name-addr like header (like FROM, TO,
Contact), you should do:
append_hf("P-Asserted-Identity: \"Test User\"
<sip:[email protected]
<mailto:sip%[email protected]>>;user=phone\r\n", "Call-ID");
where "Test User" is the display name - but depends on the end devices
if they do display it or not.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 04/29/2013 02:19 AM, Nick Khamis wrote:
Hello Everyone,
Is it possible to pass a meaningful caller name along with the caller
id given the carrier supports CLI?
Before asking the carrier, I was doing some tests.
I know that append_hf("P-Asserted-Identity:
<sip:[email protected]
<mailto:sip%[email protected]>>; user=phone\r\n",
"Call-ID") works
fine for the phone number alone (i.e., 15453387463) however,
append_hf("P-Asserted-Identity: From: \" Test User \"
<sip:[email protected]
<mailto:sip%[email protected]>>; user=phone\r\n",
"Call-ID") generates a meaningless CID.
The SIP Trace: P-Asserted-Identity: From: "Mike Peer"
<sip:[email protected]
<mailto:sip%[email protected]>>; user=phone.
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,
I have added the following code:
modparam("auth_db", "load_credentials", "rpid")
modparam("auth", "rpid_avp", "$avp(rpid)")
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?
Thanks in Advance,
Nick
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
