cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1053
Views
0
Helpful
4
Replies

Extension mobility: same DN with different partition login/logout version 12.0

jaheshkhan
Level 4
Level 4

I have a situation for the customer. .

They need same DN number for login and logout condition condition but different privilage.

when they login they should be able call external calls. in logout condition only internal and emergency numbers are allowed.

 

let it be like this say extension 152.

152 assigned with partition internal-PT for internal calls. and its css will be internal-CSS.

same number will be used if the user logged with extension mobility.

ie 152 assingned with partition login-PT for login condition. its for external calls. say here mobile-CSS.

 

line is PRI line and gateway is MGCP gateway.

In MGCP gateway, for inbound call I assigned CSS as  internal-CSS. internal-CSS has both internal-PT and login-PT partition.

 

internal-CSS =  internal-PT

                         login-PT

 

This is the order of partition

My issue is that whenever somebody calling from public network to this extension it never reaches to phone extension while it is in logged in condition. otherwise it work fine without any issue.

 

We have CUCM 12.0.

 

Also suppose if Both login and logout are  available in 2 different phones, if somebody call to 152 only logout number 152 will ring. i want both to ring?

 

Why its like that?

1 Accepted Solution

Accepted Solutions

I managed to get this work for 2 different customers.

It does take some thinking though.

 

So the process goes like this.;

(1) create different css for gateway inbound calls, login-pt dns, logout-pt dns

(2) give login-pt higher priority on css-gateway-inbound

Give login-pt higher priority than logout-pt in css-logout

Give only logout-pt access to css-login

(3) on dn 152_login_pt, create call-fw not registered to 152 (css_logout)

(4) make both DNs member of same pickup group

(5) if you use hunting, make both members of the same line group

HTH

View solution in original post

4 Replies 4

Jaime Valencia
Cisco Employee
Cisco Employee

No way you get them both to ring unless you use a line group, as there are two equally good matches in the CSS, then the partition that comes on top will be chosen.

HTH

java

if this helps, please rate

I managed to get this work for 2 different customers.

It does take some thinking though.

 

So the process goes like this.;

(1) create different css for gateway inbound calls, login-pt dns, logout-pt dns

(2) give login-pt higher priority on css-gateway-inbound

Give login-pt higher priority than logout-pt in css-logout

Give only logout-pt access to css-login

(3) on dn 152_login_pt, create call-fw not registered to 152 (css_logout)

(4) make both DNs member of same pickup group

(5) if you use hunting, make both members of the same line group

HTH

Btw, by both ringing at the same time, i'm assuming when the device profile is logged on, it will ring and when it logs out the same extension rings on the same phone...
Basically the idea is that logging in and out just swaps the permission of the user so that nobody can use their phone for external calls when they are not at their desk.
Else, it works perfect for voicemail; on either the logout-pt's or login-pt's DN you can still forward calls to voicemail when not answered or busy...as a last step, cfw unregistered on the phone can to voicemail too and it wi still work, keep css-logout on the phone.for the cfwds

thank you for your valuable reply.
But i already implemented before i get the answer from you.

I didnt make the DNs of same pickup group yet.

But ill surely consider that step if client ask for it.
Im marking this as accept as solution.
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: