GV working fine; trouble adding Sipgate
RonR:
SnerdlyBosco,
FWIW, I just performed the exact steps I outlined in the previous post.
The OBi immediately registered with Sipgate and I could successfully make and receive calls.
SnerdlyBosco:
RonR
Ha! I was just coming back to tell you I'd taken some of your advice from elsewhere in the forum -- which is exactly what you've just posted here! Thanks for both...
Progress!
With ObiTalk disabled and the Obi provisioning disabled, Sipgate on SP1 registers fine.
I am able to place calls AND receive calls.
BUT, there is one-way audio on both placed and received calls. In neither case can the Obi-wired phone "hear." In both cases, the distant phone can hear.
Something in the router?
Thanks for getting me this far...
RonR:
Quote from: SnerdlyBosco on January 18, 2012, 11:51:15 am
Ha! I was just coming back to tell you I'd taken some of your advice from elsewhere in the forum -- which is exactly what you've just posted here! Thanks for both...
Progress!
With ObiTalk disabled and the Obi provisioning disabled, Sipgate on SP1 registers fine.
I am able to place calls AND receive calls.
I was confident you were getting all tangled up between the OBiTALK Web Portal, the OBiTALK Wizrd, and the OBi directly.
Do yourself a big favor and get familiar with configuring the OBi directly on your own. You'll end up thanking yourself in the end.
Quote from: SnerdlyBosco on January 18, 2012, 11:51:15 am
BUT, there is one-way audio on both placed and received calls. In neither case can the Obi-wired phone "hear." In both cases, the distant phone can hear.
Something in the router?
That's most likely a router issue.
First call the echo test at **9 222 222 222 and see how that goes (it's usually more forgiving).
Then connect the OBi directly to your modem and see if bypassing the router solves the problem.
Stewart:
I suspect that the Embarq modem is configured as a router (since you were able to run the OBi with GV, when connected directly to the modem). You can confirm that by seeing whether the Linksys gets a public IP address on its WAN interface. If not, the modem is acting as a router and you have two NATs cascaded.
I don't know whether Sipgate requires NAT mapping -- try turning off STUNEnable. If that doesn't work, turn it back on and test with OBi direct to modem. If that also fails, you might put the modem in bridge mode and set up PPPoE on the Linksys. If the direct modem connection works, try forwarding the RTP port range across the Linksys.
SnerdlyBosco:
Tried disabling STUN. One-way audio persists, with and without.
Connected Obi directly to modem.
Outbound call: SUCCESS! Both parties could hear.
Inbound call: FAILURE. Call placed with Verizon got "unable to complete your call" message. Call placed with Google Voice got ringback tones for caller, but phone connected to Obi did not ring.
I suspect that the Embarq modem is configured as a router (since you were able to run the OBi with GV, when connected directly to the modem). You can confirm that by seeing whether the Linksys gets a public IP address on its WAN interface. If not, the modem is acting as a router and you have two NATs cascaded.
I don't know how to see whether Linksys gets a public IP address on its WAN interface.
Navigation
[0] Message Index
[#] Next page
[*] Previous page