Preview Tool

Cisco Bug: CSCtf33489 - CUCM PGW SIP: Outgoing server selection should correspond to RG config

Last Modified

Feb 01, 2017

Products (3)

  • Cisco Unified Communications Manager (CallManager)
  • Cisco Unity Connection Version 7.1
  • Cisco Unified Communications Manager Version 7.1

Known Affected Releases


Description (partial)


In normal operation, outbound calls always use VIP1 and load balance between CUCM1 and CUCM2.

If we disconnect one of the physical interfaces on PGW1, this causes PGW1 to use VIP2, Meaning that all outbound call from CUCM will now go to PGW-VIP2 though SIP_trunk_to_VIP2. Now CUCM is always sending INVITE from CUCM1 to PGW1 VIP1 (DOWN), timeout, and then INVITE from CUCM3 to PGW1 VIP2 (UP). 
In this scenario we don't see load balancing among the servers in CUCM group of  SIP trunk to VIP2. CUCM2 is always used for the outgoing calls. In such PGW failure scenario we expect load balancing of outbound calls between CUCM servers that are assigned to the working trunk's CUCM group via device pool.


CUCM - PGW SIP integration.
CUCM is configured with 2 SIP trunks pointing to PGW VIP1 and PGW VIP2.
SIP trunk to VIP1 has CUCM1, CUCM2 in the associated Callmanager group.
SIP trunk to VIP2 has CUCM2, CUCM1 is the associated Callmanager group.
Route List to PGW (PSTN) has CUCM4, CUCM3 is the associated Callmanager group.
Route list is pointing to RG-PGW-Outbound which has SIP_trunk_to_VIP1 and SIP_trunk_to_VIP2 in top-down order.
Bug details contain sensitive information and therefore require a 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.