Can we still use Phantom location in an inter-cluster ELCAC config?

[Koen Van Impe]

We have a multi-cluster environment with UCCE and CVP.

Originally, ELCAC was not configured for inter-cluster traffic. (no LBM configured)

We do use Locations in CVP to send IP originated calls from remote sites to a combo gateway in that same site.

Inter-cluster ELCAC has been enable recently for other purposes, but has broken our CVP functions for IP originated calls.

After analysis, it turns out we can't make calls any more to the Phantom location, in which we have our SIP trunks to CVP (as per Cisco documentation).

Why does inter-cluster ELCAC have an influence on Phantom location?

Regards,

Koen

[Lisandro Quinteros]

Check this video of Kevin Wallace.. was about location changes on CUCM 9 he recommended to replace phantom for shadow location

https://www.youtube.com/watch?v=NzOINea_KqQ

From SRND 9 http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/srnd/9x/uc9x/cac.html

 Phantom locations are legacy locations that allow for the transmission of location information in versions of Unified CM prior to 9.0, but they are not supported with Unified CM 9.x Enhanced Locations CAC

SShadow Location

The shadow location is used to enable a SIP trunk to pass Enhanced Locations CAC information such as location name and Video-Traffic-Class (discussed below), among other things, required for Enhanced Locations CAC to function across clusters. In order to pass this location information across clusters, the SIP intercluster trunk (ICT) must be assigned to the "shadow" location. Similar to the "phantom" location, it cannot have a link to other locations, and therefore no bandwidth can be reserved between the shadow location and other locations. Any device other than a SIP ICT that is assigned to the shadow location will be treated as if it was associated to Hub_None. That is important to know because if a device other than a SIP ICT ends up in the shadow location, bandwidth deductions will be made from that device as if it were in Hub_None, and that could have varying effects depending on the location and links configuration.

Hope it helps, please rate useful posts

Lisandro