User guide

12
MultiVOIP 400/800 User Guide
Now, lets change the typical application to not have the Gatekeeper control the call session. When
you elect to use the Proprietary PhoneBook, you set up a master-slave relationship. This relationship
allows one MultiVOIP to maintain the Phone Directory Database and publish this data base to all
MultiVOIP participants in the network. This proprietary data base allows you to see all the
participants in your network and provides you with there phone numbers.
Lets again use the corporate MultiVOIP and we will set up the database so that the corporate
MultiVOIP can call the sales, marketing, or regional offices. To do this, the Phone Directory Database
will have four entries for the corporate office, and two entries for the sales office, two for the
marketing office and two for the regional office. Extension 101 at the corporate office is tied to voice
channel 1, 102 is tied to channel 2, etc. The Description again ties to the type of interface used on
the corporate MultiVOIP (E&M). The Hunt Group in this situation is set for No Hunt. But if you
wanted to activate a Hunt Group, i.e., if an extension on the MultiVOIP is busy and you wanted to
look for another extension, you can assign a hunt group to those extensions. So that, say extension
101 is busy, the corporate MultiVOIP would roll over to extension 102.
Again, the IP Address of the corporate MultiVOIP needs to be added and the port number is 1720.
This adds phone number 101 of the corporate MultiVOIP to the proprietary data base. Now, to add
extension 102 to the proprietary data base, all you have to do is change the Phone Number and
Description to support channel 2 of the corporate MultiVOIP. After you have added channel 2, you
need to include the two entries for each office.
The proprietary data base would then appear as in the following dialog box and when the office
MultiVOIP is turned on, the current data base would be down loaded.