Page History

...

1.)   Download the configuration file - this contains all the known stable generic settings. Downloading and restoring the OBI110 config from this file will minimize the amount of end user configuration performed.

2.) Determine where the cable connecting your intercom/paging system to the legacy phone system is located. In general, trace from the intercom system itself to the legacy phone system. Please make careful notes as to which cable is removed from the legacy phone system switch as it may be the incorrect cable and it makes reverting back to the legacy setup simple.

3.) In the OBI110 web configuration accessed via its IP Address, under System Management → Device Update, select Choose File under the Restore Configuration. This should be the obi110.xml from the first step. Hit Restore then allow the OBI110 to restart. This particular reboot may take a few minutes.

4.) When the OBI110 is available again, make the following changes to its configuration (and reboot it after saving each submitted change). The credentials for all the following changes are from the Pre-Configuration section above:

• Service Providers → ITSP Profile A → SIP: Set ProxyServer and RegistrarServer to be the primary VoIP server hostname the OBI110 is configured to in NocTel.
• Voice Services → SP1 Service: In the SIP Credentials section, set the contents of the AuthUserName and AuthPassword fields with the SIP user and SIP password from NocTel, respectively.

With these changes the OBI110 is generally configured and sanity testing should be conducted.

Testing the OBI110

Prior to testing if the OBI110 is configured properly for the legacy intercom/paging system, you should have a list of dial codes used by the system on hand. It is recommended to test both specific rooms/zones and all call as the dial codes are typically a different format (to prevent an all call when a room was intended to be paged). These dial codes will vary by the vendor of the intercom/paging system as well as the organization's own programmed codes. NocTel is unable to retrieve or deduce dial codes - contact your organization's technical support or the vendor of the system for assistance in the event you do not know what each dial code is or how it is programmed.

When testing the OBI110 configuration, the following steps and events generally occur:

-After dialing the OBI110 extension, after 1-2 rings there should be a different, distinct dial tone - this indicates the OBI110 successfully called into the intercom/paging system and the system is now pending a dial code.

It is possible with incorrect configuration or what the OBI110 uses to contact the intercom/paging system that an error tone is produced. Dead air is also possible and in most cases indicates an improper configuration of the OBI110, though it is possible that the cable connected to the OBI110's Line port is the incorrect one for the system.

-If you get the different, distinct dial tone have the appropriate staff available to perform test calls. Avoid having NocTel engineers or technical staff perform these test calls as the calls may interrupt regular operations - an unfamiliar voice may cause distress. Preferably, perform these test calls before or after normal hours.

• After inputting a valid dial code for the system, there should be no tone on the handset - this typically indicates you are free to speak.
• If there is no output after speaking, this may indicate an incorrect dial code to the intercom/paging system. Some vendors may play an error tone if the dial code is invalid, while others may silently fail.
• When finished conducting the test, hang up normally to terminate.
  
  

Related articles

...