Many customers are used to being able to meet local calls from there traditional telephone services, however in today’s advanced age of Multiple destinations a person’s telephone number isn’t locally defined like it was back in the days playing telephone service.
It should be noted that solutions such as the Avalo Voice Platform permit for an ever expanding realm of localization. Still at the customer wants what the customer wants and it’s important that we replicate dialing methods they are used too.
As such of Avalo is capable of excepting a seven digit destination within the North American dialplan granted the following environmental conditions are set.
In all cases the area code is required when making calls over the Avalo Voice Platform. So the question remains how do I take a seven digit number and make it ten. That is a very simple issue to resolve.
In just about every case with regards to local dialing caller ID will contain The area code of the customers local calling region. Our platform simply parses the telephone number associated to the transmitted caller ID and pretends it to the seven digit number of the caller’s destination.
With that understood it’s important that we determine the best way to present the caller ID so that the platform can correctly parse the number and build the pretend substrate. Below are several scenarios that can be used by the platform to masquerade and allow for customers to complete a local call dialing 7 seven digits.
Scenario 1:
SIP trunking has become an extremely popular method of creating IP conductivity to the PSTN. The Avalo Voice Platform supports SIP trunking via it’s PBX Connector, and also in a more advanced method which is known as an Enhanced SIP Trunk and administered via the Callflow Manager. However in both cases local seven digit dialing is still reliant on the presentation of the valid caller ID, however It should be noted that the caller ID is not set by the Avalo Voice Platform in any way and that the Caller ID transmitted when the call is made will be used to construct prepend substrate.
This means that if you were doing a call forwarding through the PBX you must present a minimum of 10 digits in order for the call to complete properly since most cases the caller ID of the A-leg or initializing party Will be used on the B-leg outbound call. As such if you presented 7 digits the Avalo Voice Platform went parse the Presented caller ID an extract the area code. This could be wrong area code for the final destination.
A good rule of thumb is to to always attempt to present minimum of 10 digits when trying to make a domestic North American dial plan call. If you’re able to do the pre-pending in the dial plan of the PBX for a local seven digit call that is optimal.
Scenario 2:
In the event you were using hosted PBX application with in the Avalo Voice Platform, Seven digit dialing area code prefixing is handled automatically Based on the caller ID settings defined in the account configuration. The hierarchical caller ID structure with in the hosted PBX application still remains true.
Scenario 3:
If you are attempting to do a remote call forward or any forwarding to the PSTN just like in scenario 1 you should present a minimum of 10 digits. The same mechanism used in SIP trunking to construct the pretended destination number is used globally throughout the platform.
We hope that you find this basic understanding how seven digit dialing works useful. If you have any questions please feel free to contact technical support.