Obi Number, incoming works, outgoing doesn't

<< < (2/4) > >>

matc:
I just removed one of the remote ones and re-added that (having previously not read what you wrote and only removed and re-added mine). Nope. They can call my OBiTALK number, me calling them results in 900.

Out of interest I turned on a 202 I had in drawer, and I can dial that successfully. I'm in UK, the 2 remotes are in Italy, but they are just used for OBiTALK so am now at a total loss!

azrobert:
Can the 202 call the remote OBi's?

matc:
Y'see, why did I not think of that?
Dug out a phone and yes, it can reach them both.
Does this point you towards something? Fingers crossed.

Edited to add: both behind same router, the 1032 wired, 202 WiFi.

azrobert:
How are you calling the other devices? Are you dialing "**9xxxxxxxxx"? Did you check the call history to see if the number is being sent to OBiTalk correctly? It should be sent to OBiTalk in format "obxxxxxxxxx". If this looks good, I have no idea what's wrong.

You can call the other devices 2 different ways.

You can call the other devices using an SIP provider. If Sipgate allows multiple extensions, define 2 more extensions for the other devices and call them using their extension number. If Sipgate doesn't allow multiple extensions, you can get a free account from Callcentric or 2 accounts at SIP2SIP.

You "Should" be able to use the OBi202 to forward 1032 OBiTalk calls to the other devices. This would be the easiest setup. Just define 2 speed dials then make a one line change on the OBi202.

azrobert:
Quote from: matc on February 09, 2020, 06:53:07 am

both behind same router, the 1032 wired, 202 WiFi.


Try removing the WiFi dongle from the 202 and plug it directly into the router to see if it will now fail. I don't know why this would make a difference, but I've seen a lot of strange things happen.

Navigation

[0] Message Index

[#] Next page

[*] Previous page