It's just a extra css. But not "just" because it can be used in a very nice way.
The 2 CSS fields add up. So what cannot be found in the line CSS will be looked up in the device CSS.
For example where i use it for is emergency calls. In the Netherlands you need to send a code with a area code in it so the emergency call is routed to the right emergency centre. (normaly the provider arange this, but in this case i'm the provider )
So when you use exention mobility you can set the emergency calls to the CSS of the device in this case no matter where you are the calls emergency calls are always routed to the right emegency centre.
The one specified on the device becomes the default for any DNs on that phone. If a CSS is specified within the DN, then that is used over the phone's CSS.
For example, we assign a restricted CSS on the visitor phones used by Extension Mobility users. If nobody is logged in, the phone is restricted. When an Extension Mobility user logs in, the less restricted CSS of the Extension Mobility's DN is used and allows the user to make long distance calls.
Our company assigns it by the device. That way we can control permission level based on the device itself and not the extension (assuming it's shared over multiple devices). You can pretty much go either way as long as one of them has the CSS, calls will go out.
Take a look in the SRND guide on Cisco's site and read about the device/line calling plan. A very useful function of the 2 CSS is with device mobility. The CSS on the phone will update depending on where the phone is physically located but the CSS on the line will always be the same. So the idea is you put the Calling capabilities on the device CSS and the restrictions on the line CSS. Calling pattern selection is ALWAYS best match but if there is a tie the line CSS takes priority so the blocking pattern on the line will restrict the call but if there is not a blocking pattern in the line CSS the routing pattern in the device CSS will send the call out the best path for that location. If a phone moves from campus x to campus y the routing patterns will automatically update to the new campus for optimum routing since it always in the device CSS.
The SRND does a much better job of explaining it than me
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.