Guest

Preview Tool

Cisco Bug: CSCvu08043 - Enhancement - CMS peer link config clarification

Last Modified

May 06, 2020

Products (1)

  • Cisco Meeting Server

Known Affected Releases

2.9 unspecified

Description (partial)

Symptom:
Our CMS resiliency docs currently state for configuring clustered callbridges:

c. Leave the Peer Link SIP Domain blank unless you have call control devices between your
Call Bridges. If you leave the field blank then the address of the outbound SIP call will be in
the form of a random URI generated by the Call Bridge followed by the IP address of the
Call Bridge that it is linking to (for example randomURI@10.10.10.10) . If you specify the
Peer Link SIP Domain then, that is what will be used when calling to a remote server for a
Peer call. You can have it route to your call control device if you have set up an Outbound
Rule that matches the Peer Link SIP Domain. If routing through an existing call control, it is
recommended to use a unique domain or each servers’ FQDN for the Peer link SIP domain.
This ensures no accidental call loops that can occur if using the same domain on all. 

I propose revising this to avoid confusion.  It would change the notes at this Point:  
If you specify the Peer Link SIP Domain then, that is what will be used when calling to a remote server for a Peer call.  You can have it route to your call contorl device if you have set up an Outbound rule that has your call control as SIP Proxy to use.  Or you can still call direct by putting your CMS FQDN in your outbound calls as SIP Proxy to use to route direct without a call control. If routing through an existing call control, it is recommended to use a unique domain or each servers’ FQDN for the Peer link SIP domain. This ensures no accidental call loops that can occur if using the same domain on all.

Conditions:
na
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.