What are you trying to accomplish with the MTP that can't already be accomplished with media flow-through and dtmf-relay?
On Mon, Mar 30, 2015 at 12:38 PM, Anthony Holloway < avholloway+cisco-v...@gmail.com> wrote: > All, > > I know the name itself, LTI, includes the word transcoding, but I'm just > double checking that this will or will not work for registering an MTP on > the CUBE. All roads are leading me to the answer, but it just seems like a > huge miss on Cisco's part to not allow us to register MTPs as well as XCODE > via the LTI method. > > This works for me: > dspfarm profile 1 transcode > codec g711ulaw > codec g729ar8 > max sessions 1 > assoc app cube > no shut > ! > > This does not work for me (it hangs on associating to cube app): > dapfarm profile 2 mtp > codec g711ulaw > max sessions software 1 > assoc app cube > no shut > ! > > I have the required dspfarm and mode border-element commands, and rebooted > after as well. > > Seems like with the standard requirement of rfc2833 on SIP trunks to the > ITPS, and CTI apps in the network (I'm looking at you UCCX), MTPs play a > large role in the success of SIP trunking for customers, and yet I cannot > even register them locally with the LTI. > > I do have a fallback plan, so I'm not stuck. I'm just looking for the > optimal design scenario. In my order of preference I would like to go: > > 1. LTI > 2. SCCP via Telephony Service > 3. SCCP via CUCM > > Would you rank them differently? > > Thanks for your input in advance. > > _______________________________________________ > cisco-voip mailing list > cisco-voip@puck.nether.net > https://puck.nether.net/mailman/listinfo/cisco-voip > >
_______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip