There is only one thing left: keep-alive. To keep the NAT pinhole open
you need periodic traffic from/to the client. Either enable NAT keep
alive on the SIP client, or on Kamailio (nathelper module and save() the
contacts just for the purpose of nathelper keep-alive) or on Avaya (e.g.
if Avaya
Hello,
for dialogs (like subscriptions or invites), you have to use record
routing (see rr module) -- so for initial subscribe/invite you have to
add record-route header in kamailio, then do loose routing for requests
within the dialog (like notify) -- the default config file coming with
kama
Hi
I'm trying to configure kamailio version 3.3.0 to be a Session Border
Controller which only purpose is to handle far-end-nat.
On the far end site I have a SIP client with IP '192.168.1.2' which is
NAT'ed to IP 'zz.zz.85.230'. The SIP ALG is disabled on the NAT
firewall. The SIP client is commu
