http://www.dslreports.com/forum/r22639935 en Sat, 05 Dec 2009 08:56:56 EDT Sat, 05 Dec 2009 08:56:56 EDT http://www.dslreports.com/forum/remark,22639935 rsaturns : I have a question I might already know the answer to but would like a logic check. What I’m trying to accomplish is the following. We are going to implement extension mobility on all our phones due to the fact people move between locations on the frequent basis. A challenge of this would be accurate 911 information, in an effort to avoid the E911 server I’m attempting the following:

Say a user DN has a separate CSS from the device:

User-CSS
Device-CSS

User-CSS contains a route pattern of 9.@ with a route filter of (SERVICE EXISTS) and the pattern is set to block. This would effectively stop the user from being able to dial 9.911 / 911.

Device-CSS would contain a 9.@ route patter without the route filter applied so from the device CSS standpoint you could dial 9.911 / 911.

Now it’s my understanding that if a user CSS does not have a matching route pattern the CUCM server will then check the device CSS and if it’s finds a match use it.

Now by that logic since my 9.@ route patter with the route filter applied would match the CUCM would block the pattern.

So I guess my question is in order to rely on the device for the 9.911 / 911 pattern match I’d have to do away with the 9.@ route pattern in the user CSS. Is this correct?

The end goal here would be that no matter what location the user loads their profile at the 911 / 9.911 match will occur on the device and go out the local gateway verses the users CSS gateway.

Also if there is a better way to approach this please let me know.

Thanks
--
»vinfotech.blogspot.com]]> http://www.dslreports.com/forum/remark,22639935 Wed, 01 Jul 2009 13:55:41 EDT