Re: [SR-Users] carrierroute and failure route

Hi, On Sat, Aug 5, 2017 at 7:00 PM, Yu Boot wrote: > Gotcha! I've added fix_nated_contact() to [NATDETECT] route and now all > messages UNTIL reinvite occurs are with correct NATed IP in "Contact" field. while fix_nated_contact() may work in your scenario, it is generally a

Re: [SR-Users] carrierroute and failure route

Gotcha! I've added fix_nated_contact() to [NATDETECT] route and now all messages UNTIL reinvite occurs are with correct NATed IP in "Contact" field. Now I'm trying to make it work similiar way with reinvites. And I still don't understand, is default Kami config is somewhat broken or what.

Re: [SR-Users] carrierroute and failure route

Hi, On Thu, Aug 3, 2017 at 12:48 PM, Yu Boot wrote: > First one works OK, but if second route triggers, the following disaster > occurs (tshark dump) https://pastebin.com/00Ayty36 it's not really a disaster. The Mediant2000 sends out a reINVITE after the call was established.

Re: [SR-Users] carrierroute and failure route

Hello 200 Ok couldnt reach somewhere. it is hard to understand what is going. YOu can use sngrep for tshark to understand better. Maybe there is nat issue https://github.com/irontec/sngrep/wiki/Installing-Binaries#centos--fedora--rhel -- View this message in context: