[cisco-voip] transcoding from g711 to g729 with CME

[Hinson, Greg]

i ran "show sdspfarm units" and the dspfarm does show registered with
the MAC associated with the sccp interface I am bound to, and that also
matches what I configured in telephony service. a "show sdspfarm
sessions" shows the correct number of allocated streams configured in
telephony-service, all of which are idle.

As far as dialing the pilot directly, here's what I discovered. In
12.4.3 IOS, the virtual efxs devices in CME auto-register to the
gatekeeper so I didn't have to predefine them. That allowed calls from
CCM to CME to work. I am also using a default-technology prefix to route
calls the opposite direction to CCM from CME, which also works great for
this application(small scale-1 GK & CCM cluster). Since the gatekeeper
doesn't know about my pilot point for CUE, I predefined a gw-type prefix
in the gatekeeper and hard-coded the CME router's ip address for its
destination. I also created a route pattern for the CUE pilot point in
callmanager that points to the h225-gatekeeper controlled trunk. the
call still fails with a fast busy, but at least I know its getting out
of ccm, through the gatekeeper intact, and over to CUE, as it matches
the same outbound dial-peer that a local CME phone matches when going to
voicemail.

-Greg

-----Original Message-----
From: Ted Nugent [mailto:tednugent69 at yahoo.com] 
Sent: Friday, August 04, 2006 9:42 PM
To: Hinson, Greg; cisco-voip at puck.nether.net
Subject: RE: [cisco-voip] transcoding from g711 to g729 with CME

Exact same issue I faced... Oringally I had my codec
voice class to allow g711 and g729. As soon as I
pulled out g711 it worked fine. If you do sho sdspfarm
stat and sess does it sho all is registerd fine then?
Do you get the same issue if you call the pilot
direct?

--- "Hinson, Greg" <Greg_Hinson at adp.com> wrote:

> thanks for the reply. debug voip dial-peer does show
> the right dial-peer
> matches. The WAN is forced to codec 729, as well as
> the sip dial-peer
> for unity forced to g711ulaw. I also added
> transfer-pattern .T to
> telephony-service. cme phone to cme phone cfa to VM
> always works great,
> as well as enterprise to cme if the codecs are
> forced to g711ulaw
> end-to-end. it only fails when g729 is added to the
> region and wan
> dial-peers. also, when i run debug dspfarm, I see no
> activity on the
> output during the attempt, as if the CME's Media
> Resource Manager is not
> even being called to provide transcoding.
> 
> -Greg
> 
> 
> -----Original Message-----
> From: Ted Nugent [mailto:tednugent69 at yahoo.com] 
> Sent: Friday, August 04, 2006 8:12 PM
> To: Hinson, Greg; cisco-voip at puck.nether.net
> Subject: Re: [cisco-voip] transcoding from g711 to
> g729 with CME
> 
> Yes, I've had the exact same problem and finally
> figured it out.
> First of make sure your matching your inbound (from
> WAN) and outbound (to CUE) DPs... (debug voip
> dialpeer
> all). If not make sure your translation rules are
> right or tranfer-pattern .T is added in tel-serv.
> Most
> importantly make sure you lock in your WAN DP to
> G729... if you use a voice class with G711 it will
> never work even if G729 is prefered first.
> 
> 
> HTH
> Ted
> 
> 
> --- "Hinson, Greg" <Greg_Hinson at adp.com> wrote:
> 
> > I have a client that is using CME at a remote
> store
> > and Enterprise
> > CallManager at the host location. I have regions
> > setup, forcing the
> > calls destined for the remote location to g729.
> The
> > CME hardware is a
> > 2821 platform running 12.3.14T7 spservices IOS
> with
> > an NM-CUE module.
> > Using a gatekeeper to interconnect the two
> > callmanagers, I can
> > successfully negotiate a g729 call across the
> > network, but on a CME
> > call-forward-no answer condition to Unity Express,
> > the call drops with a
> > fast busy. I followed the guidelines referenced in
> > the doc below for
> > creating a dspfarm/sccp profiles and its
> assignment
> > to
> > telephony-service, but with no success. I also
> > upgraded the IOS to
> > 12.4.3, thinking it was an incompatibility issue
> > with 12.3.14, and I
> > have the same problem.  Any ideas?
> >  
> >  
> >
>
http://www.cisco.com/en/US/partner/products/sw/iosswrel/ps5207/products_
> > feature_guide_chapter09186a00802d255d.html
> >  
> >  
> >  
> > -Greg
> >  
> > 
> > 
> > This message and any attachments are intended only
> > for the use of the addressee and may contain
> > information that is privileged and confidential.
> If
> > the reader of the message is not the intended
> > recipient or an authorized representative of the
> > intended recipient, you are hereby notified that
> any
> > dissemination of this communication is strictly
> > prohibited. If you have received this
> communication
> > in error, please notify us immediately by e-mail
> and
> > delete the message and any attachments from your
> > system.
> > > _______________________________________________
> > cisco-voip mailing list
> > cisco-voip at puck.nether.net
> >
> https://puck.nether.net/mailman/listinfo/cisco-voip
> > 
> 
> 
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam
> protection around 
> http://mail.yahoo.com 
> 
> 
> This message and any attachments are intended only
> for the use of the addressee and may contain
> information that is privileged and confidential. If
> the reader of the message is not the intended
> recipient or an authorized representative of the
> intended recipient, you are hereby notified that any
> dissemination of this communication is strictly
> prohibited. If you have received this communication
> in error, please notify us immediately by e-mail and
> delete the message and any attachments from your
> system.
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 


This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.