3KB / Pyxis Solution ID - 3KB6239
By default, when setting up NBX dial plans for VTL, the Caller ID will be in the form:
{ip_address}{extension_number}, for example 192*168*1*190*100. This is what will be seen
if extension 100 at site A calls an extension at site B, on the Site B phone LCD display.
It has become fairly well-known that you can tailor the Caller ID so that the site-to-site
extension calls will show a customized label in the LCD, if a Pretranslator is set up with
the VTL channels as Devices Using, matching the sender's site IP address, and replacing that
IP address with a site name. For example, if a Site B phone gets a call from extension 100
at Site A, instead of seeing "192*168*1*190*100" it can be customized to read "Dallas:100"
or "100:Dallas", or other customization on a per-site basis and matching on the incoming IP address.
While this works well to spruce up the LCD for internal calls between sites, it does not
address hopoff calls, where extension 100 at Site A may dial 918005551234 and that call needs
to dial out the PSTN from Site B via VTL hopoff over a PRI, BRI, or T1 where the NBX is presenting CIDIt is often required from telco that the outbound caller ID be a 10-digit numeric string, and
if the caller ID is "Dallas:100" telco may reject the attempted outbound call.
To get around this, create a standard CLIP pretranslator (Outbound Caller ID pretranslator) just
as you would normally, even without multiple sites or VTL, at the site with the PRI/BRI/T1.
If there is already an outbound CLIP pretranslator, you will only have to add additional
pretranslator entries.
Add pretranslator digit matching entries to the standard CLIP pretranslator, to match each of the
other site's caller ID that would be doing PSTN hopoff through this site. The pretranslator digit
matching entry will depend on whether you have customized the caller ID using a VTL LCD formatting
pretranslator or not. For example, by default, the caller ID for a VTL call might be
192*168*1*190*100. For this calling site, for hopoff, add 192*168*1*190 to the standard outbound
CLIP pretranslator, and either do a REPLACE dial plan command to post the calling site's 10 digit
BTN (billing telephone number), or, you could do several steps such as striplead 14 (in this case,
to strip off "192*168*1*190*" (leaving just the calling extension), and then prepend "5083231" for
example, to rebuild the proper DID for this extension, so that a final caller ID of 5083231100 would
be sent to telco as the Calling Number. If you are already using a VTL LCD formatting pretranslator,
and the caller ID reads something like "Dallas:100" for internal extension calls over VTL, you
would add "Dallas:" instead of "192*168*1*190" as the CLIP pretranslator matching digit entry. In
this manner you can match any site uniquely for hopoff, and present any desired 10 digit number
to Telco for the Calling number outbound Caller ID. You can be as granular as you wish, and could
actually match specific extensions from specific sites, and present any distinct number, such as
a departmental DID number for that site, or an 800 number, or, for specific "Executives" wishing to
hide just their DID, you could present that site's main phone number instead of the DID for one
or more extensions. For example, match "Dallas:149" as a specific match, replace with any phone
number, in order to present something different just for extension 149 doing hopoff calls from
Dallas. This would be in addition to a generic "Dallas:" matching entry that might do a static
BTN replacement, or a prepend of specific digits to rebuild the DID number for all other extensions at that site.