I drug out an OBi200 that I was not using to put back in service with Localphone and a couple od GV numbers I have setup with the Simon GV Gateway. I dont want to connect a phone to it as I dont have any more desk space available. I decided to have all inbound calls go to my OBi1032 IP Phone.
I setup the OBi200 InboundCallRoute as {pp(ob610xxxxxx),ph} on SP1, SP2 and SP3
On SP1 Localphone no ringing. I will deal with that later.
On my OBi200 Call Hisyory it shows for both calls from SP2 and SP3 (Simon GV Gateway)
Fork to:
PP1(ob610xxxxxx)
PH1
Ringing (PH1)
21:30:55 Call Failed (486 Busy Here; PP1(ob610xxxxxx))
That seems strange as my OBi1032 is NOT busy on a call.
"Busy Here" simply means that the Obi1032 has rejected the call for some reason. It may be that it cannot accept the CallerID of the OBi200. Are the any rules here that might reject the OBi200 CallerID:
OBi1032
Voice Services > OBiTALK Service > InboundCallRoute
For testing purpose using one single rule of ph here would accept any calls.
Calls can be rejected for other reasons such as incompatible codecs being used.
Hi Ian,
On SP1 InboundCallRoute is ph
On SP2 through SP6 I have ph,sp2(18667326184@tollfree.alcazarnetworks.com;ui=$1)
That is for NoMoRobo spam filtering.
The OBi1032 will receive the forwarded call via OBiTALK not via sp1 - sp6. Have a look here:
OBi1032
Voice Services > OBiTALK Service > InboundCallRoute
I figured that so I got to thinking that the ObiTalk trunk DigitMap has to be changed as forking the calls is probably passing CID.
So I changed the ObiTalk DigitMap from (<ob>xxxxxxxxx|obxxxxxxxxx)
to (1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|(<ob>xxxxxxxxx|obxxxxxxxxx) and that solved the problem.