[cisco-voip] Can Cisco UCM Support Multiple MTPs on same call?
Ryan Ratliff
rratliff at cisco.com
Wed Oct 8 13:29:51 EDT 2008
That's what I mean when I say a transcoder can be an MTP but an MTP cannot
transcode. The older NM-HDV transcoders can definitely do some MTP
functions but they may not support some of the newer supplementary services
(particulary around SIP). If you are using a 2851 you have the newer DSPs
and they can most definitely support all of the supplementary services MTP
functions.
-Ryan
_____
From: Matt Slaga (US) [mailto:Matt.Slaga at us.didata.com]
Sent: Wednesday, October 08, 2008 12:33 PM
To: Matt Slaga (US); Ryan Ratliff
Cc: cisco-voip at puck.nether.net
Subject: RE: [cisco-voip] Can Cisco UCM Support Multiple MTPs on same call?
I did find some more information on this in UCM 6.0 documentation
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/6_0_1/ccmsys/a05tra
ns.html
Excerpt:
Cisco Unified Communications Manager supports MTP and transcoding
functionality simultaneously. For example, if a call originates from a Cisco
Unified IP Phone (located in the G723 region) to NetMeeting (located in the
G711 region), one transcoder resource supports MTP and transcoding
functionality simultaneously.
So according to this, a single MTP resource gets enacted to act as both
xcode and supplementary services MTP. That would require a hardware MTP
obviously (software MTP cannot xcode) which is not a problem in this case.
I'll have to do more tracing and stats to get to the bottom of that.
What is interesting in this same doc, it states specifically that the
WS-X6608 can do both MTP and XCode, but does not state this for NM-HDV
(pretty old info apparently, don't see anything on newer hardware). That of
course doesn't mean that it cannot perform both simultaneously, but it also
doesn't mean that it can. In this instance, we are using a 2851 with
hardware DSP resources.
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Matt Slaga (US)
Sent: Thursday, October 02, 2008 9:50 AM
To: Ryan Ratliff
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Can Cisco UCM Support Multiple MTPs on same call?
No worries. These are UCM traces.
From: Ryan Ratliff [mailto:rratliff at cisco.com]
Sent: Thursday, October 02, 2008 9:26 AM
To: Matt Slaga (US)
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Can Cisco UCM Support Multiple MTPs on same call?
Without the full CCM traces I can't begin to tell why that call is failing.
Are those router debugs?
-Ryan
On Oct 1, 2008, at 4:36 PM, Matt Slaga ((US)) wrote:
Right, but some MTPs cannot Xcode (i.e. software). I was trying to make
that distinction.
Here is my underlying issue:
One call coming into the SIP trunk fails:
10/01/2008 11:22:03.345 CCM|(isHeldOrHolding):
er=0,ee=0,mh=0|<CLID::DDNA><NID::10.194.12.215><CT::4,100,78,6.1><IP::><DEV:
:><LVL::Detailed><MASK::ffffff>
10/01/2008 11:22:03.345 CCM|getOobScbId: Created scbId. mOobScbId=1163,
ccbId=1162|<CLID::DDNA><NID::10.194.12.215><LVL::Detailed><MASK::ffffff>
10/01/2008 11:22:03.345
CCM|//SIP/SIPCdpc(2,83,530)/ci=71719367/ccbId=1162/scbId=0/setCgpnNumPresent
ation: fIdPresentation is 1 and the SIP Trunk Config is
1|<CLID::DDNA><NID::10.194.12.215><CT::4,100,78,6.1><IP::><DEV::><LVL::Detai
led><MASK::ffffff>
10/01/2008 11:22:03.345
CCM|//SIP/SIPCdpc(2,83,530)/ci=71719367/ccbId=1162/scbId=0/applyNumPresentat
ionBasedOnDirection: fIdPresentation is 1 and the DialogDirection is 1
|<CLID::DDNA><NID::10.194.12.215><CT::4,100,78,6.1><IP::><DEV::><LVL::Detail
ed><MASK::ffffff>
10/01/2008 11:22:03.345
CCM|//SIP/SIPCdpc(2,83,530)/ci=71719367/ccbId=1162/scbId=0/setCgpnNamePresen
tation: fIdPresentation is 1 SIP Trunk Config is 1
|<CLID::DDNA><NID::10.194.12.215><CT::4,100,78,6.1><IP::><DEV::><LVL::Detail
ed><MASK::ffffff>
10/01/2008 11:22:03.345
CCM|//SIP/SIPCdpc(2,83,530)/ci=71719367/ccbId=1162/scbId=0/applyNamePresenta
tionBasedOnDirection: fIdPresentation is 1
|<CLID::DDNA><NID::10.194.12.215><CT::4,100,78,6.1><IP::><DEV::><LVL::Detail
ed><MASK::ffffff>
10/01/2008 11:22:03.346
CCM|//SIP/SIPCdpc(2,83,530)/ci=71719367/ccbId=1162/scbId=0/setCnNameAndNumbe
r: connectedName connectedNumber 5404274502 connectedNumberPi 1
connectedNamePi 1 connectedSi
0|<CLID::DDNA><NID::10.194.12.215><CT::4,100,78,6.1><IP::><DEV::><LVL::Detai
led><MASK::ffffff>
10/01/2008 11:22:03.346 CCM|//SIP/Stack/Info/0x0/ccsip_spi_get_msg_type
returned: 3 for event
28|<CLID::DDNA><NID::10.194.12.215><CT::4,100,78,6.1><IP::><DEV::><LVL::Deta
iled><MASK::40000>
10/01/2008 11:22:03.346 CCM|//SIP/Stack/Info/0xe2130e0/method = 107 state =
7|<CLID::DDNA><NID::10.194.12.215><CT::4,100,78,6.1><IP::><DEV::><LVL::Detai
led><MASK::40000>
10/01/2008 11:22:03.346 CCM|//SIP/Stack/Info/0xe2130e0/Received media sip
event
SIP_REQUEST_ANSWER|<CLID::DDNA><NID::10.194.12.215><CT::4,100,78,6.1><IP::><
DEV::><LVL::Detailed><MASK::40000>
10/01/2008 11:22:03.346 CCM|//SIP/Stack/Error/0xe2130e0/ignoring ACK request
answer|<CLID::DDNA><NID::10.194.12.215><CT::4,100,78,6.1><IP::><DEV::><LVL::
Error><MASK::40000>
10/01/2008 11:22:03.647 CCM| |<CLID::DDNA><NID::10.194.12.215><LVL::State
Transition><MASK::0040>
The next call works:
10/01/2008 11:20:26.384 CCM|(isHeldOrHolding):
er=0,ee=0,mh=0|<CLID::DDNA><NID::10.194.12.215><CT::2,100,78,300.1><IP::><DE
V::><LVL::Detailed><MASK::ffffff>
10/01/2008 11:20:26.384 CCM|getOobScbId: Created scbId. mOobScbId=1159,
ccbId=1158|<CLID::DDNA><NID::10.194.12.215><LVL::Detailed><MASK::ffffff>
10/01/2008 11:20:26.384
CCM|//SIP/SIPCdpc(2,83,528)/ci=43311006/ccbId=1158/scbId=0/setCgpnNumPresent
ation: fIdPresentation is 1 and the SIP Trunk Config is
1|<CLID::DDNA><NID::10.194.12.215><CT::2,100,78,300.1><IP::><DEV::><LVL::Det
ailed><MASK::ffffff>
10/01/2008 11:20:26.384
CCM|//SIP/SIPCdpc(2,83,528)/ci=43311006/ccbId=1158/scbId=0/applyNumPresentat
ionBasedOnDirection: fIdPresentation is 1 and the DialogDirection is 1
|<CLID::DDNA><NID::10.194.12.215><CT::2,100,78,300.1><IP::><DEV::><LVL::Deta
iled><MASK::ffffff>
10/01/2008 11:20:26.384
CCM|//SIP/SIPCdpc(2,83,528)/ci=43311006/ccbId=1158/scbId=0/setCgpnNamePresen
tation: fIdPresentation is 1 SIP Trunk Config is 1
|<CLID::DDNA><NID::10.194.12.215><CT::2,100,78,300.1><IP::><DEV::><LVL::Deta
iled><MASK::ffffff>
10/01/2008 11:20:26.384
CCM|//SIP/SIPCdpc(2,83,528)/ci=43311006/ccbId=1158/scbId=0/applyNamePresenta
tionBasedOnDirection: fIdPresentation is 1
|<CLID::DDNA><NID::10.194.12.215><CT::2,100,78,300.1><IP::><DEV::><LVL::Deta
iled><MASK::ffffff>
10/01/2008 11:20:26.384
CCM|//SIP/SIPCdpc(2,83,528)/ci=43311006/ccbId=1158/scbId=0/setCnNameAndNumbe
r: connectedName Matt Slaga connectedNumber 5712034132 connectedNumberPi 1
connectedNamePi 1 connectedSi
0|<CLID::DDNA><NID::10.194.12.215><CT::2,100,78,300.1><IP::><DEV::><LVL::Det
ailed><MASK::ffffff>
10/01/2008 11:20:26.385 CCM|MediaTerminationPointControl(125) -
MediaExchangeAgenaAssociateReq confId=33638548 inserted
AIF(380901,0)|<CLID::DDNA><NID::10.194.12.215><CT::2,100,167,380901.1><IP::>
<DEV::><LVL::Detailed><MASK::0080>
The second call gets MTP control, but the first gets, well, not sure what it
gets but something different.
Both calls are from the same SIP endpoint.
From: Ryan Ratliff [mailto:rratliff at cisco.com]
Sent: Wednesday, October 01, 2008 4:24 PM
To: Matt Slaga (US)
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Can Cisco UCM Support Multiple MTPs on same call?
Remember MTP != Transcoder (but a transcoder can do some MTP services)
But in general yes, there are some cases where you will end up with an MTP
and transcoder invoked for the same call. Sometimes this is desired
behavior, other times not.
-Ryan
On Oct 1, 2008, at 3:26 PM, Matt Slaga ((US)) wrote:
If I have a call coming in through SIP requiring MTP for codec translation,
can I also have an MTP assigned to transcode?
I.e.,
Incoming call on Direct SIP Trunk to UCM, MTP is required on the trunk.
Call is coming in G711 from SIP trunk, however Cisco UCM side is using G729.
In theory, UCM SIP trunk would negotiate MTP resources required for the SIP
trunk.
Also, UCM call coming from a remote phone or remote voice gateway at G729
would negotiate an MTP resource for transcoding.
_____
Disclaimer: This e-mail communication and any attachments may contain
confidential and privileged information and is for use by the designated
addressee(s) named above only. If you are not the intended addressee, you
are hereby notified that you have received this communication in error and
that any use or reproduction of this email or its contents is strictly
prohibited and may be unlawful. If you have received this communication in
error, please notify us immediately by replying to this message and deleting
it from your computer. Thank you.
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
_____
Disclaimer: This e-mail communication and any attachments may contain
confidential and privileged information and is for use by the designated
addressee(s) named above only. If you are not the intended addressee, you
are hereby notified that you have received this communication in error and
that any use or reproduction of this email or its contents is strictly
prohibited and may be unlawful. If you have received this communication in
error, please notify us immediately by replying to this message and deleting
it from your computer. Thank you.
_____
Disclaimer: This e-mail communication and any attachments may contain
confidential and privileged information and is for use by the designated
addressee(s) named above only. If you are not the intended addressee, you
are hereby notified that you have received this communication in error and
that any use or reproduction of this email or its contents is strictly
prohibited and may be unlawful. If you have received this communication in
error, please notify us immediately by replying to this message and deleting
it from your computer. Thank you.
_____
Disclaimer: This e-mail communication and any attachments may contain
confidential and privileged information and is for use by the designated
addressee(s) named above only. If you are not the intended addressee, you
are hereby notified that you have received this communication in error and
that any use or reproduction of this email or its contents is strictly
prohibited and may be unlawful. If you have received this communication in
error, please notify us immediately by replying to this message and deleting
it from your computer. Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20081008/11ff37c7/attachment-0001.html>
More information about the cisco-voip
mailing list