[cisco-voip] Transcoding issue

[Peter Slow]

Tim,
  Did you ever figure this out?

On Tue, Apr 13, 2010 at 11:33 AM, Chris Ward (chrward) <chrward at cisco.com>wrote:

>  Tim,
>
>
>
> In this type of situation, I always like to put a device like a PC or
> anything with ping capabilities in one of the voice vlans from the call flow
> and then ping to a phone at the opposite end of the call flow. This will
> ensure that IP connectivity (routing) is working.
>
>
>
> You probably aren’t using a transcoder for an IP Phone to IP Phone call.
> Regardless of them being on different cluster unless there is DTMF mismatch
> or fast start being used. You can check by setting up the call with no audio
> and then checking the IP Phone web pages to see where the streams are being
> sent. That will show use where other potential issues may lie.
>
>
>
> +Chris
>
>
>
> *From:* cisco-voip-bounces at puck.nether.net [mailto:
> cisco-voip-bounces at puck.nether.net] *On Behalf Of *H, Tim
> *Sent:* Tuesday, April 13, 2010 11:20 AM
> *To:* cisco-voip at puck-nether.net
> *Subject:* [cisco-voip] Transcoding issue
>
>
>
> I have a remote site on a separate CUCM cluster than another remote site.
> They can dial each other and the call will connect, but they then cannot
> hear each other.
>
>
>
> I have other sites on the same CUCM cluster and can talk to the other
> remote sites with no issues.
>
>
>
> I have a feeling it’s a transcoding issue.  Any other ideas?
>
>
>
>
>
> *Tim ***
>
>
>
> _______________________________________________
> 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/20100414/25b3ba23/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 21602 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20100414/25b3ba23/attachment.png>