...
| Info |
|---|
Note: When adapting over, you may notice a brief delay between when speaking and when the intercom/paging system plays out. This is a side effect of adapting from using a direct physical line between a POTS handset to the intercom/paging system to a VoIP adapted system. The delay experienced will vary based on network latency from the speaker's handset to the OBI110 into the intercom/paging system |
-If you get a busy signal or dead air, it is possible the Line In Use voltage needs to be adjusted. The correct value will vary by vendor and setup. Use the LINE & PHONE status interface on the OBI110 web UI before placing a call and when one is received. The voltage should change readout on the Line port in both cases - use this to make gradual adjustments to the LineInUseVoltageThreshold under Physical Interfaces → LINE Port and possibly the LineInUseCurrentThreshold in the same section. Don't forget to reboot the OBI110 after making changes for them to take effect.
- You may experience the case where the OBI110 is sometimes able to successfully connect to the intercom/paging system and sometimes fail to do so. This is usually due to the LineInUseVoltageThreshold setting not fully overlapping with the Line In Use voltage variance. Use the same troubleshooting guidance above.
Common Troubleshooting
As with any configuration for integration, there are a number of missteps and incorrectly input settings. This section identifies several common problems and recommended resolution:
Dead Air When Dialing the OBI110 Extension
Causes:
- Incorrect settings used for the OBI110 extension in NocTel
- Forgot to create a NocTel extension for the OBI110
- VoIP server configuration in NocTel for the OBI110 changed without updating the SIP user and password credentials on the OBI110 as well
- Intercom/paging system cable connected to the Phone port when it should be in the Line port
- Incorrect cable for the intercom/paging system is connected to the OBI110's Line port
- OBI110's ethernet port is connected to a switch that does not have the port configured for voice VLAN (or whatever configuration is used for NocTel handsets)
Fixes:
This can occur if the OBI110 generic SIP device extension is improperly configured. In the NocTel control panel ensure the extension exists, is of generic SIP device type, and the SIP username, password, and VoIP server address are correct. If you have specified different VoIP servers for the OBI110 extension, use the VoIP server address of the primary server.
If the OBI110 was functioning correctly prior, this is likely that the VoIP server configuration changed. Changing the VoIP server(s) also regenerates the SIP user and password credentials. These need to be updated on the OBI110 or the device will not register with the VoIP server correctly.
Also ensure the OBI110 is cabled up properly. The mostl likely case would be the wrong cable used to connect the intercom/paging system to the OBI110's Line port.
Busy Signal When Dialing the OBI110 Extension
Causes:
- Improper settings for LineInUseVoltageThreshold and/or LineInUseCurrentThreshold
Fixes:
Modify the above setting(s) accordingly. The appropriate values for a particular system can be inferred based on the outputs for the LINE Port, which can be found under Status → PHONE & LINE Status. The voltages will change depending on what's occurring between On Hook and In Use.
Related articles
| Content by Label | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...