Guest

Preview Tool

Cisco Bug: CSCul58705 - EMCC devices' SLRG always points to EMCC SIP trunk

Last Modified

Oct 01, 2019

Products (16)

  • Cisco Unified Communications Manager (CallManager)
  • Cisco Business Edition 5000 Version 8.6
  • Cisco Intercompany Media Engine
  • Cisco Unity Connection Version 9.1
  • Cisco Business Edition 5000 Version 9.1
  • Cisco Business Edition 6000 Version 8.5
  • Cisco Business Edition 3000 Version 8.6
  • Cisco Business Edition 5000 Version 8.5
  • Cisco Unified Communications Manager Version 8.6
  • Cisco Unity Connection Version 8.5
View all products in Bug Search Tool Login Required

Known Affected Releases

8.0(1) 8.5(1) 8.6(1) 8.6(2) 9.1(1) 9.1(2)

Description (partial)

Symptom:
EMCC devices' SLRG always points to EMCC SIP trunk. So, if the Home Cluster's regular dial plan (for local / long distance calls) is not globalized but configured with SLRG, EMCC devices' calls on the home cluster might fail, as it gets routed to the Visiting Cluster instead of the Home Cluster's gateway.

Conditions:
Detailed scenario :

- Europe cluster has regular dial plan defined based on SLRG. The route patterns point to SLRG, and every local Device Pool is configured with SLRG.
- EMCC implemented between Americas and Europe clusters
- European user travels to America, and logs back in to Europe cluster using EMCC
- EMCC user dials local call to London number. This call hits route pattern that points to a standard local route group. SLRG for EMCC device is the EMCC SIP trunk, irrespective of what is set on the roaming device pool on the home cluster (http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/8_6_1/ccmfeat/fsemcc.html#wp1462644). So, the call to local London number now gets routed from home cluster to visiting cluster through the EMCC SIP trunk
- Even if routing is set up on the visiting cluster, it becomes an international call and negates the purpose of EMCC login
- Even with the concept of multiple Local Route Groups, every Local Route Group will pick EMCC SIP Trunk for EMCC device, irrespective of what is set on the roaming device pool on the home cluster
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.