Guest

Preview Tool

Cisco Bug: CSCsg33741 - Caller Name/Caller ID incorrect on a SIP truk Transf scenarios

Last Modified

Jul 04, 2017

Products (1)

  • Cisco Unified Communications Manager (CallManager)

Known Affected Releases

4.1(3)SR4

Description (partial)

Symptom:
No caller Name display when one party drops a call from SIP truk conference in a scenario.

Conditions:
Steps to Reproduce:
Cluster 1 setup:
Have a Sip Trunk "siptr1" with the caller name "cluster1sip".
Register IP phones A (1008), B (1009) in cluster1.
Create a Route pattern 3XXX  in cluster1and select the Sip Trunk "siptr1".

Cluster 2 setup:
Have a Sip Trunk "siptr2" with the caller name "cluster2sip"
Register IP phone C (3017) registered in cluster2.
Create a Route pattern 1XXX configured in cluster2 and select Sip Trunk "siptr2".

Call steps:
Issue1:

1.Make a call from phone A to phone C via sip trunk. Answer it in phone C and call gets connected. Phone A shows "To 3017" and Phone C shows "cluster1sip (1008)". 
2.Now from phone C do a conference to phone B. Phone A,B,C are in conference and display changes to "To conference" in Phone A,C and "From conference" in phone B. 
3.Disconnect the calls from phone A. Now phone B and C are connected. After this Phone C shows "To 1009" and Phone B shows "From 3017". 

Since it is a sip trunk call display in phone B should be with caller name "cluster2sip" not just "From 3017". 
Issue2:

Made a call from phone A to phone C via sip trunk. Call is connected and in phone C presses "transf" softkey to initiate blind transfer to phone B via sip trunk. Here after Phone A display changes to "To 1009" from "To 3017".But Phone B shows "From Cluster2sip 3017" instead of "From 1008".In case of consult transfer the display in Phone B is correct.
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.