Obi202 Direct IP (Peer to Peer) Dialing
RonR:
Quote from: Ostracus on April 18, 2012, 08:28:46 am
Has anyone checked to see if this is still true for the Obi202?
Why wouldn't it be?
Ostracus:
Opportunity to clean up their code for one. Ability to use all four for GV* and still use SIP URLs, as corner case as that may sound.
*Maybe in the future Skype.
N2VWZ:
Quote from: RonR on April 18, 2012, 09:15:57 am
Quote from: N2VWZ on April 18, 2012, 08:13:49 am
Ron, I've tried configuring my Obi100 exactly as you have, without success. I believe that the reason for failure is because the Obi100 is behind the NAT and has no knowledge of the WAN IP address. The SPA2000 works because the EXT IP parameter programmed with the WAN IP address. The OBi100 has no EXT IP parameter for setting the WAN IP.
Is your Obi equipment connected directly to the WAN or is it behind a NAT?
My OBi's are behind a NAT router.
Do you have SIP (5060-5061) and RTP (16600-16998) ports forwarded in your router to the OBi's LAN IP address?
SIP is forwarded, but RTP is not. I didn't need to forward RTP with the Sipura SPA-2000.
If you are behind a router, how does the Obi correcty configure the SIP packets without knowledge of the WAN IP address?
RonR:
Quote from: N2VWZ on April 18, 2012, 12:02:37 pm
SIP is forwarded, but RTP is not. I didn't need to forward RPT with the Sipura SPA-2000.
If you are behind a router, how does the Obi correcty configure the SIP packets without knowledge of the WAN IP address?
Even though it's not always necessary, I always make a habit of forwarding SIP and RTP ports to the ATA just to preclude future problems.
The OBi is able to determine your public IP address using a STUN server. I use PAP2's also, along with a STUN server, and have never used the EXT IP setting. Unless you have a static IP address, EXT IP will be problematic, whereas a STUN server will always obtain your correct public IP address.
Felix:
Quote from: N2VWZ on April 18, 2012, 08:13:49 am
The SPA2000 works because the EXT IP parameter programmed with the WAN IP address. The OBi100 has no EXT IP parameter for setting the WAN IP.
EXT IP in SPA devices serve very narrow purpose, according to Cisco's administration guide:
If the ITSP network does not provide a Session Border Controller functionality, and if other requirements are met, you can configure NAT mapping to ensure interoperability with the ITSP.
Requirements:
You must have an external (public) IP address that is static.The NAT mechanism used in the router must be symmetric. See “Determining the Router’s NAT Mechanism”The LAN switch must be configured to enable Spanning Tree Protocol and Port Fast on the ports to which the SPA devices are connected.Per docs, if you are using EXT IP, you should disable STUN and enable VIA, Which is completely counter-intuitive given that STUN fields are in the middle between VIA and EXT IP.
So, I doubt that EXT IP setting has any effect on your SPA2000. I had it myself, assuming - just like you - that it is needed for direct dialing. Then I figured out how to do it, and then removed EXT IP value (or rather, my dynamic IP changed, so the value was obviously incorrect - so I cleared it) and it continued working.
Navigation
[0] Message Index
[#] Next page
[*] Previous page