mFlowKey=872 replied: 502 Bad Gateway

[Trimline]

I signed up with a new 800 provider called tollfreesipgateay located here: http://tollfreesipgateway.com/Home.html

After receiving my confirmation e-mail (IP address is verified), I simply replaced my current provider from sip.denetron.com to IP:208.92.48.238. When dialing a toll free number, I receive:

Call to 1877888XXXX@(Ln.10004@TollFree800) has failed. [ V4 208.92.48.238:5060 UDP target domain=unspecified mFlowKey=872 ] replied: 502 Bad Gateway; from IP:208.92.48.238:5060
Attempt to reach <sip:[email protected]> failed. Reason: Server Failure

Should I swap back in sip.denetron.com, or any number of other 800 providers, the calls will complete.

Does anyone know what would cause this error? My installation does have my hard coded IP address, and my other providers work flawlessly.

 

[leejor]

Let's see if i get this right... you just changed the destination to na IP from a URL (different provider)?

Call to 1877888XXXX@(Ln.10004@TollFree800) has failed. [ V4 208.92.48.238:5060 UDP target domain=unspecified mFlowKey=872 ] replied: 502 Bad Gateway; from IP:208.92.48.238:5060

So where is the TollFree800 coming from if the call is sent to an IP?

502 Bad Gateway; from IP:208.92.48.238:5060

This part seems to indicate that a message is coming back from that IP, meaning that you did reach someone. Have you spoken to them? Perhaps you have been given an incorrect IP or port.

 

[Trimline]

Let's see if i get this right... you just changed the destination to na IP from a URL (different provider)?

Yes, I simply just replace either the host name or address, and update the VoIP provider. Traffic flows fine with tf.callwithus.com or sip.denetron.com.

So where is the TollFree800 coming from if the call is sent to an IP?

All of the above are simple VoIP providers, just like Callcentric or VoIP.ms. The only difference is that most VoIP tollfree providers do not require a user/password for access.

 

[Trimline]

The solution here was to hard code 208.92.48.238 in my host file as sip.tollfreegateway.com. After updating my VoIP provider with sip.tollfreegateway.com rather than the IP address, the calls are now being completed successfully.

I would suspect that this is a bug in some ways as you should be able to use IP addresses for SIP server IP address.

 

[leejor]

When I look up that URL, it translates to 76.10.223.207 , not the IP you were using.

 

[Trimline]

When I look up that URL, it translates to 76.10.223.207 , not the IP you were using.

If you go to your C:\Windows\System32\drivers\etc\ and edit your HOST file as and administrator and add:
208.92.48.238 sip.tollfreegateway.com
and then save, when you ping it will return the ip address as entered.

That is what I had to perform to get around the error.