[cisco-voip] Cell Phone Call Treatment Different than Landline

[Matthew Saskin]

My guess is that something from the ISDN side of things (information
element, etc.) isn't getting properly translated and is causing issues once
the call routes to EUM via SIP.

1 - When external calls to EUM fail (either don't route or get dropped) any
error log messages on the exchange UM server(s)?
2 - Can you get a q931 debug from the gateway side of things for working and
non-working calls?
3 - Can you get CallManager SIP traces for the working and non-working calls
to EUM?

Matthew Saskin
msaskin at gmail.com
203-253-9571

July 18, 2010 - 1500m swim (in the hudson), 40k bike, 10k run
Please support the Leukemia & Lyphoma Society
http://pages.teamintraining.org/nyc/nyctri10/msaskin


On Tue, Apr 27, 2010 at 12:40 PM, Tkachuk,Birni <birnit at nait.ca> wrote:

>  We have a campus set up in a different city than our Call Manager
> (version 6.1.4) with a Voice Router and PRI Service for local calling.  We
> have Microsoft Exchange Unified Messaging for all of our staff which works
> great except at this remote campus.  When a cell phone call is received the
> call is routed to Exchange voicemail after 4 rings or on a busy.  When a
> landline call is received it will ring no answer but never route to
> voicemail.  If we call forward the phone line to voicemail the landline
> caller will hear a fast busy but the cell phone caller will go immediately
> to the voicemail.  Why would a cell phone receive different call treatment
> than a landline?
>
>
>
> Birni Tkachuk
>
> Network Services
>
> Department of Information Services
>
> NAIT
>
> 11762 - 106 Street NW
>
> Edmonton, Alberta  T5G 2R1
>
> P 780.471.7532  F 780.491.3083  E birnit at nait.ca
>
> *www.nait.ca*
>
>
>
> _______________________________________________
> 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/20100427/82197140/attachment.html>