PBX setup with Obi202 moving from expired Obiplus subscription
ppppplus:
Hello.
I had tried out the Obiplus PBX setup with no major issue. But since last month, I had discovered that I am no longer eligible for the Obiplus Basic service, which was perfect for my modest 4-line PBX setup. I was advised to try FreePBX and while I learned quite a bit in the process, I'm still clearly not getting it because I would experience things like choppy sound, especially on the other end of the line, which had never been an issue with Obiplus/Obi202. I've read that this is typical of bandwidth restrictions or high ping times, but for some reason, the Obiplus setup worked with the same bandwidth restrictions and delivered audible sound.
So I guess I'm wondering if anyone might be able to help with replicating my experience with Obiplus. I had requested assistance from Obihai and am currently awaiting their response, but I feel that from what I've read here, that there are many experts in the field of SIP, RTP, etc. I still have the 2 Cisco SPA504G phones that I had bought for use with Obiplus and am currently using those with my FreePBX server. But again, even if the FreePBX server is being run on a robust Intel Core i5 2450m cpu and 4GB DDR3 RAM, the Obi202 when used as the Obiplus basic gateway, is still killing it. I'm going to go out on a limb and say that this is not a hardware issue since I doubt that the cpu on the Obi202 wouldn't be capable of being used in a full blown current pc as the Core i5 is used.
I still have the Obi202 and Cisco SPA504G configuration files from the previous setup and I imagine that it just requires a little finagling to get the four lines going again.
Thank you!
ppppplus:
based on this fantastic thread, https://www.obitalk.com/forum/index.php?topic=8857.0 , I attempted to set something up similar but am having some massive issues with it. As I only have SP4 unconfigured, I went ahead and adapted a mixture of the instructions on the websites below to use SP4 as my proxy rather than SP2:
http://blog.obihai.com/2012/08/use-your-obi202-as-google-voice-gateway.html
and
http://voxilla.com/2011/02/15/how-to-obify-your-ip-phone-no-asterisk-involved/
but am finding my Cisco SPA504G phone not being registered.
I tried this with the auto-provisioning enabled and disabled per the voxilla article and for voice services >> X_InboundCallRoute, I have "{ph1,SP4(1001@192.168.2.2)}" so that it rings on both one of my analogue phone and my ip phone.
The blog advises to follow this syntax: SP1/X_InboundCallRoute = {SP2(1001@local_client)}
but I'm wondering if "local_client" here is meant as a placeholder or if "local_client" needs to be in there verbatim. Otherwise I followed the instructions to the letter and still can't seem to get my Obi202 to chat with my SPA504G as it once did with Obiplus. Thanks.
azrobert:
{SP2(1001@local_client)} is verbatim.
You should make the 1001 match the Auth User Name of the SPA504G.
You normally can use any string, but I had a device that wouldn't work unless it matched.
Did you check the System Status to see if the phone is registered?
You can register multiple phones to a single Proxy.
Outbound calls will work for all, but only the last to register will receive inbound.
azrobert:
Quote from: azrobert on July 02, 2016, 01:57:52 pm
only the last to register will receive inbound.
This only applies when using "local_client". You should be able to route inbound calls to multiple phones via IP address.
ppppplus:
thank you. That's how it's currently setup with the auth username as 1001 and password set temporarily to "password". That's great news that multiple IP phones can get extensions this way. Not so great news that only one ip phone can receive incoming calls though, unless I misunderstood.
Is there any more information I can provide to get my spa phone registered? I can supply the entire spa504g config.xml if need be. Cheers.
Navigation
[0] Message Index
[#] Next page