Page History

Noprint
Panel borderColor green bgColor transparent borderWidth 2 Back to Table of Contents Back to SIP Services Back to SIP Signaling

 

The Cisco Unified Communication Manager (CUCM) does not allow multiple endpoints to register with same IP Port addresses. Any subsequent registration that uses same IP Port is rejected with 405 response code. SBC overcomes The

Spacevars
0 product

 overcomes this with the ability to use different ports for each new registration on egress side when registering with CUCM using the flag usePortRangeFlag.

When this flag is enabled, SBC egresses the

Spacevars
0 product

 egresses the SIP REGISTER message via a new port for each REGISTER message. This feature uses the media port range configured on trunk group and at the global level for to open the port. SBC maintains The

Spacevars
0 product

 maintains the connection IDs based on SipSigPort ID, Protocol, IP Address Type and IP Address. SBC sends The

Spacevars
0 product

 sends the message using a different connection ID for UDP. SBC uses The

Spacevars
0 product

 uses the same connection ID for sending out the subsequent messages from the corresponding registered user.

Some salient points to note for Salient points about this feature:

• The

  Spacevars
  0 product

   uses SBC uses the independent media port range per IPTG if configured.

• The

  Spacevars
  0 product

   uses SBC uses the system wide media port range if no independent media port range is configured per IPTG.

• The

  Spacevars
  0 product

   uses SBC uses a different port from this port range for each unique new egress registration towards the trunk group. Any de-registration shall free the corresponding port for re-use by another registration or media port requirement.

Excerpt

The Spacevars 0 product SBC supports this feature when: Only one SipSigPort is configured on egress. IP address of SipSigPort is the same as the associated LIF IP. note Info title Note Disable usePortRangeFlag flag before performing the Live Software Upgrade (LSWU).   Feature limitations and restrictions: This feature is supported only for UDP. Disable the flag passCompleteContact passCompleteContactHeader to use this feature. Do not use this feature if two Interfaces are configured on the same Interface Group. Disable this flag before performing LSWU.

Info
icon false title Related articles
SIP Trunk Group - Signaling - CLI Transparency Flags sipTrunkGroup signaling - CLI Sip SIP Trunk Group - Signaling (EMA) Common Ip Attributes - Transparency Flags (EMA)

Pagebreak