DTMF are getting ripped off after hitting the MPP


Doc ID    SOLN272850
Version:    1.0
Status:    Published
Published date:    02 Aug 2015
Author:   
Mukti Sharma
 

Details

 

Problem Clarification

 Customer is passing the DTMF to MPP over RTP payload after analyzing the logs BBE found that MPP is not recognizing few DTMF

                  

Call 1 analysis

In list trace on CM side I can see that below DTMF are being sent to MPP(Customer system is in Australian time zone GMT+10)

List trace file Test call 1 220715.txt

10:39:05     digit 2 originated by station    1722 cid 0x3293

10:39:09     digit 2 originated by station    1722 cid 0x3293

: 10:39:12     digit 4 originated by station    1722 cid 0x3293

10:39:19     digit 1 originated by station    1722 cid 0x3293

10:39:43     digit 1 originated by station    1722 cid 0x3293

10:40:15     digit 5 originated by station    1722 cid 0x3293

10:40:16     digit 1 originated by station    1722 cid 0x3293

10:40:16     digit 0 originated by station    1722 cid 0x3293

10:40:16     digit 5 originated by station    1722 cid 0x3293

10:40:16     digit 1 originated by station    1722 cid 0x3293 

10:40:17     digit 0 originated by station    1722 cid 0x3293

10:40:17     digit 5 originated by station    1722 cid 0x3293

10:40:17     digit 1 originated by station    1722 cid 0x3293

10:40:17     digit 0 originated by station    1722 cid 0x3293

10:40:18     digit 5 originated by station    1722 cid 0x3293

10:40:18     digit 1 originated by station    1722 cid 0x3293

10:40:18     digit 0 originated by station    1722 cid 0x3293

10:40:18     digit 5 originated by station    1722 cid 0x3293

10:40:19     digit 1 originated by station    1722 cid 0x3293

10:40:19     digit 0 originated by station    1722 cid 0x3293

10:40:19     digit 0 originated by station    1722 cid 0x3293

: 10:40:19     digit # originated by station    1722 cid 0x3293

10:40:28     digit 0 originated by station    1722 cid 0x3293

10:40:28     digit 4 originated by station    1722 cid 0x3293

10:40:29     digit 1 originated by station    1722 cid 0x3293

10:40:29     digit 7 originated by station    1722 cid 0x3293

10:40:32     digit 4 originated by station    1722 cid 0x3293

10:40:32     digit 5 originated by station    1722 cid 0x3293

10:40:32     digit 8 originated by station    1722 cid 0x3293

10:41:03     digit 1 originated by station    1722 cid 0x3293

10:42:00     digit # originated by station    1722 cid 0x3293

10:42:01     digit * originated by station    1722 cid 0x3293

10:42:07     digit * originated by station    1722 cid 0x3293

10:42:19     digit * originated by station    1722 cid 0x3293

10:42:21     digit * originated by station    1722 cid 0x3293

10:42:21     digit * originated by station    1722 cid 0x3293

10:42:22     digit * originated by station    1722 cid 0x3293

 10:42:23     digit * originated by station    1722 cid 0x3293

10:42:23     digit * originated by station    1722 cid 0x3293

10:42:24     digit * originated by station    1722 cid 0x3293

10:42:24     digit * originated by station    1722 cid 0x3293

10:42:24     digit * originated by station    1722 cid 0x3293

10:42:24     digit * originated by station    1722 cid 0x3293

10:42:25     digit * originated by station    1722 cid 0x3293

10:42:25     digit * originated by station    1722 cid 0x3293

 

 

Below DTMF digits are recievd on MPP(R2-SP-EP-MPP-2015203011254-18)

 

@2015-07-22 10:38:46,700||FINER|SessMgr|3698||IncomingDtmfDigitsComplete: [] Reason = 6, Bargein = 0 |R1-SP-EP-MPP####

@2015-07-22 10:38:49,664||FINER|SessMgr|3698||IncomingDtmfDigitsComplete: [] Reason = 6, Bargein = 0 |R1-SP-EP-MPP####

