[cisco-voip] EM number reachability

[Kalle Tetto]

I don't think so, for CFNA I have a forward to voicemail. The other 
thing is, that if the user is logged into em, the QSIG trunk is away, 
because, this is for an RD case.

All the best

Jonathan Charles schrieb:
> The problem is that if the phone is registered and the user is just away 
> from their desk, it will CFNA to the QSIG trunk... even though you may 
> want it to go to vmail...
> 
> 
> 
> Jonathan
> 
> On 3/21/07, *Kalle Tetto* <tettokalle at hotmail.com 
> <mailto:tettokalle at hotmail.com>> wrote:
> 
>     Like you told me, I created an CSS_CF-QSIG, which contains the route
>     patterns. Then I inserted all Device Profiles, with BAT. For using BAT,
>     I created a default device profile, which has 0XXX as forward to pattern
>     for unregistered devices.
> 
>     Works great, but not easy to configure, because you have to touch every
>     em profile and not doing the normal route pattern, CSS stuff.
> 
>     Many thanks again.
> 
>     cheers
> 
>     Jonathan Charles schrieb:
>      > How did you configure it?
>      >
>      >
>      > Jonathan
>      >
>      > On 3/21/07, *Kalle Tetto* <tettokalle at hotmail.com
>     <mailto:tettokalle at hotmail.com>
>      > <mailto: tettokalle at hotmail.com <mailto:tettokalle at hotmail.com>>>
>     wrote:
>      >
>      >     Thanks alot,
>      >
>      >     I tried this tonight by myself and it is working, a little bit
>      >     difficult
>      >     to configure, but it works.
>      >
>      >     All the best
>      >
>      >     Jonathan Charles schrieb:
>      >      > Here's your problem.
>      >      >
>      >      > Yes, longest match wins. However, when a phone is
>     unregistered, it is
>      >      > still in the system and calls will go to the CFNA setting.
>      >      >
>      >      > So, you need to install CCM 4.2 and use CFUR to point to
>     the QSIG
>      >     trunk...
>      >      >
>      >      >
>      >      >
>      >      > Jonathan
>      >      >
>      >      > On 3/20/07, *Kalle Tetto* <tettokalle at hotmail.com
>     <mailto:tettokalle at hotmail.com>
>      >     <mailto: tettokalle at hotmail.com <mailto:tettokalle at hotmail.com>>
>      >      > <mailto:tettokalle at hotmail.com
>     <mailto:tettokalle at hotmail.com> <mailto:tettokalle at hotmail.com
>     <mailto:tettokalle at hotmail.com>>>>
>      >     wrote:
>      >      >
>      >      >     Hi all,
>      >      >
>      >      >     I'm looking for a solution for the reachability of
>     Extension
>      >     Mobility
>      >      >     numbers. Actually I have a route pattern 01XX which
>     should
>      >     route all
>      >      >     number to an qsig trunk. If now a user is logged in
>     with an
>      >     extension
>      >      >     mobility number of 0111 he should reachable on the
>     phone he
>      >     is logged
>      >      >     in. If he is not logged in the call should go as normal to
>      >     the qisg
>      >      >     trunk. Do you have any idea how to solve it?
>      >      >
>      >      >     Is it correct, that the longest match rule always
>     choose the
>      >     Em line
>      >      >     and
>      >      >     then the qsiq, or can this solved by using css so that the
>      >     route list
>      >      >     appears first.
>      >      >
>      >      >     Many thanks
>      >      >
>      >      >     Kalle
>      >      >
>      >      >     _______________________________________________
>      >      >     cisco-voip mailing list
>      >      >     cisco-voip at puck.nether.net
>     <mailto:cisco-voip at puck.nether.net>
>      >     <mailto:cisco-voip at puck.nether.net
>     <mailto:cisco-voip at puck.nether.net>>
>      >     <mailto:cisco-voip at puck.nether.net
>     <mailto:cisco-voip at puck.nether.net>
>     <mailto:cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net>>>
>      >      >     https://puck.nether.net/mailman/listinfo/cisco-voip
>     <https://puck.nether.net/mailman/listinfo/cisco-voip>
>      >      >
>      >      >
>      >      >
>      >      >
>      >    
>     ------------------------------------------------------------------------
>      >
>      >      >
>      >      > _______________________________________________
>      >      > cisco-voip mailing list
>      >      > cisco-voip at puck.nether.net
>     <mailto:cisco-voip at puck.nether.net>
>     <mailto:cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net> >
>      >      > https://puck.nether.net/mailman/listinfo/cisco-voip
>      >
>      >     _______________________________________________
>      >     cisco-voip mailing list
>      >     cisco-voip at puck.nether.net
>     <mailto:cisco-voip at puck.nether.net>
>     <mailto:cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net>>
>      >     https://puck.nether.net/mailman/listinfo/cisco-voip
>      >
>      >
>      >
>      >
>     ------------------------------------------------------------------------
>      >
>      > _______________________________________________
>      > cisco-voip mailing list
>      > cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net>
>      > https://puck.nether.net/mailman/listinfo/cisco-voip
>     <https://puck.nether.net/mailman/listinfo/cisco-voip>
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip