NAT Registrations | Diversions RE-write


#1

I have gateways that are behind NAT and would like them to register to Yeti-Switch for both origination and termination. Does Yeti work well with gateways behind NAT? I have changed registrations_enable=yes in sems.conf but I still get error “405 Method Not Allowed”

I would like to re-write the “diversion in” number to " destination prefix out "

Lastly I see documentation on Version 1.8. Is it ready for upgrade? Where can I get the changelog ?


#2

Yeti doesn’t process incoming registrations. Only outgoing registrations is supported(when Yeti sends REGISTER to external server)

I would like to re-write the “diversion in” number to " destination prefix out "

This is not supported yet. see Creating a new call diversion header
It is possible to add Diversion header with constant value, but it is not possible to build it from number in other field.

Lastly I see documentation on Version 1.8. Is it ready for upgrade? Where can I get the changelog ?

We are preparing documentation, but 1.8 still not released. We will announce 1.8 release on this forum.

PS: Could you create different topics for not related questions.