[cisco-voip] SIP Trunk from ISP DTMF issue

[Mark Holloway]

The Genband is probably doing the same thing that CUBE would be doing.  What are the DTMF requirements from your provider?  Have you confirmed that DTMF is being passed to the provider?  A Wireshark capture on the public side of the S3 would verify DTMF is being passed.

On Jul 13, 2010, at 7:58 AM, Bill wrote:

> You should not trunk directly to CUCM from your ITSP. You need to go through a CUBE router. Terminate the ITSP on the CUBE and then do a SIP trunk to your CUBE router.
>  
> From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Paul van den IJssel
> Sent: Tuesday, July 13, 2010 9:54 AM
> To: cisco-voip at puck.nether.net
> Subject: [cisco-voip] SIP Trunk from ISP DTMF issue
>  
> Hi all,
>  
> Currently I'm running a acceptance test on a SIP Trunk from our ISP. Everything is working fine except the DTMF.
>  
> Setup:
> [GenBand SBC] ---- [SIP Trunk into CUCM 7.1] ---- [Cisco Unity Express 7.0]
>  
> The SIP Trunk as well as the CUE are in the same region supporting only G.711. On the SIP Trunk I've tried all different kind of DTMF configurations (No Preference, RFC 2833 and OOB). We've tried to force the GenBand SBC to only use RFC 2833 as well as the SIP Trunk. But this didn't work, not even after we added a MRGL with MTP's.
>  
> Is there some sort of best practive to implement DTMF over a SIP Trunk? Is there a way I can do some debugging on the CUCM/CUE?
>  
> Kind regards,
>  
> Paul van den IJssel
> Digacom
> _______________________________________________
> 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/20100713/eabcf4a2/attachment.html>