- Sun 8th Mar 2015, 10:43
#1422
FULL_POST
Best answer
Hi
New user and I am in the process for setting up my Obi200. I have update manually to the latest firmware.
I have used the latest XML file to set up the UK parameters and added 2 VOIP providers (voipfone as SP1 and sipgate as SP2). Obi shows both as registered.
However when I dial **210000 on my handset, instead of getting Sipgate , all I get is a cannot be connect message. The call history on the Obi says
"10:34:32 From PH1 To SP1(0000)
10:34:33 Call Connected
10:34:38 Call Ended"
So it is not connecting via SP2 and also losing the leading 1 in the sipgate number.
Any ideas as the dial plans/routes have not been changed by myself but are the ones in the XML configuration file.
New user and I am in the process for setting up my Obi200. I have update manually to the latest firmware.
I have used the latest XML file to set up the UK parameters and added 2 VOIP providers (voipfone as SP1 and sipgate as SP2). Obi shows both as registered.
However when I dial **210000 on my handset, instead of getting Sipgate , all I get is a cannot be connect message. The call history on the Obi says
"10:34:32 From PH1 To SP1(0000)
10:34:33 Call Connected
10:34:38 Call Ended"
So it is not connecting via SP2 and also losing the leading 1 in the sipgate number.
Any ideas as the dial plans/routes have not been changed by myself but are the ones in the XML configuration file.
Chalk one up for my not thinking things through. When testing, I was just plugging the lead from the master BT socket into the Obi and forgot that there is a call blocker machine linked to the DECT base station. Hence it was eating the **21 and passing the rest to the Obi.
Whoops.
Whoops.
FULL_POST
How did this post make you feel?