[cisco-voip] H.323 DTMF to SIP 2833

[Eric Pedersen]

Does the other end of the SIP trunk support KPML?  I'm pretty sure that if you use alphanumeric on the h323 trunk and kpml on the SIP trunk you won't need an MTP.

From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Divin John (dijohn)
Sent: 18 July 2013 2:44 AM
To: Chris Ward (chrward); Mark Holloway
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] H.323 DTMF to SIP 2833

SCCP and SIP Phones support OOB and in band.
CUCM does rtp-nte only out a SIP trunk.
H323 Trunks don't support RFc2833 (inband)
H323 to SIP would need a MTP if you need to convert OOB (h323 side) to rtp-nte/inband (SIP side). CUCM would automatically pick up a MTP for DTMF inter-networking.

Regards,
Divin

From: "Chris Ward (chrward)" <chrward at cisco.com<mailto:chrward at cisco.com>>
Date: Wednesday, 17 July 2013 8:48 PM
To: Mark Holloway <mh at markholloway.com<mailto:mh at markholloway.com>>
Cc: Divin John <dijohn at cisco.com<mailto:dijohn at cisco.com>>, "cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>" <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Subject: RE: [cisco-voip] H.323 DTMF to SIP 2833

Since its in-band, it wouldn't require an MTP... The 2833 would flow as part of the RTP stream.

Adding rtp-nte to the dial peer should remove the need for an MTP if the other leg (from CUCM's perspective at least) is SIP.

+Chris
Unity Connection TME

From: Mark Holloway [mailto:mh at markholloway.com]
Sent: Wednesday, July 17, 2013 11:08 AM
To: Chris Ward (chrward)
Cc: Divin John (dijohn); cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] H.323 DTMF to SIP 2833

Wouldn't this still require MTP?  It looks like he is trying to avoid using MTP for the conversion.

On Jul 17, 2013, at 9:17 AM, Chris Ward (chrward) <chrward at cisco.com<mailto:chrward at cisco.com>> wrote:



CUCM support RFC2833 so long as one of the legs is SIP. An H323 to SIP call through CUCM should allow RFC2833.

+Chris
Unity Connection TME

From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net<mailto:voip-bounces at puck.nether.net>] On Behalf Of Mark Holloway
Sent: Wednesday, July 17, 2013 8:13 AM
To: Divin John (dijohn)
Cc: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] H.323 DTMF to SIP 2833

John is correct, if you're using Alphanumeric on H323 you should be able to use SIP INFO without the need of an MTP. The question is what's on the other end of the SIP Trunk, and will they support SIP INFO?

DTMF interworking between SIP and H.323 in the signaling plane, using the Alphanumeric method
of UserInputIndication


On Jul 16, 2013, at 1:29 PM, Divin John (dijohn) <dijohn at cisco.com<mailto:dijohn at cisco.com>> wrote:




CUCM on the H323 leg doesn't support rfc2833 (rtp-nte).
So, to stop CUCM from invoking an MTP, the SIP side should support Out of band (notify maybe)

Regards,
Divin

From: Nate VanMaren <VanMarenNP at ldschurch.org<mailto:VanMarenNP at ldschurch.org>>
Date: Tuesday, 11 June 2013 1:26 AM
To: "cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>" <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Subject: [cisco-voip] H.323 DTMF to SIP 2833



What H.323 DTMF method can I use on a H.323 dial-peer to CUCM that will not invoke an MTP when the outbound side of CUCM is a SIP Trunk that is configured to use 2833.

I am currently using h245-alphanumeric, which seems to be invoking an MTP.

Thanks,
-Nate


NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip



The contents of this message may contain confidential and/or privileged
subject matter. If this message has been received in error, please contact
the sender and delete all copies. Like other forms of communication,
e-mail communications may be vulnerable to interception by unauthorized
parties. If you do not wish us to communicate with you by e-mail, please
notify us at your earliest convenience. In the absence of such
notification, your consent is assumed. Should you choose to allow us to
communicate by e-mail, we will not take any additional security measures
(such as encryption) unless specifically requested.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20130719/8235d44d/attachment.html>