[VoiceOps] Caller-ID: SIP From vs. P-Asserted-Identity
ryandelgrosso at gmail.com
Mon Jul 23 23:14:42 EDT 2012
In an inter-carrier agreement I have never seen any restrictions placed
on what could or could not be sent. In end-user trunks that is largely
up to how the carrier dealing with the end user wants to handle it, I
can tell you for end user trunks we generally restrict the calling
number to one that the customer has on their trunks, but for wholesale
to other carriers we allow them to send anything since it isn't usually
a bi-directional trunk in those scenarios.
On 07/23/2012 07:53 PM, Paul Timmins wrote:
> Better question, why is the carrier letting you specify the billing telephone number? Isn't that a massive security flaw? Or is this an additional layer of accounting?
> On Jul 23, 2012, at 22:38 , Ryan Delgrosso wrote:
>> I have to agree with Alex on this one.
>> Only one matters and they are weighted in that order.
>> If you need the billing number to be different than the highest applicable in the above list, insert a diversion header and be done with it (warning not all term carriers properly obey diversion headers but it is the most correct answer)
>> On 07/23/2012 02:45 PM, Jay Hennigan wrote:
>>> On 7/23/12 2:34 PM, Eric Wieling wrote:
>>>> Set a Diversion: header to specify the CallerID number.
>>>> Diversion: <sip:+12125551212 at 172.17.5.11>;reason=rcf
>>>> The ;reason=whatever is optional, I don't know of any carriers which use it.
>>> That would likely work, but it is easier said than done. Sometimes it
>>> isn't diverted. An agent in a pool wants to display the pool inbound
>>> number in CLID but keep the individual number for billing and CDRs. Or
>>> the IAD on site doesn't support diversion headers, etc.
>>> Jay Hennigan - CCIE #7880 - Network Engineering - jay at impulse.net
>>> Impulse Internet Service - http://www.impulse.net/
>>> Your local telephone and internet company - 805 884-6323 - WB6RDV
>>> VoiceOps mailing list
>>> VoiceOps at voiceops.org
>> VoiceOps mailing list
>> VoiceOps at voiceops.org
More information about the VoiceOps