Obitalk & Vonage Simultaneously?
SteveInWA:
OBi devices act as Google Chat clients over XMPP, not SIP. Thus, any settings related to SIP are not applicable, including port forwarding in the 506x range.
https://support.google.com/a/answer/1279090?hl=en
Does the OBi work correctly (two-way audio) when the Vonage ATA is unplugged from power, but fails when the Vonage ATA is powered on and connected? Or, does the OBi never work correctly, or what, exactly? You're not going about this in a systematic manner.
LTN1:
Quote from: TerryaG on April 22, 2016, 05:23:44 pm
My question to LTN is, are you using port forwarding for your Obi or are you using DMZ?
I am not using port forwarding or the DMZ for the OBi. I am using port forwarding only for a PBX system connected to the SBG6580.
Besides that, my OBi is pretty much plug and play with both the SGB6580 and Comcast.
LTN1:
Quote from: SteveInWA on April 22, 2016, 04:58:48 pm
Quote from: LTN1 on April 22, 2016, 04:37:32 pm
I have the same SBG6580 and my SIP ALG is enabled--as a matter of fact, under the NAT ALG Status of Advanced Options, everything is enabled. Mine works fine with the OBi202. I also have Comcast.
Maybe more experienced contributors can provide other suggestions.
BTW...a pet peeve of mine is when VoIP services like the OBi, Ooma, Vonage, etc. is called a landline. Landline should be something like POTS. The services that use the high speed internet for phone communication are VoIP lines or SIP lines.
I agree that the term "landline" is outdated, as one would think of wires on telephone poles over land. However, it's useful as a way to distinguish the underlying carrier being used: VoIP numbers are generally treated as wireline telephone numbers from a Local Exchange Carrier standpoint, vs. mobile numbers, because the numbers usually belong to wireline LECs. The FCC has some specific terminology used in its regulations, when referencing VoIP. The FCC calls VoIP service providers "interconnected voice over Internet Protocol (VoIP) providers".
Quote
Interconnected VoIP service enables users, over their broadband connections, to receive
calls that originate on the public switched telephone network (PSTN) and to terminate calls to the
PSTN.31 In order to have this capability, an interconnected VoIP service must offer consumers NANP
telephone numbers.32 Interconnected VoIP providers generally obtain NANP telephone numbers for their
customers by partnering with a local exchange carrier (LEC) through a commercial arrangement rather
than obtaining them directly from the numbering administrator, which provides numbers only to entities
that are licensed or certificated as carriers under the Act."
Whereas most VoIP service providers partner with wireline LECs, to obtain NANP telephone numbers, these numbers are usually considered wireline (landline) numbers. It gets messy when a mobile carrier's number is ported into a wireline LEC, to use with a VoIP ITSP.
If you have insomnia, you can read this document to see how the FCC treats VoIP numbers with regard to Local Number Portability: https://apps.fcc.gov/edocs_public/attachmatch/FCC-07-188A1.pdf
Thanks for the PDF link Steve. From my first perusal of the 2007 FCC ruling, I see why they were using the term interconnected VoIP Providers--in order to have authority and jurisdiction to regulate things like LNP and 911 requirements--basically summed up in paragraph 21.
While there may be different classifications of VoIP, I think it should be differentiated from the traditional POTS landline. I'm OK with using the terms defined by the FCC--perhaps with the acronym IVoIP?
TerryaG:
Sorry for the late response guys, been very busy. I appreciate the help. I reenabled the SIP stuff and removed the port forwarding, per LTN1's suggestion, and everything works fine, both the Obi box AND Vonage! Thanks again for the help, I appreciate it!
Terry
Navigation
[0] Message Index
[*] Previous page