September 18, 2020, 04:08:38 pm *
Welcome, Guest. Please login or register.
News:
 
   Forum Home   Search Login Register OBiTALK  
Pages: [1]
  Print  
Author Topic: Obi Number, incoming works, outgoing doesn't  (Read 3437 times)
matc
Newbie
*
Posts: 13


« on: February 08, 2020, 05:03:49 am »

[Removed from wrong section and reposted here]

Hello. On Obi1032, from one day to next, cannot reach 2 OBi numbers, ends up with error 900. They, however, can reach my OBi Number. No firewall, no router changes. Stumped. Any ideas of where to begin looking? Sipgate is working fine in and out, just the OBi numbers that cannot be reached.

All configs are local, not through OBitalk.


Logged
matc
Newbie
*
Posts: 13


« Reply #1 on: February 08, 2020, 07:04:49 am »

Have reset, reconfigured, reloaded latest firmware, still 900 fail on both outgoing OBitalk OBi numbers. Anyone else having problems starting 2/3 days ago? Something needing changing on router?
Logged
matc
Newbie
*
Posts: 13


« Reply #2 on: February 08, 2020, 07:22:06 am »

Excuse me just blethering on here, talking to myself ... just to say that the echo service is working, all lights are green on the Obitalk dash, and have had remote units rebooted ... still nothing. Really hoping this is some sporadic issue withe the Obitalk servers.
Logged
azrobert
Hero Member & Beta Tester
*****
Posts: 4030


« Reply #3 on: February 08, 2020, 10:07:05 am »

All configs are local, not through OBitalk.

Have all the devices been added to OBiTalk using **5xxxx?

Edit:
And removed and re-added from OBiTalk after reset?
« Last Edit: February 08, 2020, 10:09:31 am by azrobert » Logged
matc
Newbie
*
Posts: 13


« Reply #4 on: February 08, 2020, 11:06:12 am »

Thanks for response. Yes, have done that a few times. Just now tried something different, removed the 1032 from OBiTalk, re-added it and then used Expert Configuration for the first time, rather than just local config.

Still not working on OBi Number. Sipgate working fine. Only difference I can see after using 'Expert' is that buttons 1 and 2 of the 8 are now unlit, but both lines are working.
Logged
matc
Newbie
*
Posts: 13


« Reply #5 on: February 09, 2020, 01:45:19 am »

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!
Logged
azrobert
Hero Member & Beta Tester
*****
Posts: 4030


« Reply #6 on: February 09, 2020, 06:34:46 am »

Can the 202 call the remote OBi's?
Logged
matc
Newbie
*
Posts: 13


« Reply #7 on: February 09, 2020, 06:53:07 am »

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.
« Last Edit: February 09, 2020, 07:00:32 am by matc » Logged
azrobert
Hero Member & Beta Tester
*****
Posts: 4030


« Reply #8 on: February 09, 2020, 07:32:24 am »

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.
Logged
azrobert
Hero Member & Beta Tester
*****
Posts: 4030


« Reply #9 on: February 09, 2020, 07:54:44 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.
Logged
matc
Newbie
*
Posts: 13


« Reply #10 on: February 09, 2020, 08:17:16 am »

Yes, OBi numbers being sent correctly **9 300 348 *** fails with 900, whereas **9 222 222 222 works just fine.

The 202 can reach both remotes on wired as well, so this is clearly something funky with the 1032. I've just factory reset it and pedantically followed the steps in the 'official' post, still the same ... **9 222 222 222 works, I can reach the 202 OBiTALK number, but neither of the remotes (an admittedly ageing 100 and a 110).

Utterly stumped, and very frustrated. This setup has worked, untouched, for years, nothing whatsoever has changed that I know of. Your help is appreciated.
Logged
azrobert
Hero Member & Beta Tester
*****
Posts: 4030


« Reply #11 on: February 09, 2020, 08:52:12 am »

I have an OBi1032 and an OBi110 and can call the 110. Check if you have current firmware. I have 4858EX (not latest) on the 1032 and 2886 on the 110.
Logged
matc
Newbie
*
Posts: 13


« Reply #12 on: February 09, 2020, 09:01:52 am »

4983EX.1311 on 1032
1.3.0 (Build: 2872) on 100 - is that old now, have not looked in a long while?
Logged
matc
Newbie
*
Posts: 13


« Reply #13 on: February 09, 2020, 09:26:34 am »

I see that it is newer, the last version. Will try updating as soon as there's someone physically 'at' the device. Cheers.
Logged
matc
Newbie
*
Posts: 13


« Reply #14 on: February 10, 2020, 01:36:57 am »

Aw well, 2886 loaded and still no difference. They can call me on OBiTALK, I cannot call them.
Looks like I need to try new devices.
Very very odd.
Logged
matc
Newbie
*
Posts: 13


« Reply #15 on: February 10, 2020, 02:30:34 am »

Quote
Just define 2 speed dials then make a one line change on the OBi202.

Care to talk me through that please?
Logged
azrobert
Hero Member & Beta Tester
*****
Posts: 4030


« Reply #16 on: February 10, 2020, 06:11:15 am »

111111111 = 1032 OBi Number
222222222 = 202
333333333 = remote#1
444444444 = remote#2

Setup 2 speed dials
pp(222222222*1)
pp(222222222*2)

202 OBiTalk InboundCallRoute:
{111111111>1:pp(333333333)},{111111111>2:pp(444444444)},{ph}

Speed dials will send a "1" or "2" to the 202
202 will check for the "1" or "2" and forward the call to the remotes.
I did NOT test this, but have done a similar setup in the past.
Logged
matc
Newbie
*
Posts: 13


« Reply #17 on: February 10, 2020, 06:14:39 am »

Much appreciated, looks very logical, will test this now for use the next time, because, with tedious inevitability, things have just now started working again! Must have been an issue with Obitalk servers, at a guess.

Also, thanks for the Callcentric steer - the free IP Freedom plan looks to be perfect and will also test that.
Logged
GeeObi
Jr. Member
**
Posts: 31


« Reply #18 on: February 10, 2020, 12:19:41 pm »

Maybe it's a bug in firmware 4983. Why don't you try 4858?
Logged
matc
Newbie
*
Posts: 13


« Reply #19 on: February 12, 2020, 06:36:12 am »

As I said above, the OBiTALK number just started working again after 2 or 3 days, nothing obviously to do with what I had done, I am presuming this was something on OBiTALK server side.

Many thanks to azrobert for his suggestion of using Callcentric and free extensions (well, the whole thing is free using their 'IP Freedom' plan) - have not got Callcentric setup as an SP line on all devices for the next time this happens. Callcentric have some great setup guides for OBi devices and, as long as you remember to select the correct profile if you already have another SIP account active, they work flawlessly.
Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by SMF 1.1.11 | SMF © 2006-2009, Simple Machines LLC

Advertisement
Advertisement