...
This section presumes the OBI110 is new out of box and never accessed or configured. Out of box, the OBI110 will default to DHCP to obtain an IP address so it may be necessary to leverage network appliances to discover what IP address the device has been assigned. This is typically done by accessing the switch port the OBI110 was connected into on its ethernet port or querying a firewall or switch for the IP address of the device with the OBI110's MAC Address.
...
- Incorrect settings used for the OBI110 extension in NocTel
- Forgot to create a NocTel extension for the OBI110VoIP server configuration in NocTel for the OBI110 changed without updating the SIP user and password credentials on the OBI110 as well
- Improper settings for LineInUseVoltageThreshold and/or LineInUseCurrentThreshold
- 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)
...
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. The OBI110 should appear in the NocTel control panel with the status available if it was able to register properly with the assigned VoIP serverit's possible the Line in Use voltage from your intercom/paging system varies such that some calls fall outside the expected value.
Also ensure the OBI110 is cabled up properly. The most likely case would be the wrong cable used to connect the intercom/paging system to the OBI110's Line port or connecting to the Phone port instead of the Line port.
Busy Signal When Dialing the OBI110 Extension
...