Identifying outbound calling id?

[johnnywan]

Multiple sites collapse back into 1 central MGCP GW for PSTN connectivity via a PRI. Using E911 (RedSky) so 911 is not an issue, but, is there a way to tag the calling number on an outbound call to display different caller id from each bldg out a single PRI? Right now obviously all outbound calls are id'ing as the main number of the main site PRI. Thanks in advance.

[Joseph Martini · Accepted solution]

Assuming your provider will allow a different caller ID without over writting it, you can setup multiple route patterns and set a calling search space for each building to hit a certain router pattern that could have a different calling party transformation.

[William Bell · Accepted solution]

It depends. If you mean to leverage DIDs provisioned by the CO on trunks in your main building, then you should be fine. If you wish to leverage DIDs that would be associated to trunks/geographic areas tied to your remote office buildings, you may run into obstacles.  For reasons like toll fraud and life safety, a carrier will typically filter out any calling number information where the calling number does not match a DID provisioned on the trunk/trunk group. In some cases, you can negotiate this "feature" into your contract.  Essentially, this contract would put all perceived liability onto your company. I have only seen it done twice, usually the carrier will ignore such requests unless you represent a large source of revenue for them.

Now, going back to scenario 1 where we assume you are attempting to transform CLID to a DID provisioned on your Main site trunks. You could use separate route patterns (1 set per site) where you make the transformation. You could also leverage Transformation Patterns on your Main site voice gateways to accomplish the task with fewer configurations. This approach would assume that you have some way to easily identify the extensions assigned to the remote site phones.

HTH.

Regards,
Bill

[johnnywan]

Excellent information. Thank you both!