Courtesy callback is not offered, when EWT in the ICM is set more than 30 minutes

From DocWiki

(Difference between revisions)
Jump to: navigation, search
m (1 revision)
 
(7 intermediate revisions not shown)
Line 1: Line 1:
{| border="1"
{| border="1"
|-
|-
-
! '''Problem Summary'''
+
! '''Problem Summary'''  
-
| Courtesy callback is not offered, when EWT in the ICM is set more than 30 minutes.
+
| Courtesy callback is not offered, when EWT in the ICM is set more than 30 minutes.  
 +
Consider the following scenario:
 +
 
 +
When a TDM caller makes a call, a callback is offered and accepted. The callback is initiated and the caller answers the call. After 250-260 sec the callback entry on the Reporting Server portal gets erased and as a result no Courtesy Callback is offered.
 +
 
|-
|-
-
! '''Possible Cause'''
+
! '''Possible Cause'''  
-
| When EWT in the ICM is set more than 30 minutes, the call entry on the Reporting Server gets erased and as a result the Courtesy Callback is not offered.
+
| When EWT in the ICM is set more than 30 minutes, the callback entry on the Reporting Server gets erased and as a result the Courtesy Callback is not offered. This is because the Gateway terminates the VRU leg by sending BYE which Unified CVP uses for any callback. As a result, Unified CVP erases all call details of the call and as result the callback is not made. It is found that a possible SIP session time out causes this behavior.
|-
|-
-
! '''Recommended Action'''
+
! '''Recommended Action'''  
-
| The following configuration has to be made on the Ingress gateway/CUBE:
+
| The following configuration has to be made on the Ingress gateway/CUBE:  
   voice service voip
   voice service voip
-
  sip
+
sip
-
  min-se 7200 session-expires 7200
+
min-se 7200 session-expires 7200                                                                                            
-
!
+
 
 +
!  
|-
|-
-
! '''Release'''
+
! '''Note'''  
-
| Release 9.0(1)  
+
| In addition to the above configuration the session expire in the CUCM should also be changed to a higher value (7200), otherwise the callback will fail in Unified CVP due to SIP error response 422(session expire value too low) from Gateway.
|-
|-
-
! '''Associated CDETS #'''
+
! '''Release'''  
-
| CSCua18769'''
+
| Release 9.0(1)
|-
|-
 +
! '''Associated CDETS #'''
 +
| CSCua18769
|}
|}
-
 
-
<Replace this entire line with the required category or categories.>
 

Latest revision as of 12:48, 16 October 2012

Problem Summary Courtesy callback is not offered, when EWT in the ICM is set more than 30 minutes.

Consider the following scenario:

When a TDM caller makes a call, a callback is offered and accepted. The callback is initiated and the caller answers the call. After 250-260 sec the callback entry on the Reporting Server portal gets erased and as a result no Courtesy Callback is offered.

Possible Cause When EWT in the ICM is set more than 30 minutes, the callback entry on the Reporting Server gets erased and as a result the Courtesy Callback is not offered. This is because the Gateway terminates the VRU leg by sending BYE which Unified CVP uses for any callback. As a result, Unified CVP erases all call details of the call and as result the callback is not made. It is found that a possible SIP session time out causes this behavior.
Recommended Action The following configuration has to be made on the Ingress gateway/CUBE: 
 voice service voip
sip
min-se 7200 session-expires 7200
Note In addition to the above configuration the session expire in the CUCM should also be changed to a higher value (7200), otherwise the callback will fail in Unified CVP due to SIP error response 422(session expire value too low) from Gateway.
Release Release 9.0(1)
Associated CDETS # CSCua18769

Rating: 0.0/5 (0 votes cast)

Retrieved from "http://docwiki.cisco.com/wiki/Courtesy_callback_is_not_offered,_when_EWT_in_the_ICM_is_set_more_than_30_minutes"
Personal tools