Ding ding ding! Winner! I wonder why Cisco doesn't update the CUCM UI. I was looking for DTMF support in a Telepresence Admin Guide for like an SX20 or something, and I couldn't find RFC2833 mentioned anywhere, but it did mention RFC4733. Anyway, that's all the trivia I have for now.
On Fri, Apr 24, 2020 at 10:17 AM Ryan Huff <ryanh...@outlook.com> wrote: > RCF 4733, I believe. > > Sent from my iPhone > > On Apr 24, 2020, at 10:58, Anthony Holloway < > avholloway+cisco-v...@gmail.com> wrote: > > > Actually you don't want to set rfc2833 (pop quiz: rfc2833 is not the real > RFC number. What's the real RFC number? Don't google it, but reply if you > know!) on your CUCM SIP Trunk to CUBE. You want No Preference. It's a > setting right on the SIP Trunk, just scroll to the bottom of the settings > page. Also, on your CUBE dial-peers you don't want solely rtp-nte either, > you want both rtp-nte and at least one Out of Band (OOB) option, like > sip-kpml or sip-notify (thought the latter requires a SIP Trunk Security > Profile change from default to allow unsolicited NOTIFY). > > > On Fri, Apr 24, 2020 at 9:35 AM Hamu Ebiso <hebiso2...@hotmail.com> wrote: > >> Thank you Jason for your questions. how can you setup rfc2833 In CUCM >> trunks? >> >> thanks >> >> ------------------------------ >> *From:* Jason Aarons <scubajas...@gmail.com> >> *Sent:* Friday, April 24, 2020 8:24 AM >> *To:* Hamu Ebiso <hebiso2...@hotmail.com> >> *Cc:* cisco-voip <cisco-voip@puck.nether.net> >> *Subject:* Re: [cisco-voip] Ported Numbers to SIP call handler transfer >> is not working correctly. >> >> I am doubtful porting had anything to do with it. Was it tested fully >> before the port? >> >> Under dial peers is dtmf-relay rtp-nte set? In CUCM trunks is rfc2833 >> set? How is Unity integrated with CUCM ? SIP? CXN Version? >> >> Without some debugs /traces I suspect you won't find much. >> >> On Thu, Apr 23, 2020, 3:52 PM Hamu Ebiso <hebiso2...@hotmail.com> wrote: >> >> Hello team, >> >> I hope someone have come across this issue and can help me. We ported our >> numbers to SIP yesterday. Now, their main menu is not transferring numbers >> correctly. For example, when you select classifieds, it is supposed to go >> to the LAC Classifieds call handler. Selecting option 1 is not routing >> correctly. Calling the LAC numbers directly works. >> What do you think might be causing this issue? >> >> Thanks >> Hamu >> _______________________________________________ >> cisco-voip mailing list >> cisco-voip@puck.nether.net >> https://puck.nether.net/mailman/listinfo/cisco-voip >> <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip&data=02%7C01%7C%7Ccdf3f9636d86481fa96008d7e85fef7a%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637233371061347722&sdata=gQIs%2FfMD6wh1OiGlmZSljaGRaZwpL9ioN8Zltc%2BbBB0%3D&reserved=0> >> >> _______________________________________________ >> cisco-voip mailing list >> cisco-voip@puck.nether.net >> https://puck.nether.net/mailman/listinfo/cisco-voip >> <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip&data=02%7C01%7C%7Ccdf3f9636d86481fa96008d7e85fef7a%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637233371061347722&sdata=gQIs%2FfMD6wh1OiGlmZSljaGRaZwpL9ioN8Zltc%2BbBB0%3D&reserved=0> >> > _______________________________________________ > cisco-voip mailing list > cisco-voip@puck.nether.net > > https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip&data=02%7C01%7C%7Ccdf3f9636d86481fa96008d7e85fef7a%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637233371061367711&sdata=bYdGNM%2Fs795%2FjAJ%2FZFcXDZ41QJTGykNajY6IDAmSJeE%3D&reserved=0 > >
_______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip