I think ...
From a standards point of view there is no such header as P-Asserted-ID so you've effectively made that one up by setting the sip_h_P-Asserted-ID variable.
The P-Asserted-*Identity* header is the standards based one which is inserted by FS if you set something like: {sip_cid_type=pid,effective_caller_id_name=George,effective_caller_id_number=1234} I don't think it supports multiple comma delimited values but you could try suppress it and craft the header yourself: {sip_cid_type=none,sip_h_P-Asserted-Identity='<sip:1234@1.1.1.1>, tel:+1234'} You will need to work our the quotation system and escaping if you want to add a name and you might need to use \, instead of , too. No idea if that would work. Good luck! On 6 January 2015 at 13:57, George F. Phelps <GeorgePhelps@gfphelps.com> wrote:
Michael Jerris,
Thanks for pointing out the comma delimited syntax. However…
I am still trying to get setting my outbound caller ID to work. I noticed, in this Freeswitch SIP trace…
send 1202 bytes to udp/[66.33.147.150]:5060 at 07:12:09.474756:
------------------------------------------------------------------------
INVITE sip:1770XXXXXXX@66.33.147.150 SIP/2.0
Via: SIP/2.0/UDP 54.174.255.168:5080;rport;branch=z9hG4bKKDN5acD6Zcp2g
Max-Forwards: 69
From: "George F Phelps" <sip:1404XXXXXXX@54.174.255.168
;tag=gpmpmpp142SFH
To: <sip:1770XXXXXXX@66.33.147.150>
Call-ID: 146d208a-1040-1233-1bbe-0a1aa9c1784d
CSeq: 69937100 INVITE
Contact: <sip:gw+switch2voip.us@54.174.255.168:5080;transport=udp;gw= switch2voip.us>
User-Agent: FreeSWITCH-mod_sofia/1.5.15b+git~20141230T150632Z~1965b3b18d~64bit
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY
Supported: timer, path, replaces
Allow-Events: talk, hold, conference, refer
Privacy: none
Content-Type: application/sdp
Content-Disposition: session
Content-Length: 251
P-Asserted-ID: "George F Phelps", <sip:1404XXXXXXX@66.33.147.150>, tel:+1404XXXXXXX
X-FS-Support: update_display,send_info
P-Asserted-Identity: "George F Phelps" <sip:1404XXXXXXX@54.174.255.168>
v=0
o=FreeSWITCH 1420520731 1420520732 IN IP4 54.174.255.168
s=FreeSWITCH
c=IN IP4 54.174.255.168
t=0 0
m=audio 25598 RTP/AVP 0 8 101 13
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20
------------------------------------------------------------------------
…that there is apparently both a “P-Asserted-Identity” and a “P-Asserted- ID” header. What’s up with this? Are there two different headers? Is the Freeswitch SIP trace a formatted dump of the SIP packet, or is it a series of debug printf statements from where the data is added to the packet?
Thanks,
George
*From:* freeswitch-users-bounces@lists.freeswitch.org [mailto: freeswitch-users-bounces@lists.freeswitch.org] *On Behalf Of *Michael Jerris *Sent:* Monday, January 05, 2015 1:34 PM *To:* FreeSWITCH Users Help *Subject:* Re: [Freeswitch-users] Multiple P-Asserted-Identity Headers
put them together as a single header separated by a comma. http://www.ietf.org/mail-archive/web/sip/current/msg17485.html has more info.
On Jan 5, 2015, at 6:56 AM, George F. Phelps <GeorgePhelps@gfphelps.com> wrote:
How do I create two (2) unique, P-Asserted-Identity headers? As required by *RFC 3325 <http://www.ietf.org/rfc/rfc3325.txt>*:
A P-Asserted-Identity header field value MUST consist of exactly one name-addr or addr-spec. There may be one or two P-Asserted-Identity values. If there is one value, it MUST be a sip, sips, or tel URI. If there are two values, one value MUST be a sip or sips URI and the other MUST be a tel URI.
A valid, multiple P-Asserted-Identity headers example, taken from RFC 3325:
INVITE sip:+14085551212@proxy.pstn.net SIP/2.0
Via: SIP/2.0/TCP useragent.cisco.com;branch=z9hG4bK-124
Via: SIP/2.0/TCP proxy.cisco.com;branch=z9hG4bK-abc
To: <sip:+14085551212@cisco.com>
From: "Anonymous" <sip:anonymous@anonymous.invalid>;tag=9802748
Call-ID: 245780247857024504
CSeq: 2 INVITE
Max-Forwards: 69
P-Asserted-Identity: "Cullen Jennings" <sip:fluffy@cisco.com>
P-Asserted-Identity: tel:+14085264000 <+14085264000>
Privacy: id
When I use the following two (2) statements in a Freeswitch dialplan, the second “set,” of course, overwrites the data stored by the first “set.”
<action application="set" data="sip_h_P-Asserted-ID=tel:+1404XXXXXXX"/>
<action application="set" data="sip_h_P-Asserted-ID="George F Phelps" <sip:1404XXXXXXX@YY.YY.YYY.YYY>"/>
Thanks,
George
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org