GV missed calls - when answered by home machine?
offroad:
Auto Provisioning seems to have been the issue.
I reset the OBi to factory config, did initial setup of SP1-GV and SP2-CallCentric using OBiTalk then disabled Auto Provisioning.
SP2-CC now stays registered, and the only values I changed directly on the OBi was to set ProxyServerPort and OutboundProxyPort to 5080. RegistrarServer was left blank by OBiTalk during setup of SP2-CC so I left it alone.
I'll check it again tomorrow but all seems stable with Verizon 4G and I'll try it with the WISP Ethernet as well.
Thanks for the help, only need to get 911 working and digit maps right to be complete for my purposes.
offroad:
This morning OBiTalk shows: CallCentric Account Registered (server=204.11.192.22:5080; expire in 56s)
So it appears to be working fine now, also just tested with my WISP Ethernet and it shows the same.
Just curious, if CC accounts should be talking over port 5080, why is ProxyServerPort and OutboundProxyPort set by OBiTalk to 5060?
Stewart:
Quote from: offroad on January 19, 2012, 05:16:28 am
Just curious, if CC accounts should be talking over port 5080, why is ProxyServerPort and OutboundProxyPort set by OBiTalk to 5060?
Because the port number should be set by CC's DNS SRV record. Hard coding the port number (as I requested) is not as robust -- if CC needed to change it for some reason, your system would stop working.
But hey, not only are VZW's DNS servers failing to look up SRV records (either maliciously or by incompetence, though you could never prove the former), but they have also hijacked the DNS ports, so you can't work around the problem by using third-party DNS servers. Short of connecting via a VPN, explicitly specifying port 5080 seemed like the only solution.
RonR:
Quote from: RonR on January 14, 2012, 09:34:21 pm
The number you PM'd me rings endlessly using Google Voice, IdeaSIP, Ribbit, Alcazar Networks, and SIP Broker. I can't see how this can be an OBi problem.
It turns out there is a problem in the OBi with calls using 'Early Media'.
Calls initiated through the OBi PHONE Port using a service provider that supports 'Early Media', such as IdeaSIP, Alcazar Networks, or SIP Broker work just fine. The same calls initiated from another OBi or OBiON App via the OBiTALK Service do not. The one exception to this I've found is IdeaSIP, which does work properly with the OBiTALK Service involved (somehow I missed this about IdeaSIP in my earlier testing).
I've asked Obihai to investigate this problem, but have not yet received a response.
offroad:
If this is fixed by Obihai, would that also fix the problem I had with that number dialed through GV?
If not is this because GV doesn't support early media at all?
Navigation
[0] Message Index
[#] Next page
[*] Previous page