Can I change Caller Number to Caller Name in P-Asserted-Identity and/or Remote-Party-ID headers sended from my S20 to Sip Peer trunk?
For example I got Remote-Party-ID: "115" <sip:115@192.168.100.100> but I need "John Doe" <sip:115@192.168.100.100> as a header From
P Asserted Identity and Remote Party ID options are enabled (I have tried all options: Default, Extension Number, DOD number) in Trunk Properties -> Advanced -> Outbound Parameters
Yeastar S20 30.10.0.16
The answer is yes. Go the the advanced tab in the trunk and look for the outbound settings. You can change using the pull down for RPID and PAI. While you can change these, and they will be sent to the provider, the provider may not accept, but no harm in trying.
Hi， Вениамин,
Got your feedback, let me try from our side then update you
Did you reboot the PBX after applying the changes? Try creating a new extension and test again. Sometimes changing the Outbound parameters doesn't take effect by just save/apply (although it should).
I am having the same issue and cannot figure this out.
What are you trying to do exactly? There are headers within a SIP message that can be manipulated to a degree. However, the other end may also elect as to what it will accept and what it will not. In some cases, a provider will not allow/accept the change, so more detail is needed as to your expectations and what you want the final receiving device to show and we also need to know your country/locale.
Basically, my SIP provider needs the account username in the From and Contact elements.
So I have to send either Remote Party ID/ P Asserted Identity to get the right outbound caller ID.
When I enable Remote Party ID and set it to DOD.
I've tried leaving DOD blank and configuring it per extension, and get the same result.
It builds the packet with my phone number in both the Caller ID and the Caller Number Field
What I think I want is this.
Hi Andrew, did you try it on the latest version?
How about configure the DOD like this?
Yes I tried this as well. After contacting Yeastar support they confirmed that Yeastar will currently always send the Number in both the Number and Caller ID name fields of the Invite packet on outbound calls.
They said they would take an enhancement request for this DOD Name to be used in the future.
I myself do not really understand the implications of this being wrong, since the receiving caller is just looking up my phone number for the name anyways. So everyone sees the correct Caller ID name from me because of the lookup. It just looks weird in my VOIP providers CDR logs.
What you are trying to do seems odd. It is not clear to me that they really want your name "Andrew" as this then implies that they know your name and that it would possibly change for every extension.
PAI, RPID are not the headers that are used for the contact or connection info. Both of these (RPID and PAI) are other headers that are informational only so that, if the provider allows it, you can customize the info CID as seen on the other end. CId can also be in the FROM header.
Are you using a register trunk or peer?
They don't really want "Andrew" they want my full name to go through. It would be the same name I have registered in the CNAM database.
I am using a register trunk through VOIP.MS, which is a Candian based company so maybe they are applying some of that logic to my support case. According to their Wiki, it appears you can just pass through your Caller ID name and receivers accept that name without looking up in a CNAM database.
I'm starting to think this really doesn't matter as long as I am calling US numbers and I have the CNAM updated accordingly.
https://wiki.voip.ms/article/Caller_ID
If you will be making calls to Canadian numbers, you can simply pass the Caller ID name from your device or system as most of them support this. You will need to check for a field on the interface from the device to enter this setting, and in case you are using a more advanced system, get assistance to set the outgoing Caller ID name set up.
The Caller ID name on US calls works differently, this is controlled by a national CNAM database with records of numbers and names matching each number. When you make a call to a US number, you will send a Caller ID number and the system will check the CNAM database for a name matching that same Caller ID number in order to display both name and number to the final phone.
It depends:
In Canada, many carriers will allow the subscriber to send Cnam info.
In the US, the delivering PSTN carrier will do a dip into a Cnam database to match the CID sent in the call. If the carrier is SIP and the call is "on network" the carrier "may allow" the Cnam info as sent to be delivered. It is not necessarily a single national Cnam database as the carriers may elect to maintain their own or may subscribe to one as there are several out there. As it is the delivering carrier who presents Cnam, they really only have to consider the names of their subscribers and not everyone from all carriers.
If calling a cell phone, Cnam is typically not delivered, unless the subscriber's carrier provides or offers a subscription to same and if neither is used, then no name is delivered and the cell will use its internal contacts in an attempt to match.
The reason that more SIP carriers are allowing manipulation is because SIP is not tied always tied to a single physical location, I can have a PBX in Texas with remote workers in NY, FL, and CA and I can manipulate to the extent that should one dial 911, the CID shown at the e911 center will tie to their address and not that of the PBX.
If you have no need to do anything fancy, then you are likely good to go as is.
Unified Communications
