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

[Mark Holloway]

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> 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] On Behalf Of Mark Holloway
> Sent: Wednesday, July 17, 2013 8:13 AM
> To: Divin John (dijohn)
> Cc: 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> 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>
> Date: Tuesday, 11 June 2013 1:26 AM
> To: "cisco-voip at puck.nether.net" <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
> https://puck.nether.net/mailman/listinfo/cisco-voip
>  

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20130717/7cee6058/attachment.html>