<div><font face="arial,helvetica,sans-serif">My ISP is able to set the DTMF to</font>:</div>
<div>
<p style="MARGIN: 0in 0in 0pt" class="MsoPlainText"><font face="arial,helvetica,sans-serif">- SIP INFO;</font></p>
<p style="MARGIN: 0in 0in 0pt" class="MsoPlainText"><font face="arial,helvetica,sans-serif">- SIP NOTIFY;</font></p>
<p style="MARGIN: 0in 0in 0pt" class="MsoPlainText"><font face="arial,helvetica,sans-serif">- RFC2833 (payload type 101);</font></p>
<p style="MARGIN: 0in 0in 0pt" class="MsoPlainText"><font face="arial,helvetica,sans-serif"></font> </p>
<p style="MARGIN: 0in 0in 0pt" class="MsoPlainText"><font face="arial,helvetica,sans-serif">If my ISP sets it to RFC2833 the CUCM should accept it right?</font></p><br><br></div>
<div class="gmail_quote">2010/7/13 Matt Slaga (US) <span dir="ltr"><<a href="mailto:Matt.Slaga@us.didata.com">Matt.Slaga@us.didata.com</a>></span><br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">If you are not using a cube, you might need an enhanced IOS software MTP termination point which will allow the capturing of DTMF packets inband and process them out of band. These can run as software MTPs on the gateway (cannot use the UCM built in software MTPs for this purpose).<br>
<br>________________________________________<br>From: <a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a> [<a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>] On Behalf Of Nick Matthews [<a href="mailto:matthnick@gmail.com">matthnick@gmail.com</a>]<br>
Sent: Tuesday, July 13, 2010 11:38 AM<br>To: Mark Holloway<br>Cc: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>; Paul van den IJssel<br>Subject: Re: [cisco-voip] SIP Trunk from ISP DTMF issue<br>
<div>
<div></div>
<div class="h5"><br>Also check the ccn subsystem sip on the CUE - make sure you're<br>configured for the DTMF method you're using everywhere else. Plus use<br>a CUBE as stated.<br><br>-nick<br><br>On Tue, Jul 13, 2010 at 11:17 AM, Mark Holloway <<a href="mailto:mh@markholloway.com">mh@markholloway.com</a>> wrote:<br>
> The Genband is probably doing the same thing that CUBE would be doing. What<br>> are the DTMF requirements from your provider? Have you confirmed that DTMF<br>> is being passed to the provider? A Wireshark capture on the public side of<br>
> the S3 would verify DTMF is being passed.<br>> On Jul 13, 2010, at 7:58 AM, Bill wrote:<br>><br>> You should not trunk directly to CUCM from your ITSP. You need to go through<br>> a CUBE router. Terminate the ITSP on the CUBE and then do a SIP trunk to<br>
> your CUBE router.<br>><br>> ________________________________<br>> From: <a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a> [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>] On<br>
> Behalf Of Paul van den IJssel<br>> Sent: Tuesday, July 13, 2010 9:54 AM<br>> To: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>> Subject: [cisco-voip] SIP Trunk from ISP DTMF issue<br>
><br>> Hi all,<br>><br>> Currently I'm running a acceptance test on a SIP Trunk from our ISP.<br>> Everything is working fine except the DTMF.<br>><br>> Setup:<br>> [GenBand SBC] ---- [SIP Trunk into CUCM 7.1] ---- [Cisco Unity Express 7.0]<br>
><br>> The SIP Trunk as well as the CUE are in the same region supporting only<br>> G.711. On the SIP Trunk I've tried all different kind of DTMF configurations<br>> (No Preference, RFC 2833 and OOB). We've tried to force the GenBand SBC to<br>
> only use RFC 2833 as well as the SIP Trunk. But this didn't work, not even<br>> after we added a MRGL with MTP's.<br>><br>> Is there some sort of best practive to implement DTMF over a SIP Trunk? Is<br>
> there a way I can do some debugging on the CUCM/CUE?<br>><br>> Kind regards,<br>><br>> Paul van den IJssel<br>> Digacom<br>> _______________________________________________<br>> cisco-voip mailing list<br>
> <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
><br>><br>> _______________________________________________<br>> cisco-voip mailing list<br>> <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
><br>><br><br>_______________________________________________<br>cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br></div></div>-----------------------------------------<br>Disclaimer:<br><br>This e-mail communication and any attachments may contain<br>confidential and privileged information and is for use by the<br>designated addressee(s) named above only. If you are not the<br>
intended addressee, you are hereby notified that you have received<br>this communication in error and that any use or reproduction of<br>this email or its contents is strictly prohibited and may be<br>unlawful. If you have received this communication in error, please<br>
notify us immediately by replying to this message and deleting it<br>from your computer. Thank you.<br></blockquote></div><br>