cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1245
Views
10
Helpful
7
Replies

Call Forwarding from offline phone

gunnydaman
Level 1
Level 1

Hello Everyone,

 

Currently, my organization is using mobility extension profiles to lock down phones. The users here must log in to a device profile in order to call out past the limited call search space they are in. This system works well, however when a user is logged in, the original number of the phone can't be called or vice versa due to the number being inactive.

I would like to have it where if either number is called and doesn't answer, a redirection will automatically take place and dial the secondary number. I already tried call forwarding, but because one of the numbers is inactive at all times it doesn't forward to the active number. 

Can anyone suggest a solution for my issue.

 

Thanks,

Matt

2 Accepted Solutions

Accepted Solutions

What I is use in my environment.

 

All my users use extensions mobility. For each user I have two extensions as below.

  • One extension for example 123 in logout partition.
  • Second extension as the above 123 but in different partition.

CSS is configured in CUCM in such a way that when some one calls 123 extensions first it lands on 123 in logout partition and if unregistered it forward to 123 login.How I made this working is,

  • CSS internal has partition logout .So when some one calls 123  it try 123 logout. 
  • 123 in logout partition  is applied on the phone and when users don't login still they receive calls on desk phones.  And  123 logout extensions has forwarding setting unregistered to 123 in  login partition   with css login(which has only portion login). and busy and no answer to voicemail. 
  • so when a user login to extension mobility,  123 in login  partition gets registered  and 123 logout  gets unregistered. so all calls get forwarded by the above forward setting on 123 logout extension to 123 login . And I have no answer and busy  set on 123 login extension to voicemail.

 

Modify the above according to your setup.

 

 



Response Signature


View solution in original post

Create CSS with partition P_login

 

2.PNG

 

Logout extension 399 is assigned on the phone and its on internal partition.

 

3.PNG

 

Call forwarding setting for unregistered set to  399 in login partition and i assigned CSS_Login for call forwarding CSS .  Busy and no answer i set to voicemail.

 

4.PNG

 

 

Configured a device profile with extension 399 in login partition.

 

5.PNG

When user logined  and if busy or not answered it transfer to voicemail.

 

6.PNG

 

 



Response Signature


View solution in original post

7 Replies 7

What I is use in my environment.

 

All my users use extensions mobility. For each user I have two extensions as below.

  • One extension for example 123 in logout partition.
  • Second extension as the above 123 but in different partition.

CSS is configured in CUCM in such a way that when some one calls 123 extensions first it lands on 123 in logout partition and if unregistered it forward to 123 login.How I made this working is,

  • CSS internal has partition logout .So when some one calls 123  it try 123 logout. 
  • 123 in logout partition  is applied on the phone and when users don't login still they receive calls on desk phones.  And  123 logout extensions has forwarding setting unregistered to 123 in  login partition   with css login(which has only portion login). and busy and no answer to voicemail. 
  • so when a user login to extension mobility,  123 in login  partition gets registered  and 123 logout  gets unregistered. so all calls get forwarded by the above forward setting on 123 logout extension to 123 login . And I have no answer and busy  set on 123 login extension to voicemail.

 

Modify the above according to your setup.

 

 



Response Signature


Hello Nithin,

 

So I am still having an issue with the partitions. I have the same number in two different calling search spaces and two different partitions, but when I call, it only dials the number in the first partition and not the second, and being that the first partition is a mobility extension using a device profile, it simply gives me a busy signal as the device profile is not logged into and offline.

Even if I set the forwarding for busy signal, I continue to get busy signal and no forward to number in separate partition and calling search space. 

Any idea on how to fix this problem?

 

Thanks,

Matt

The first partition extension's call forward should be to second partition  extension for Forward No Coverage  & Forward No Coverage Condition. 

 

Screenshot 2021-02-11 at 9.23.12 PM.png

 

 



Response Signature


I still just get a busy signal and it never forwards.

 

Line 1: 

Directory number assigned directly to phone

Partition: Part1

Calling search space: space1

 

Line 2

Device profile (Floater line which doesn't exist on physical phone till after user logs in)

Partition: Part2

Calling search space: space 2

 

Does this help?

If you don’t get this to work as described by @Nithin Eluvathingal you are not configuring it as he described. Recommend you to go back to his reply, read it again, understand what it say, check your configuration and address what you have done wrong.



Response Signature


Create CSS with partition P_login

 

2.PNG

 

Logout extension 399 is assigned on the phone and its on internal partition.

 

3.PNG

 

Call forwarding setting for unregistered set to  399 in login partition and i assigned CSS_Login for call forwarding CSS .  Busy and no answer i set to voicemail.

 

4.PNG

 

 

Configured a device profile with extension 399 in login partition.

 

5.PNG

When user logined  and if busy or not answered it transfer to voicemail.

 

6.PNG

 

 



Response Signature


Thank you for taking time to further explain this. 

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: