Chapter 5: Phonebook Configuration

The simplest case is a call from Baltimore to a phone within the Minneapolis/St. Paul area code where the company’s VOIP and PBX are located, namely 763. In that case, that local VOIP removes 1763 and dials 9 to direct the call to its local 7-digit PSTN.

Finally, consider the longest entry in the Minneapolis Inbound Phonebook, “17637175. Note that the main phone number of the Minneapolis PBX is 763-717-5170. The destination pattern 17637175 means that all calls to Minneapolis employees will stay within the suburban Minneapolis PBX and will not reach or be carried on the local PSTN. Similarly, the Inbound Phone Book for the Baltimore VOIP (shown first below) generally matches the Outbound Phone Book of the Minneapolis VOIP (shown second below).

Figure 5-11: Inbound Baltimore example

Notice the extended prefix to be removed: 14103257. This entry allows Minneapolis users to contact Baltimore co-workers as though they were in the Minneapolis facility, using numbers in the range 7000 to 7999.

Note also that a comma (as in the entry 9,443) denotes a delay in dialing. A one-second delay is commonly used to allow a second dial tone to be generated for calls going outside of the facility’s PBX system.

The Outbound Phone Book for the Minneapolis VOIP is shown below. The third destination pattern, “7” facilitates reception of co-worker calls using local-appearing-extensions only. In this case, the “Add Prefix” field value for this phonebook entry would be “1410325”.

Figure 5-12: Outbound Minneapolis example

Multi-Tech Systems, Inc.

92

Page 92
Image 92
Multi-Tech Systems MVP210/410/810-FX, MVP210/410/810-SS manual Inbound Baltimore example