Can I bind multiple SIP Gateways to the same IP Interface?
Posted by Elena Brambilla, Last modified by Daniel Lizaola on 12 December 2017 05:13 PM
|
|
In some cases you may want to create multiple SIP gateways to subscribe to multiple SIP Telephony Services at the same time, or to seperate LAN SIP calls from Global/Internet SIP calls. In order to bind multiple SIP gateways to the same IP interface the signaling port of the different gateways has to be different. Use the "call-signaling-port" command for this purpose 172.16.40.125(cfg)#gateway sip SIP1 172.16.40.125(gw-sip)[SIP1]#bind interface eth0 172.16.40.125(gw-sip)[SIP1]#no shutdown 172.16.40.125(cfg)#gateway sip SIP2 172.16.40.125(gw-sip)[SIP2]#bind interface eth0 172.16.40.125(gw-sip)[SIP2]#call-signaling-port 5062 172.16.40.125(gw-sip)[SIP2]#no shutdown If you do not change the signalling port you will get the following error message when you try to bind or activate the second gateway: % ANOTHER GATEWAY IS ALREADY BOUND TO THE SAME PORT Note: The ports are allocated even if a gateway is in shutdown. You must still use different signalling ports on each gateway! Note: The signalling port numbers must be even values e.g. 5060, 5062, 5064 etc. As an alternative, you may want to create different SIP "services" within one gateway - this allows to have mulitple virtual gateways on the same interface, using all the same call signaling port. | |
|
Comments (0)