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? ... View more

We have strange kind of implementation so people have to think not the normal way of implementation Our client must have to use VPN connection. its a must. jabber client they want to use. after establishing the vpn and tried to make call they were able to establish calls but cannot no voice traffic between end parties. because of limitation of VPN concentrator to route the call between end points we were forced to use expressway just to route the voice call. This accomplish our voice issue. they were able to hear voice. ie expressway inside VPN connection. After getting into VPN users will not get internet access.    CUCM,IMP,CUC, Expressway C and Edge are all in one vlan and one subnet.    collab-edge srv added in our DNS. whether the users through vpn or locally all will use collab-edge. its not hosted in public but internally as if like lab environment. another DNS server we used for cisco-uds srv. its a standalone dns server with all dns entries required. This is the dns server for expressway C.   but today for some reason none of our clients are able to login to jabber. users are ldap users. either ill get message cannot communicate with server or username or password is incorrect message.   our security engineer had made some changes since all our traffic are now passing through expressway Edge. so he changed so many policies which were working when there was no expressway in picture.   now when i checked firewall i foound client PC traffic is blocked to cucm publisher with 8443. I didnt understand how this is happening actually it should be only from expresswau and how jabber client is requesting to cucm for login authentication instead of expressway.   I want to know how the ldap authentication process is happening in normal expressway and in our scenario happening.    should we open 8443 from jabber client network to cucm publisher and cucm subscriber.   When we tried self care portal for cucm subscriber i found i cannot login to it. it gives error and usrname and passware is incorrect. is it correct to have like that for subscriber? dont know its getting blocked or not.   ... View more