[cisco-voip] fast tone

Jonathan Charles jonvoip at gmail.com
Fri Feb 16 09:00:35 EST 2007


It depends what kind of call it is...

If it is an outbound call to a PRI, the the PRI could be in use (all 23
channels have a call on them)... if it is a WAN call, you could be out of
locations bandwidth (you should see a message on the phone), it could be to
a phone that is unregistered (WAN bounce)...

There are almost too many reasons to list...

You need to determine where the call was to and when... and get a CCM trace
and find out why CCM issued the reorder tone.



Jonathanq

On 2/16/07, kevin k <kds850 at gmail.com> wrote:
>
> today and many times before i had users complain they get fast tone.  they
> dial number and get the fast tone.  it seems to be only for outgoing call.
> to be sure i advised them to write down time and called number.
>
> what is causing that?
>
> per "cisco callmanager fundamental", read below.
>
> if it is bandwidth issue, which bandwidth?
> phone to vg?
> vg to pri?
>
> how can i see it?
>
> thanks guys in advance.
>
>
>
> Like IP precedence, regions play an important role in ensuring the quality
> of voice calls within your network. Regions allow you to constrain the
> codecs selected when one device calls another. Most often, you use regions
> to limit the bandwidth used when calls are placed between devices connected
> by an IP WAN. However, you can also use regions as a way of providing higher
> voice quality at the expense of network bandwidth for a preferred class of
> users.
>
> When you define a new region, Cisco CallManager Administration asks you to
> define the compression type used for calls between devices within the
> region. You also define, on a region-by-region basis, compression types used
> for calls between the region you are creating and all other regions.
>
> You associate regions with device pools. All devices contained in a given
> device pool belong to the region associated with that device pool. When an
> endpoint in one device pool calls an endpoint in another, the codec used is
> constrained to what is defined in the region. If, for some reason, one of
> the endpoints in the call cannot encode the voice stream according to the
> specified codec, CallManager attempts to introduce a transcoder (see Chapter
> 5) to allow the endpoints to communicate."
>
> _______________________________________________
> 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/20070216/f5732adc/attachment-0001.html 


More information about the cisco-voip mailing list