Some customers asking us about the possibility to route calls to the vendor via connection in case if vendor's GW has a dynamic IP address or behind the NAT.


  • Create a domain name for vendor's GW.
  • Create connection with the environment IP address (see the below scenario):

You have to create two accounts(for example 666001 and 666003) and special connection(with IP address of environment, name - "local connection").

First account 666001 will receive calls and route them to our "local connection".

In the connection properties you have to specify CLD TR. rule:


Result will be like this:

[ssp-root@demo-slave ~]$ python /home/ssp/sippy/ 's/^/666003;cld=/' 380663833754

and IP of your environment. Add second account 666003 to your environment and you will use it for GW registration(GW will be the same as UA, customer should register 666003 account on the gateway of his vendor).

So as result connection will send calls to the account 666003.

See screenshot of your connection:

With this configuration Sippy will send the following To: header

To: <sip:666003;cld=380663833754@>

Removal of "666003;cld" is possible with the assistance of Support team.