Obi Number, incoming works, outgoing doesn't

<< < (4/4)

matc:
Quote

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

Care to talk me through that please?

azrobert:
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.

matc:
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.

GeeObi:
Maybe it's a bug in firmware 4983. Why don't you try 4858?

matc:
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.

Navigation

[0] Message Index

[*] Previous page