@2015-07-22 10:38:49,810||FINER|SessMgr|3698||IncomingDtmfDigitsComplete: [] Reason = 6, Bargein = 0 |R1-SP-EP-MPP####

@2015-07-22 10:39:06,018||FINER|SessMgr|3698||IncomingDtmfDigitsComplete: [2] Reason = 0, Bargein = 1 |R1-SP-EP-MPP####

@2015-07-22 10:39:09,178||FINER|SessMgr|3698||IncomingDtmfDigitsComplete: [2] Reason = 0, Bargein = 1 |R1-SP-EP-MPP####

@2015-07-22 10:39:12,158||FINER|SessMgr|3698||IncomingDtmfDigitsComplete: [4] Reason = 0, Bargein = 1 |R1-SP-EP-MPP####

@2015-07-22 10:39:14,868||FINER|SessMgr|3698||IncomingDtmfDigitsComplete: [] Reason = 6, Bargein = 0 |R1-SP-EP-MPP####

@2015-07-22 10:39:19,898||FINER|SessMgr|3698||IncomingDtmfDigitsComplete: [1] Reason = 0, Bargein = 1 |R1-SP-EP-MPP####

@2015-07-22 10:39:27,349||FINER|SessMgr|3698||IncomingDtmfDigitsComplete: [] Reason = 6, Bargein = 0 |R1-SP-EP-MPP####

@2015-07-22 10:39:36,604||FINER|SessMgr|3698||IncomingDtmfDigitsComplete: [] Reason = 6, Bargein = 0 |R1-SP-EP-MPP####

@2015-07-22 10:39:44,238||FINER|SessMgr|3698||IncomingDtmfDigitsComplete: [1] Reason = 0, Bargein = 1 |R1-SP-EP-MPP####

@2015-07-22 10:40:19,877||FINER|SessMgr|3698||IncomingDtmfDigitsComplete: [5105105105105100#] Reason = 0, Bargein = 0 |R1-SP-EP-MPP####

@2015-07-22 10:40:29,418||FINER|SessMgr|3698||IncomingDtmfDigitsComplete: [0417] Reason = 0, Bargein = 0 |R1-SP-EP-MPP####

@2015-07-22 10:40:32,797||FINER|SessMgr|3698||IncomingDtmfDigitsComplete: [458] Reason = 0, Bargein = 1 |R1-SP-EP-MPP####

@2015-07-22 10:40:58,907||FINER|SessMgr|3698||IncomingDtmfDigitsComplete: [] Reason = 6, Bargein = 0 |R1-SP-EP-MPP####

@2015-07-22 10:41:03,738||FINER|SessMgr|3698||IncomingDtmfDigitsComplete: [1] Reason = 0, Bargein = 1 |R1-SP-EP-MPP####

@2015-07-22 10:42:09,880||FINER|SessMgr|3698||IncomingDtmfDigitsComplete: [] Reason = 6, Bargein = 0 |R1-SP-EP-MPP####

@2015-07-22 10:42:29,426||FINER|SessMgr|3698||IncomingDtmfDigitsComplete: [] Reason = 6, Bargein = 0 |R1-SP-EP-MPP####

 

 

In below sniffer trace we can see from CM side  MPP is receiving all the DTMF (Compare digits received in lis trace List trace) but somehow it is not recognizing it.

 

 

 

Cause

calls received frequent SIP re-INVITE requests for media shuffling.  This eventually caused MPP to fail to recognize digits.  Known issue and fixed in to EP 7.0.2.

Solution

 

1.  Known issue and fixed in to EP 7.0.2.

2.  Customer can turn off shuffling from Cm side (In customer system every call shuffles as they’re all SIP. They only have 80 DSP resources in 1x G450 gw for their entire system. Turn off shuffling, and DSP usage will go sky high. If shuffling is turned off it’ll require more DSP resources and will result in a system redesign. That’s not an option in this case so they will go for an AAEp upgrade)


Avaya -- Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy