OBI-100 call failure to OBI110

(1/3) > >>

Demos:
I am not able to reach an OBI-110 from two OBI-100 ATA's over the Obitalk network. I reach a recording that reads out the Obihai device (Telephone) number, and ends with a 404 statement.

The OBI-110 can dial out & reach both OBI-100's OK, and can also call complete to the call echo test line **9 222 222 222 OK.

drgeoff:
No need for multiple posts. We heard you the first time.

Too soon to say for sure but maybe not just you.  http://www.obitalk.com/forum/index.php?topic=14555.0

Demos:

I have had difficulty getting a post on this forum, so forgive any multiple and redundant posts. Until now I have been loosing my posts and attempts to send an internal e-mail.

A more detailed explanation of the trouble is below (The trouble described at the supplied link differs in terms of the trouble condition encountered at a OBI-100 ATA) 

I am not able to reach an OBI-110 from two OBI-100 ATA's over the Obitalk network. From the OBI-100's, I reach a recording that states that the call will not go through, reads back the Obi-110 Obitalk device number called (**9 123 456 789) and ends the announcement with a 404 statement.

The failed call announcement appears to be not network based, but appears to be generated locally as a result of a call reject response from the Obitalk server.

The OBI-110 can dial out & reach each OBI-100 OK, and all ATA’s can call complete calls to the  echo test line **9 222 222 222 OK. Both OBI-100's can call each other over the Obitalk network OK.

All three ATA's are configured on SP-1 with a VoIP provider, and authenticate & call complete via the VoIP service providers network OK.

OBI-110 primary line is configured for SP1. A factory reset (Hard or soft Reset) ob the OBI-110 does not clear the trouble. Auto provisioning has been disabled on all OBI ATA's.

Thank you in advance

drgeoff:
Quote from: Demos on July 24, 2018, 10:12:23 am

The trouble described at the supplied link differs in terms of the trouble condition encountered at a OBI-100 ATA



The crux appears the same to me. Cannot reach an OBi110 over the Obitalk network.

My hunch is a partial failure of the database on an OBihai server that maps the 9 digit OBi number to its current IP address. OBi110s have a different set of digits at the start of their numbers. Maybe that part of the database is corrupt. Just a guess.

Update. It is not all 110s. I can call both of mine over the Obitalk network.

drgeoff:
Wonder if http://www.obitalk.com/forum/index.php?topic=14554.0 is another manifestation.

Do the unreachable OBi's show as "Offline" on the Obitalk Dashboard?

Navigation

[0] Message Index

[#] Next page