Professional Documents
Culture Documents
Transfer Mode
MediaManager(214616)::wait_AuConnectRequest, CI(33846747,33846748), capCount(6,4), mcNodeId(0,0), xferMode(16,4), reConnectType(0),
mrid (0, 0) IFCreated(0 0) proIns(0 0), AC(0,0)
xferMode(16,4), means one side of the call leg is a SIP device and other side of the device is a skinny device.
const NATURAL CIRCUIT_MODE = 0;
const NATURAL CALL_INDEPENDENT_SIGNALING_CONNECTION_MODE = 0;
const NATURAL PACKET_MODE = 2;
const NATURAL H323_MODE = 3;
DTMFMTPSide*(2*)
This represents which side of the call leg we are mentioning. So, these values are either 1 or 2.
mtpNeededForDtmf(1)
DTMFMTP_None=0,
DTMFMTP_CapMismatch,
DTMFMTPReason_Config,
DTMFMTPReason_SavedConnection,
DTMFMTPReason_ProvideOOBSet,
DTMFMTPReason_RSVPWithXcoder
firstconnDTMF(3) or secondconnDTMF(2)
NoDTMF=0,
OOB,
RFC2833,
OOB_RFC2833,
UnknownDTMF
DMTFConfig
BestEffort=1,
PreferOOB,
Prefer2833,
PreferBoth
DTMFMethod
NoDTMF=0,
OOB,
RFC2833,
OOB_RFC2833,
UnknownDTMF
|interfacesEstablished
Cause_ModifiedCap,
Cause_AgentChange
// CIA2180:CSCtb36936
// CSCtg52998
Why MTP got Inserted though both sides have matching caps?
00:30:21.267 |SIG-MediaManager-(1463678)::wait_AuConnectRequest, CI(44923859,44923860), capCount(6,11), mcNodeId(0,0),
xferMode(16,12), reConnectType(0), mrid (0, 0) IFCreated(0 0) proIns(0 0), AC(0,0) party1DTMF(3 2 101 1 0) party2DTMF(1 3 0 1
0),reConnFlag=0, connType(3,3), IFHand(0,0),*MTP(2,0),*MRGL(63e214ae-566f-0c89-e222-fa429caaf9da,) videoCap(0 0),
mmCallType(0),FS(0,0) IpAddrMode(0 0) aPid(2, 74, 1092820), bPid(2, 140, 684) EOType(0 0) MOHAnnConnType(0
0)|2,100,160,1.7496146^198.5.85.214^*
MTP(2,0)
side 1 specifies 2 as MTP requirements, which means RequiresRFC2833MediaTerminationPoint
So, MTP got inserted just because it was configured to insert though both side may not have needed MTP based on their caps support and
interregion bw value.
NoRequirements,
RequiresMediaTerminationPoint,
RequiresRFC2833MediaTerminationPoint,
RequiresMediaTerminationPointAndUseTRP, // Both "MTP required" and "Use TRP" are checked
RequiresRFC2833MediaTerminationPointAndUseTRP, // Both "MTP required" with RFC2833 cap and "Use TRP" are checked
RequiresRFC2833AndUseTRP, // "Use TRP" is checked, and RFC2833 cap needed
UseTRP, // "Use TRP" is checked
Disable_AudioPassThru // Media will disable audio pass thru if either endpoint sets this flag.
Media_Payload_Max,
// Please leave this so we won't get compile errors.'
Media_Payload_RFC2833_DynPayload = 257, // This is an extended payload type to indicate RFC2833 support
Media_Payload_PassThrough = 258,
Media_Payload_Dynamic_Payload_PassThru = 259,
//Can be used for any dynamic Payload type but is mainly being used for 2833 in SD
GA release
Media_Payload_DTMF_OOB = 260,
Media_Payload_Inband_DTMF_RFC2833 = 261,