To learn more about the various methods of controlling transport protocols for SIP signaling and how these work together, refer to Controlling SBC Core Transport Protocols for SIP Signaling.
In this section:
Overview
Use this object to configure SIP signaling ports for a specified zone. For additional routing details, refer to Routing Mechanisms page.
A SIP Signaling Port is a logical address permanently bound to a specific zone and is used to send and receive SIP call signaling packets. A SIP Signaling Port is capable of multiple transports such as UDP, SCTP, TCP and TLS/TCP.
SBC Core supports up to 16 SIP Signaling Ports per zone. These SIP Signaling Ports can use the same IP address, but each must have its own unique UDP/TCP port. In the example below, three SIP Signaling Ports are created using the same IP address but each with a unique UPD port.
- SIP Signaling Port 1: 100.110.120.130 port 5060
- SIP Signaling Port 2: 100.110.120.130 port 5070
- SIP Signaling Port 3: 100.110.120.130 port 5080
A SIP Signaling Port can contain an IPv4 address, an IPv6 address or both. However, all SIP Signaling Ports within a particular zone must use the same address types as shown in below examples.
Example 1:
- SIP signaling port 1 - IPv4 address
- SIP signaling port 2 - IPv4 address
Example 2:
- SIP signaling port 1 - IPv6 address
- SIP signaling port 2 - IPv6 address
Example 3:
- SIP signaling port 1 - IPv4 / IPv6 addresses
- SIP signaling port 2 - IPv4 / IPv6 addresses
A SIP Signaling Port must reference one IP Interface Group signifying that signaling associated with that port is restricted to IP Interfaces in that group. Only reference IP Interface Groups within the same Address Context.
The SBC 7000 system supports creating IP Interface Groups containing sets of IP interfaces that are not "processor friendly" (i.e. carried on physical Ethernet ports served by separate processors). However, restrictions exist regarding the usage of such Interface Groups.
(This ability does not apply to the SBC 5400, which has only two physical media ports. You may configure the IP interfaces from the two physical ports within the same IP Interface Groups without restrictions.)
For complete details, refer to Configuring IP Interface Groups and Interfaces.
If a zone's sipSigPort
is configured for transportProtocolsAllowed
= sip-tls-tcp
, the SBC increments the configured portNumber
by 1 and uses it as the new port number for SIP over TLS signaling. The SBC then opens a TCP socket for SIP over TLS for the new TCP port number.
Example: When sipSigPort
is configured with a portNumber
of 5060 and transportProtocolsAllowed
= sip-tls-tcp
, the SBC listens on TCP port 5061 for SIP over TLS.
Command Syntax
SBC 7000/SWe Syntax
% set addressContext <name> zone <name> sipSigPort <index #> action <dryup | force> dryUpTimeout <1-1440 mins> dscpValue <0-63> enforceAORMatch <disabled | enabled> facState <disabled | system> ipAddressV4 <IPv4 address> ipAddressV6 <IPv6 address> ipInterfaceGroupName <name> maskIpAddressforRcb <disabled | enabled> maskPortforRcb <disabled | enabled> mode <inService | outOfService> portNumber <1-65535> recorder <disabled | enabled> sctpProfileName <name> siprec <disabled | enabled> sipTcpConnectionAgingState <disabled | enabled> state <disabled | enabled> tcpConnectTimeout <0-180> tcpKeepaliveInterval <60-120 seconds> tcpKeepaliveProbes <1-10> tcpKeepaliveTime <60-7200 seconds> tcpUserTimeout < 0 | 10-3600 seconds > tlsProfileName <name> transportProtocolsAllowed <sip-sctp | sip-tcp | sip-tls-tcp | sip-udp | sip-ws-tcp | sip-wss-tls>
S-SBC Syntax
% set addressContext <name> zone <name> sipSigPort <index #> action <dryup | force> dryUpTimeout <1-1440 mins> dscpValue <0-63> enforceAORMatch <disabled | enabled> facState <disabled | system> ipInterfaceGroupName <name> ipPublicVarV4 <metadata> ipPublicVarV6 <metadata> ipVarV4 <metadata> ipVarV6 <metadata> maskIpAddressforRcb <disabled | enabled> maskPortforRcb <disabled | enabled> mode <inService | outOfService> portNumber <1-65535> recorder <disabled | enabled> sctpProfileName <name> siprec <disabled | enabled> sipTcpConnectionAgingState <disabled | enabled> state <disabled | enabled> tcpConnectTimeout <0-180> tcpKeepaliveInterval <60-120 seconds> tcpKeepaliveProbes <1-10> tcpKeepaliveTime <60-7200 seconds> tcpUserTimeout < 0 | 10-3600 seconds > tlsProfileName <name> transportProtocolsAllowed <sip-sctp | sip-tcp | sip-tls-tcp | sip-udp | sip-ws-tcp | sip-wss-tls>
Make sure when configuring sipSigPort
and dsbcSigPort
for an S-SBC deployment that you specify different IP addresses for them. To do so you must select different metavariables for each of them. The actual values of the metavariables are determined during orchestration based on your Heat templates.
Command Parameters
Key |
---|
M = Mandatory O = Optional |
Zone SIP Signaling Port Parameters
If recorder
is enabled
, the SBC does not handle the following requests. To overcome this, configure a separate SIP Signaling Port towards the recording server (with recorder enabled
).
- OPTIONS
- NOTIFY
- SUBSCRIBE
- MESSAGE
- PUBLISH
- INFO
- REFER
- REGISTER
S-SBC Parameter Differences
For S-SBC configurations, the following parameters are used in lieu of ipAddressV4
and ipAddressV6
parameters listed in the above table.
Command Examples
To set SBC tcpKeepaliveTime
to 90 seconds, tcpKeepaliveInterval
to 60 seconds and tcpKeepaliveProbes
count to 2:
set addressContext default zone ZONE_SIPART_AS sipSigPort 2 tcpKeepaliveTime 90 tcpKeepaliveInterval 60 tcpKeepaliveProbes 2 commit show details addressContext default zone ZONE_SIPART_AS sipSigPort 2 ipInterfaceGroupName LIG2; ipAddressV4 10.11.12.13; portNumber 5060; mode inService; state enabled; recorder disabled; siprec disabled; tcpConnectTimeout 5; dscpValue 0; tlsProfileName defaultTlsProfile; transportProtocolsAllowed sip-tcp; sctpProfileName defaultSctpProfile; tcpKeepaliveTime 90; tcpKeepaliveInterval 60; tcpKeepaliveProbes 2;
To create a S-SBC SIP Signaling Port for a particular zone:
set system ntp timeZone vsbcSystem zone asia-Kolkata commit set addressContext default dnsGroup SWeDNS commit set addressContext default dnsGroup SWeDNS server SWeDNS ipAddress fd00:10:6b50:45c0::b4 priority 0 state enabled commit set addressContext default dnsGroup SWeDNS type ip interface S_IMS_SIG_V6 commit set addressContext default zone INTERNAL id 3 sipSigPort 1 ipInterfaceGroupName S_VBIZ_V4 ipVarV4 IF6.IPV4 portNumber 5060 transportProtocolsAllowed sip-udp,sip-tcp state enabled mode inService commit set addressContext default zone EXTERNAL id 4 sipSigPort 2 ipInterfaceGroupName S_IMS_SIG_V6 ipVarV6 IF2.IPV6 portNumber 5060 transportProtocolsAllowed sip-udp,sip-tcp state enabled mode inService commit set addressContext default zone INTERNAL id 3 sipSigPort 3 ipInterfaceGroupName S_CDMA_V4 ipVarV4 IF5.IPV4 portNumber 5060 transportProtocolsAllowed sip-udp,sip-tcp state enabled mode inService commit set addressContext default zone INTERNAL sipTrunkGroup INGRESS_TG mode inService state enabled media mediaIpInterfaceGroupName M_VBIZ_V4 commit set addressContext default zone INTERNAL sipTrunkGroup INGRESS_TG ingressIpPrefix 0.0.0.0 0 commit set addressContext default zone EXTERNAL sipTrunkGroup EGRESS_TG mode inService state enabled media mediaIpInterfaceGroupName M_IMS_SIG_V6 commit set addressContext default zone INTERNAL sipTrunkGroup EGRESS_TGV4 mode inService state enabled media mediaIpInterfaceGroupName M_CDMA_V4 commit set addressContext default zone EXTERNAL sipTrunkGroup EGRESS_TG ingressIpPrefix :: 0 commit
To set tcpUserTimeout:
set addressContext default zone defaultSigZone sipSigPort 1 tcpUserTimeout 0 commit