Dialing out Using Skype with IPO 1

[deltaserver403]

Dear All.

There is DSL conection from service provider with DSL modem for internet connection, this internet conection is only used for making voice calls using Skype service,

is there any possibilty to use IPO to conect directly to DSL Router which has got 2 LAN ports & route all international calls to Skype without using any FXS gateways between DSL & IPO.
Is anybody tested this or is this possible.

Looking forward
Thanks
DS

 

[MrIPO]

With IPO release 4.0 this may be possible using the SIP trunking interface for the IPO to place a SIP call directly onto Skype gateways. However this will require a license and possible STUN setup as I am guessing you would be using NAT.

I am currently testing V.4.0 in regard to SIP trunking, I can provide a few more details once this is performed as to the exact implementation of SIP on the IPO, and how well the interface has been designed.

http://www.iporesource.com

"Launching late 2006

 

[superikey]

Can you explain exactly what STUN is? Can it be used with H323?

Isaac Braca
CTO / ICCS & Co., LLC.
Email: braca@iccsllc.com

ICCS, Your Premier IT Partner, is a NYC Based Avaya Business Partner and IT Consulting Firm.

 

[MrIPO]

STUN (Simple Traversal of User Datagram Protocol (UDP) Through Network Address Translators (NATs)) is a network protocol allowing a client behind a NAT (or multiple NATs) to find out its public address, the type of NAT it is behind and the internet side port associated by the NAT with a particular local port. This information is used to set up UDP communication between two hosts that are both behind NAT routers.

STUN is a client-server protocol. A VoIP phone or software package such as the IP Office include a STUN client, which will send a request to a STUN server. The server then reports back to the STUN client what the public IP address of the NAT router is, and what port was opened by the NAT to allow incoming traffic back in to the network.

The response also allows the STUN client to determine what type of NAT is in use, as different types of NATs handle incoming UDP packets differently. It will work with three of four main types: Full Cone, Restricted Cone, and Port Restricted Cone. (In the case of Restricted Cone or Port Restricted Cone NATs, the client must send out a packet to the endpoint before the NAT will allow packets from the endpoint through to the client.) STUN will not work with Symmetric NAT (also known as bi-directional NAT) which is often found in the networks of large companies. With Symmetric NAT, the IP address of the STUN server is different than that of the endpoint, and therefore the NAT mapping the STUN server sees is different than the mapping that the endpoint would use to send packets through to the client. For details on the different types of NAT, see network address translation.

Once a client has discovered its external addresses, it can relate it to its peers. If the NATs are full cone then either side can initiate communication. If they are restricted cone or restricted port cone both sides must start transmitting together.

Note that using the techniques described in the STUN RFC does not necessarily require using the STUN protocol; they can be used in the design of any UDP protocol.

Protocols like SIP use UDP packets for the transfer of sound/video/text signaling traffic over the Internet. Unfortunately as both endpoints are often behind NAT, a connection cannot be set up in the traditional way. This is where STUN is useful.

An example of a well-known VoIP application that uses STUN is Google Talk, which interoperates with STUN servers situated in Google's datacenters.

The STUN server is contacted on UDP port 3478, however the server will hint clients to perform tests on alternate IP and port number too (STUN servers have two IP addresses). The RFC states that this port and IP are arbitrary.

The RFC for STUN is RFC3489

I understand STUN can be used with H323 but I have not as yet tested.

http://www.iporesource.com

"Launching late 2006

 

[MrIPO]

The reply above was taken from

http://en.wikipedia.org/wiki/STUN

With some additional notes I added.

I understand the statement above - "STUN will not work with Symmetric NAT (also known as bi-directional NAT) which is often found in the networks of large companies" is incorrect and that STUN will work with Symmetric NAT

http://www.iporesource.com

"Launching late 2006

 

[superikey]

How can I use STUN to setup current IP Office releases wo allow IP Phones to connect form the outside without using VPN's?

Isaac Braca
CTO / ICCS & Co., LLC.
Email: braca@iccsllc.com

ICCS, Your Premier IT Partner, is a NYC Based Avaya Business Partner and IT Consulting Firm.

 

[MrIPO]

The initiating device requires a STUN client installed on the device. Releases prior to 4.0 do not include STUN Client hence this is not possible.

Even on ACM the 46XX firmware does not include STUN support to the best of my knowledge.

It may be possible with a STUN Server locally but until I test I cannot be 100% sure.

http://www.iporesource.com

"Launching late 2006

 

[blantonlewis]

Skype uses a proprietary protocol - neither SIP or H.323. If you want to use a multi-port device, for now you have to use a computer-based device with analog ports on the IPO. Here's one with four ports:

http://www.vosky.com/product.php?pid=321

The Skype protocol takes quite a bit of processing power b/c it's encrypted. We're about to set this system up.