View Single Post
Unread 03-03-2007, 02:26 PM   #9
v164
Member
 
Join Date: Mar 2006
Posts: 96
Thanks: 8
Thanked 26 Times in 19 Posts
v164 is a jewel in the roughv164 is a jewel in the rough
Default lr=on problem workaround

Quote:
Originally Posted by v164 View Post
I'm hoping that this may be a workaround to the "lr=on" problem that prevents me from receiving calls from Voxalot / SipBroker, as described here:
http://forum.voxalot.com/showthread.php?t=53&page=2

At the moment, the only way I've been able to get an incoming call to work from Voxalot / SipBroker is by registering my ATA as a "provider" in my Voxalot setup (entering my ATA's IP address, and a dummy username and password).
http://www.voxalot.com/action/providerList
I've confirmed that this workaround works.

At e164.org, my PSTN numbers are mapped to my VoXaLot SIP URI

6xxxxx@au.voxalot.com

and in Voxalot, I've got all calls forwarded, via my "provider" to 050xxxxxxxx. My "provider", of course, is just my ATA (ie in the provider details page, I've put my public IP address in as the host, and entered a dummy username and password (my ATA doesn't ask for them).

The calls get through OK, but the media stream is being proxied by Voxalot. Similar to web callback, it looks like Voxalot is implementing call forwarding via providers as a "back to back user agent" arrangement.

On the plus side, that gives me automatic transcoding if necessary (my ATA only does G711 u-law), however on the minus side, it causes the voice traffic to transit voxalot which may increase latency.
v164 is offline   Reply With Quote