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. The
Unable to show "metadata-from": No such page "_space_variables"
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, the
Unable to show "metadata-from": No such page "_space_variables"
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. The
Unable to show "metadata-from": No such page "_space_variables"
maintains the connection IDs based on SipSigPort ID, Protocol, IP Address Type and IP Address. The
Unable to show "metadata-from": No such page "_space_variables"
sends the message using a different connection ID for UDP. The
Unable to show "metadata-from": No such page "_space_variables"
uses the same connection ID for sending out the subsequent messages from the corresponding registered user.
Salient points about this feature:
The
Unable to show "metadata-from": No such page "_space_variables"
uses the independent media port range per IPTG if configured.The
Unable to show "metadata-from": No such page "_space_variables"
uses the system wide media port range if no independent media port range is configured per IPTG.The
Unable to show "metadata-from": No such page "_space_variables"
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.
The
Unable to show "metadata-from": No such page "_space_variables"
supports this feature when:- Only one
SipSigPort
is configured on egress. - IP address of
SipSigPort
is the same as the associated LIF IP.
Feature limitations and restrictions:
This feature is supported only for UDP.
Disable the flag 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.