[cisco-voip] SIP Trunk for ISP's - DTMF SIP Notify

[Ryan Ratliff]

And remember that support for 2833 isn't going to be in the header, it's going to be in the SDP with other media information.

Even 7960s support RFC2833 so I'm very confident the 7941 and 7961s do.

-Ryan

On Jun 2, 2010, at 9:45 AM, Nick Matthews wrote:

> Cisco has a 'receive but not send' policy on INFO messages.  The
> powers that be have determined that the SIP INFO message is too vague
> and have reduced support for it.
> 
> SIP NOTIFY is the more likely candidate, or KPML.  RFC 2833 is still
> the standard when it comes to SIP.
> 
> 
> -nick
> 
> On Wed, Jun 2, 2010 at 2:54 AM, Paul van den IJssel <pijssel at gmail.com> wrote:
>> Guys,
>> 
>> What do you suggest me to use: SIP INFO or SIP NOTIFY?
>> 
>> - Paul
>> 
>> 2010/6/1 Bill <bill at hitechconnection.net>
>>> 
>>> No VMware is not your problem in this case.
>>> 
>>> 
>>> 
>>> ________________________________
>>> 
>>> 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, June 01, 2010 4:06 PM
>>> To: cisco-voip at puck.nether.net
>>> Subject: Re: [cisco-voip] SIP Trunk for ISP's - DTMF SIP Notify
>>> 
>>> 
>>> 
>>> I added a MRGL to the both DP's (phones and SIP Trunk) containing MoH,
>>> CFB, ANN and MTP. But without any result. I'm running the CUCM in Vmware..
>>> could this have anything to do with the MTP's not be assigned when needed
>>> for the DTMF?
>>> 
>>> 
>>> 
>>> - Paul
>>> 
>>> 2010/6/1 Jason Aarons (US) <jason.aarons at us.didata.com>
>>> 
>>> Use the CallManager or IOS Software MTP in a MRG/MRGL and assign to Device
>>> Pool, etc is what I think others are saying…
>>> 
>>> 
>>> 
>>> 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, June 01, 2010 4:53 PM
>>> To: cisco-voip at puck.nether.net
>>> Subject: Re: [cisco-voip] SIP Trunk for ISP's - DTMF SIP Notify
>>> 
>>> 
>>> 
>>> The SIP Trunk is directly connected to the CUCM (7.X). So there is no ISR,
>>> or CUBE in between.
>>> 
>>> The System Guide of CUCM 7.X states that only the 7971 7975 support
>>> RFC2833. Currently I'm running the test with 7941 and 7961 phones. Also all
>>> regions are set to use g.711 and there is no MRGL associated to the Device
>>> Pools of the phones and the SIP Trunk.
>>> 
>>> 
>>> 
>>> If I try setting up a call and run the RTMT tool I don't see the CUCM
>>> using any MTP's. The SBC which is used isn't a Cisco CUBE.. but I've lost
>>> the name, I thought it was a NextTone or something.
>>> 
>>> 
>>> 
>>> - Paul
>>> 
>>> 2010/6/1 Ryan Ratliff <rratliff at cisco.com>
>>> 
>>> What phones do you have?  Most of them do in fact support RFC2833.
>>> Additionally, using g.711 for rtp the software MTP resources on your CUCM
>>> can convert the dtmf just fine.
>>> 
>>> Even if you are using g729 you can use a software MTP on the router acting
>>> as your CUBE to do the necessary dtmf conversion which doesn't require any
>>> hardware DSPs.
>>> 
>>> -Ryan
>>> 
>>> On Jun 1, 2010, at 4:34 PM, Paul van den IJssel wrote:
>>> 
>>>> Hi Guys,
>>>> 
>>>> Currently I'm testing a SIP Trunk with our ISP. Everything is working
>>>> fine but I don't get the DTMF to work. This because my SCCP phones only
>>>> support OOB DTMF. So to get it to work with SIP RFC2833 (in-band) I need an
>>>> expensive transcoder. But now we've set the SIP Trunk to SIP Notify
>>>> (out-band) which should work with the IP Phones OOB, but all I get is
>>>> 'SIP/2.0 403 Forbidden'.
>>>> 
>>>> How do I get this to work without the use of a hardware Transcoder?
>>>> 
>>>> Best regards,
>>>> 
>>>> Paul van den IJssel
>>>> Digacom
>>> 
>>>> _______________________________________________
>>>> 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.
>>> 
>>> 
>> 
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>> 
>> 
> 
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip