Accepted Solutions
Hi Cristian,
That restriction is shown here
SCCP: Configuring Single Number Reach
To enable the Single Number Reach (SNR) feature on SCCP IP phones, perform the following steps.
Prerequisites
•
Cisco Unified CME 7.1 or a later version
•Cisco IP Communicator requires version 2.1.4 or later
Restrictions
•Each IP phone supports only one SNR directory number.
•SNR feature is not supported for the following:
–SCCP-controlled analog FXS phones
–MLPP calls
–Secure calls
–Video calls
–Hunt group directory numbers (voice or ephone)
–MWI directory numbers
–Trunk directory numbers
•An overlay set can support only one SNR directory number and that directory number must be the primary directory number.
•Call forward no answer (CFNA), configured with the call-forward noan command, is disabled if SNR is configured on the directory number. To forward unanswered calls to voice mail, use the cfwd-noan keyword in the snr command.
•Call forwarding of unanswered calls, configured with the cfwd-noan keyword in the snr command, is not supported for PSTN calls from FXO trunks because the calls connect immediately.
•Calls always remain private. If a call is answered on a remote phone, the desktop IP phone can not listen to the call unless it resumes the call.
•U.S. English is the only locale supported for SNR calls.
You may want to look into CME 9.0 which has this enhancement;
Virtual SNR DN for Cisco Unified SCCP IP Phones
A virtual SNR DN is a DN not associated with any registered phone. It can be called, forwarded to a preconfigured mobile phone, or put on an Auto Hold state when the mobile phone answers the call or the time delay is reached. In the Auto Hold state, the DN can either be floating or unregistered. A floating DN is a DN not configured for any phone while an unregistered DN is one associated with phones not registered to a Cisco Unified CME system.
Before Cisco Unified CME 9.0, an SNR DN feature did not launch when the SNR DN was not associated with any registered phone. Although a call could be forwarded to the mobile phone using the call-forward busy command, the SNR DN had to be configured under a phone. Users who were assigned floating DNs could not forward calls unless they had a phone assigned to them.
In Cisco Unified CME 9.0 and later versions, an SNR DN is not required to be associated with a registered phone to have the SNR DN feature launched. A call can be made to a virtual SNR DN and the SNR feature can be launched even when the SNR DN is not associated with any phone. A call to a virtual SNR DN can be forwarded to an auto-attendant service when the preconfigured mobile phone is out of service and the voice mail can be retrieved using the telephone or extension number assigned to the voice mailbox.
Although the virtual SNR DN feature is designed for SNR DNs that are not associated with registered phones, this feature also supports virtual SNR DNs that complete phone registration or login and registered DNs that become virtual when all associated registered phones become unregistered.
http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/admin/configuration/guide/cmesnr.html#wp1011683
Cheers!
Rob
Hi Cristian,
That restriction is shown here
SCCP: Configuring Single Number Reach
To enable the Single Number Reach (SNR) feature on SCCP IP phones, perform the following steps.
Prerequisites
•Cisco Unified CME 7.1 or a later version
•Cisco IP Communicator requires version 2.1.4 or later
Restrictions
•Each IP phone supports only one SNR directory number.
•SNR feature is not supported for the following:
–SCCP-controlled analog FXS phones
–MLPP calls
–Secure calls
–Video calls
–Hunt group directory numbers (voice or ephone)
–MWI directory numbers
–Trunk directory numbers
•An overlay set can support only one SNR directory number and that directory number must be the primary directory number.
•Call forward no answer (CFNA), configured with the call-forward noan command, is disabled if SNR is configured on the directory number. To forward unanswered calls to voice mail, use the cfwd-noan keyword in the snr command.
•Call forwarding of unanswered calls, configured with the cfwd-noan keyword in the snr command, is not supported for PSTN calls from FXO trunks because the calls connect immediately.
•Calls always remain private. If a call is answered on a remote phone, the desktop IP phone can not listen to the call unless it resumes the call.
•U.S. English is the only locale supported for SNR calls.
You may want to look into CME 9.0 which has this enhancement;
Virtual SNR DN for Cisco Unified SCCP IP Phones
A virtual SNR DN is a DN not associated with any registered phone. It can be called, forwarded to a preconfigured mobile phone, or put on an Auto Hold state when the mobile phone answers the call or the time delay is reached. In the Auto Hold state, the DN can either be floating or unregistered. A floating DN is a DN not configured for any phone while an unregistered DN is one associated with phones not registered to a Cisco Unified CME system.
Before Cisco Unified CME 9.0, an SNR DN feature did not launch when the SNR DN was not associated with any registered phone. Although a call could be forwarded to the mobile phone using the call-forward busy command, the SNR DN had to be configured under a phone. Users who were assigned floating DNs could not forward calls unless they had a phone assigned to them.
In Cisco Unified CME 9.0 and later versions, an SNR DN is not required to be associated with a registered phone to have the SNR DN feature launched. A call can be made to a virtual SNR DN and the SNR feature can be launched even when the SNR DN is not associated with any phone. A call to a virtual SNR DN can be forwarded to an auto-attendant service when the preconfigured mobile phone is out of service and the voice mail can be retrieved using the telephone or extension number assigned to the voice mailbox.
Although the virtual SNR DN feature is designed for SNR DNs that are not associated with registered phones, this feature also supports virtual SNR DNs that complete phone registration or login and registered DNs that become virtual when all associated registered phones become unregistered.
http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/admin/configuration/guide/cmesnr.html#wp1011683
Cheers!
Rob
