Voxalot / SIP Broker Support Forums - View Single Post

kurun · 01-06-2008, 06:07 PM

I did set up an HT-488 a few months ago, and it has been working reliably.
I have a Voxalot account on the FXS port using Poivy as an outgoing PSTN provider.
The FXO SIP account is using another VSP.
I do not have access to the settings as this ATA is currently 5000 miles away.

Some suggestions :
1) Update to the latest firmware (The FXO port did not work properly with earlier firmware)
2) Use the default SIP ports 5060 and 5062
3) Use different RTP ports (Eg 5004, 5006) for the FXS and FXO ports
4) Use a STUN server (Eg. stun.voxalot.com.au:3478)
5) If you are behind a router, it might help to forward the SIP ports (5060-5063) and the RTP ports (5004-5007) in particular.

You might want to try setting up the FXS port by itself first (with the FXO port disabled) until you trace the cause of the 21 second call-drop problem.

01-06-2008, 06:07 PM	#2
kurun Join Date: Sep 2006 Location: Toronto, Canada Posts: 568 Thanks: 70 Thanked 147 Times in 115 Posts	I did set up an HT-488 a few months ago, and it has been working reliably. I have a Voxalot account on the FXS port using Poivy as an outgoing PSTN provider. The FXO SIP account is using another VSP. I do not have access to the settings as this ATA is currently 5000 miles away. Some suggestions : 1) Update to the latest firmware (The FXO port did not work properly with earlier firmware) 2) Use the default SIP ports 5060 and 5062 3) Use different RTP ports (Eg 5004, 5006) for the FXS and FXO ports 4) Use a STUN server (Eg. stun.voxalot.com.au:3478) 5) If you are behind a router, it might help to forward the SIP ports (5060-5063) and the RTP ports (5004-5007) in particular. You might want to try setting up the FXS port by itself first (with the FXO port disabled) until you trace the cause of the 21 second call-drop problem.