Voxalot / SIP Broker Support Forums - View Single Post

kurun · 04-02-2011, 04:10 PM

I have seen a similar problem when the calling party was using an SPA3102, but I could not debug the issue, as the PA3102 was not my device.

The workaround solution was to introduce an intermediate SIP number between the two Voxalot end points. This still allows you to call directly between the two Voxalot registered ATAs, with 2 way conversation.

You can try the following :
1) Set up a SIP account with the intermediary provider (Eg Voiptalk.org, or Callcentric.com)
2) Register the intermediate provider in the receiving side Voxalot account (requires a Premium subscription) or use the intermediate account forwarded to the Voxalot account (supported by Callcentric)
3) Call the intermediate account via Sipbroker or set up a dial plan entry to redirect a short number of your choice to the intermediate SIP account.

This approach may also be a work around for your problem.

04-02-2011, 04:10 PM	#3
kurun Join Date: Sep 2006 Location: Toronto, Canada Posts: 568 Thanks: 70 Thanked 147 Times in 115 Posts	I have seen a similar problem when the calling party was using an SPA3102, but I could not debug the issue, as the PA3102 was not my device. The workaround solution was to introduce an intermediate SIP number between the two Voxalot end points. This still allows you to call directly between the two Voxalot registered ATAs, with 2 way conversation. You can try the following : 1) Set up a SIP account with the intermediary provider (Eg Voiptalk.org, or Callcentric.com) 2) Register the intermediate provider in the receiving side Voxalot account (requires a Premium subscription) or use the intermediate account forwarded to the Voxalot account (supported by Callcentric) 3) Call the intermediate account via Sipbroker or set up a dial plan entry to redirect a short number of your choice to the intermediate SIP account. This approach may also be a work around for your problem.