Voxalot / SIP Broker Support Forums - View Single Post

ptruman · 01-28-2009, 05:02 PM

No - but they've answered my query and explained something plausible :

Without talking to the tech team I expect that this is a voxalot/DNS issue -
My reasoning is because I have seen this before where a device was sending
SIP signals to an IP address that it had resolved during a call and not that
which the call had started on. Asterisk suffers from this.

We have multiple servers for redundancy, on multiple IP addresses.
Your device, or Voxalot resolved our address as 1.1.1.1 and places a call -
during the call all is well. However should what ever voxalot is running do
a DNS lookup and resolve 2.2.2.2 for us it 'may' send any SIP messages to
2.2.2.2 which is not where your call is, so your call stays open as it
hasn't been closed.

I'll take this up with the tech team and ask for advice.

For Asterisk the solution is to configure the outbound proxy to be one
specially for this issue as it has only one IP address !
'single-01.proxy.voip.co.uk'

More information is available here:
products:asterisk [wiki.VoIP.co.uk]

So I could change the VSP details in Voxalot, but this removes resilience.

Anything you can do your end?

[EDIT]

This has happened again - a 1 min 6 second call stayed open for 4 hours 19 mins and cost me £20 UKP. I've now set my proxy to the one they suggest, and see if this alleviates the problem.

01-28-2009, 05:02 PM	#3
ptruman Member Join Date: Sep 2006 Posts: 94 Thanks: 1 Thanked 8 Times in 8 Posts	No - but they've answered my query and explained something plausible : Without talking to the tech team I expect that this is a voxalot/DNS issue - My reasoning is because I have seen this before where a device was sending SIP signals to an IP address that it had resolved during a call and not that which the call had started on. Asterisk suffers from this. We have multiple servers for redundancy, on multiple IP addresses. Your device, or Voxalot resolved our address as 1.1.1.1 and places a call - during the call all is well. However should what ever voxalot is running do a DNS lookup and resolve 2.2.2.2 for us it 'may' send any SIP messages to 2.2.2.2 which is not where your call is, so your call stays open as it hasn't been closed. I'll take this up with the tech team and ask for advice. For Asterisk the solution is to configure the outbound proxy to be one specially for this issue as it has only one IP address ! 'single-01.proxy.voip.co.uk' More information is available here: products:asterisk [wiki.VoIP.co.uk] So I could change the VSP details in Voxalot, but this removes resilience. Anything you can do your end? [EDIT] This has happened again - a 1 min 6 second call stayed open for 4 hours 19 mins and cost me £20 UKP. I've now set my proxy to the one they suggest, and see if this alleviates the problem. Last edited by ptruman; 01-29-2009 at 10:18 AM.