On 1/26/2010 8:57 PM, M. Ranganathan wrote:
On Tue, Jan 26, 2010 at 9:16 PM, Tony Graziano
<[email protected]> wrote:
  
I don't know what "206 no peers available" means from sipxbridge.
    
Well, there are two problems at hand here. The 481 error from
sipxbridge on the re-INVITE -- I believe this to be a sipxbridge bug
that I have fixed already in 4.1. You can give that a try.
However, I am curious about why verizon  issending a re-INVITE as soon
as the call is. Perhaps it does not like the fact that you are using
10.87.20.5 address in your call setup.



Regards,


Ranga.

  
We have a private connection with Verizon, and they specifically do route to our private IP. All our communication with them is on private IPs over a local DS3 loop. I"m assuming that is what you are referring to with respect to 10.87.20.5.
This server is very much in production, so I can't really try 4.1 out on it. If there is patch than can be easily backed out, I can try that.
I had to provide 80 or so wireshark captures to verizon and I don't remember anything out of the ordinary in those. Here is a voip analysis of one of them.


_______________________________________________
sipx-users mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
sipXecs IP PBX -- http://www.sipfoundry.org/

Reply via email to