Archive for the ‘CME’ Category

There are times when you would like to forward a call coming into your gateway out to PSTN before it goes to Call manager. Reason could be WAN outage to Call managers or Call manager down situation.

This is how you can route out an incoming call out of the gateway.

Let suppose the mainline number coming into the gateway is ‘881456’. The following setup will route the call out of the gateway to PSTN.

voice translation-rule 10
rule 1 /881456/ /901139886666/
!
voice translation-profile RedirectPSTN
translate called 10
!
dial-peer voice 10 pots
description Incoming Dial Peer
translation-profile incoming RedirectPSTN
incoming called-number 881456
direct-inward-dial
port 0/0/0:15
!
dial-peer voice 20 pots
description Outbound Dial Peer
destination-pattern 9T
port 0/0/0:15
!

Call comes in and match incoming-called number dialpeer 10 and then it will match the incoming translation profile. The translation profile will translate the number to another PSTN number with prefix ‘9’. This will match dialpeer 20 and will send the call out to PSTN.

Interesting case today. I had a call from customer saying they had a power cut and when the power was restored all their phones went into ‘Registering’ status.

I initially thought it could be a network issue from switches to CUCME gateway as the config was looking fine to me. I did a show ephone summary and found all of them in ‘Unregistered’ status. Nothing changed really, the config was all ok and these phones were all working fine few minutes before. So what has gone wrong?

I started going through the config if anything has changed but nothing changed. Then I did show telephony service and found below:

=====================
Version 8.1
Max phoneload sccp version 17
Max dspfarm sccp version 18
Cisco Unified Communications Manager Express
For on-line documentation please see:
http://www.cisco.com/en/US/products/sw/voicesw/ps4625/tsd_products_support_series_home.html

protocol mode default
ip source-address 172.16.49.250 port 2000
ip qos dscp:
ef (the MS 6 bits, 46, in ToS, 0xB8) for media
cs3 (the MS 6 bits, 24, in ToS, 0x60) for signal
af41 (the MS 6 bits, 34, in ToS, 0x88) for video
default (the MS 6 bits, 0, in ToS, 0x0) for serviceservice directed-pickup
no auto-reg-ephone
load 7937 apps37sccp.1-3-4-0
load 7942 SCCP42.8-5-4S
max-ephones 25
max-dn 200
max-conferences 8 gain -6
dspfarm units 0
dspfarm transcode sessions 0
conference software
.
.
.
.
.
.
.
web admin customer name Customer
edit DN through Web:  enabled.
edit TIME through web:  disabled.
Log (table parameters):
max-size: 150
retain-timer: 15
create cnf-files version-stamp 7960 Jul 29 2011 15:25:03
transfer-system full-consult
transfer-digit-collect new-call
local directory service: enabled.
Extension-assigner tag-type ephone-tag.
shutdown

Did you guys see what was wrong?

Somehow the telephony service went into shutdown state. I did a no shut on telephony service and they all start registering.

CME Paging

Posted: January 13, 2011 in CME
Tags:

A paging number can be defined to relay audio pages to a group of designated phones. When a caller dials the paging number (ephone-dn), each idle IP phone that has been configured with the paging number automatically answers using its speakerphone mode. Displays on the phones that answer the page show the caller ID that has been set using the name command under the paging ephone-dn. When the caller finishes speaking the message and hangs up, the phones are returned to their idle states.

SAMPLE CONFIG:
=============

Ephone-dn 22  will be paging DN – the number you dial to broadcast – in this case dial “5001” and it will ring all ephones part of this paging group and they will go on speakerphone.

ephone-dn 22
name Paging Shipping
number 5001
paging ip 239.1.1.10 port 2000

These are paging group members, so dialling 5001 will ring these four numbers:

ephone 4
mac-address 0030.94c3.1111
button 1:1 2:2
paging-dn 22 multicast

ephone 8
mac-address 0030.94c3.0bcf
button 1:2
paging-dn 22 multicast

ephone 12
mac-address 0030.94c3.8567
button 1:3
paging-dn 22 multicast

ephone 13
mac-address 0030.94c3.8724
button 1:4
paging-dn 22 multicast

You can also use groups for Paging:

ephone-dn 9
number 7001
name Sales
paging ip 239.1.1.2 port 2000
ephone-dn 11
number 7002
name Accounts
paging ip 239.1.1.3 port 2000
ephone-dn 17
number 7010
name Sales&Acccounts
paging ip 239.1.1.20 port 2000
paging group 9,11

 

SAMPLE CONFIG:

=============

 

Ephone-dn 22  will be paging DN – the number you dial to broadcast – in this case dial “5001” and it will ring all ephones part of this paging group and they will go on speakerphone.

 

ephone-dn 22

name Paging Shipping

number 5001

paging ip 239.1.1.10 port 2000

These are paging group members, so dialling 5001 will ring these four numbers:

ephone 4

mac-address 0030.94c3.1111

button 1:1 2:2

paging-dn 22 multicast

 

ephone 8

mac-address 0030.94c3.0bcf

button 1:2

paging-dn 22 multicast

 

ephone 12

mac-address 0030.94c3.8567

button 1:3

paging-dn 22 multicast

 

ephone 13

mac-address 0030.94c3.8724

button 1:4

paging-dn 22 multicast

The Cisco Unified IP Phone 7931 includes 24 buttons that can be assigned to lines and call features. A 3-color LED provides call status information for each line.

The line buttons are numbered 24-1 from top to bottom. The numbers do not appear on the phone.

There are two ways how the top four buttons can be programmed.

enable
configure terminal
ephone template 15
button-layout set phone-type [1 | 2]**
exit

ephone 3
ephone-template 15
end

** Specifies which fixed set of feature buttons appears on a Cisco Unified IP Phone 7931G that uses a template in which this is configured.

•1—Includes two predefined feature buttons: button 24 is Menu and button 23 is Headset.

•2—Includes four predefined feature buttons: button 24 is Menu; button 23 is Headset; button 22 is Directories; and button 21 is Messages

More on 7931 and CME here.

This was an interesting scenario where incoming calls were getting ‘user busy’ message at the gateway and an engage tone was heard at calling party side.

*Aug 18 08:36:53.581: ISDN Se0/0/0:15 Q931: RX <-CALL_PROC pd = 8  callref = 0x8D7E
Channel ID i = 0xA9839E
Exclusive, Channel 30

*Aug 18 08:36:54.997: ISDN Se0/0/0:15 Q931: RX <- DISCONNECT pd = 8  callref = 0x8D7E
Cause i = 0x8091 -User busy

It was not just one extension but several extensions which were having the same issue. They were all running fine till yesterday!

Something must have happened…

I did debug voip ccapi inout for a working extension and a non-working one, this is what I found:

Successful call to 7536 and un-successful call to 7534:

Call to 7536:

Aug 19 08:41:00.697: //757/541618588180/CCAPI/cc_api_display_ie_subfields:

ccCallSetupRequest:
cisco-username=
—– ccCallInfo IE subfields —–

cisco-ani=9XXXXXXX395
cisco-anitype=2
cisco-aniplan=1
cisco-anipi=0
cisco-anisi=1
dest=7536
cisco-desttype=0
cisco-destplan=1
cisco-rdie=FFFFFFFF
cisco-rdn=
cisco-lastrdn=
cisco-rdntype=-1
cisco-rdnplan=-1
cisco-rdnpi=-1
cisco-rdnsi=-1
cisco-redirectreason=-1   fwd_final_type =0
final_redirectNumber =
hunt_group_timeout =0

Aug 19 08:41:00.697: //757/541618588180/CCAPI/ccIFCallSetupRequestPrivate:
Interface=0x480CDF30, Interface Type=1, Destination=, Mode=0x0,
Call Params(Calling Number=9XXXXXXX395,(Calling Name=)(TON=National, NPI=ISDN, Screening=User, Passed, Presentation=Allowed),
Called Number=7536(TON=Unknown, NPI=ISDN), Calling Translated=FALSE,
Subscriber Type Str=RegularLine, FinalDestinationFlag=TRUE, Outgoing Dial-peer=10, Call Count On=FALSE,
Source Trkgrp Route Label=, Target Trkgrp Route Label=, tg_label_flag=0, Application Call Id=)
Aug 19 08:41:00.701: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:
Aug 19 08:41:00.701: :cc_get_feature_vsa malloc success
Aug 19 08:41:00.701: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:
Aug 19 08:41:00.701:  cc_get_feature_vsa count is 8
Aug 19 08:41:00.701: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:

Aug 19 08:41:00.701: :FEATURE_VSA attributes are: feature_name:0,feature_time:1187854080,feature_id:785
Aug 19 08:41:00.701: //758/541618588180/CCAPI/ccIFCallSetupRequestPrivate:
SPI Call Setup Request Is Success; Interface Type=1, FlowMode=1
Aug 19 08:41:00.701: //758/541618588180/CCAPI/ccCallSetContext:
Context=0x46B3748C
Aug 19 08:41:00.701: //757/541618588180/CCAPI/ccSaveDialpeerTag:

Outgoing Dial-peer=10

Aug 19 08:41:00.901: //758/541618588180/CCAPI/cc_api_set_called_ccm_detected:
CallInfo(called ccm detected=TRUE ccmVersion 1)
Aug 19 08:41:00.901: //758/541618588180/CCAPI/cc_api_call_proceeding:
Interface=0x480CDF30, Progress Indication=NULL(0)
Aug 19 08:41:00.905: //758/541618588180/CCAPI/cc_api_set_called_ccm_detected:
CallInfo(called ccm detected=TRUE ccmVersion 1)
Aug 19 08:41:00.905: //758/541618588180/CCAPI/cc_api_set_delay_xport:
CallInfo(delay xport=TRUE)
Aug 19 08:41:00.905: //758/541618588180/CCAPI/cc_api_call_alert:
Interface=0x480CDF30, Progress Indication=NULL(0), Signal Indication=SIGNAL RINGBACK(1)
Aug 19 08:41:00.909: //758/541618588180/CCAPI/cc_api_call_alert:
Call Entry(Retry Count=0, Responsed=TRUE)
Aug 19 08:41:00.909: //758/541618588180/CCAPI/cc_api_set_called_ccm_detected:

CallInfo(called ccm detected=TRUE ccmVersion 1)

Aug 19 08:41:00.909: //758/541618588180/CCAPI/cc_api_call_notify:
Data Bitmask=0x5, Interface=0x480CDF30, Call Id=758
Aug 19 08:41:00.909: //757/541618588180/CCAPI/ccCallAlert:
Progress Indication=NULL(0), Signal Indication=SIGNAL RINGBACK(1)
Aug 19 08:41:00.909: //757/541618588180/CCAPI/ccCallAlert:
Call Entry(Responsed=TRUE, Alert Sent=TRUE)
Aug 19 08:41:00.913: //757/541618588180/CCAPI/ccGenerateToneInfo:

Stop Tone On Digit=FALSE, Tone=Ring Back,

Tone Direction=Network, Params=0x0, Call Id=757
Aug 19 08:41:00.921: //758/541618588180/CCAPI/cc_api_get_ssCTreRoutingNotSupported:
CallInfo(ssCTreRoutingNotSupported=FALSE)
Aug 19 08:41:00.921: //758/541618588180/CCAPI/cc_api_get_ccm_detected:
CallInfo(ccm detected=TRUE)
Aug 19 08:41:00.921: //757/541618588180/

CCAPI/ccCallNotify:
Data Bitmask=0x5, Call Id=757

Call to 7534:

—– ccCallInfo IE subfields —–

cisco-ani=9XXXXXXX395
cisco-anitype=2
cisco-aniplan=1
cisco-anipi=0
cisco-anisi=1
dest=7534
cisco-desttype=0
cisco-destplan=1
cisco-rdie=FFFFFFFF
cisco-rdn=
cisco-lastrdn=
cisco-rdntype=-1
cisco-rdnplan=-1
cisco-rdnpi=-1
cisco-rdnsi=-1
cisco-redirectreason=-1   fwd_final_type =0
final_redirectNumber =
hunt_group_timeout =0

Aug 19 08:36:26.159: //-1/B07908F8816D/CCAPI/cc_api_call_setup_ind_common:
Interface=0x49470D5C, Call Info(Calling Number=9XXXXXXX395,(Calling Name=)(TON=National, NPI=ISDN, Screening=User, Passed, Presentation=Allowed),Called Number=7534(TON=Unknown, NPI=ISDN),

Calling Translated=FALSE, Subscriber Type Str=RegularLine, FinalDestinationFlag=TRUE,
Incoming Dial-peer=2, Progress Indication=NULL(0), Calling IE Present=TRUE,
Source Trkgrp Route Label=, Target Trkgrp Route Label=, CLID Transparent=FALSE), Call Id=-1
Aug 19 08:36:26.159: //-1/B07908F8816D/CCAPI/ccCheckClipClir:
In: Calling Number=9XXXXXXX395(TON=National, NPI=ISDN, Screening=User, Passed, Presentation=Allowed)
Aug 19 08:36:26.159: //-1/B07908F8816D/CCAPI/ccCheckClipClir:
Out: Calling Number=9XXXXXXX395(TON=National, NPI=ISDN, Screening=User, Passed, Presentation=Allowed)
Aug 19 08:36:26.159: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:

Aug 19 08:36:26.163: :cc_get_feature_vsa malloc success
Aug 19 08:36:26.163: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:

Aug 19 08:36:26.163:  cc_get_feature_vsa count is 11
Aug 19 08:36:26.163: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:

Aug 19 08:36:26.163: :FEATURE_VSA attributes are: feature_name:0,feature_time:1187856544,feature_id:752
Aug 19 08:36:26.163: //725/B07908F8816D/CCAPI/cc_api_call_setup_ind_common:

Set Up Event Sent;
Call Info(Calling Number=9XXXXXXX395(TON=National, NPI=ISDN, Screening=User, Passed, Presentation=Allowed),
Called Number=7534(TON=Unknown, NPI=ISDN))
Aug 19 08:36:26.167: //725/B07908F8816D/CCAPI/cc_process_call_setup_ind:

Event=0x48577A78
Aug 19 08:36:26.167: //-1/xxxxxxxxxxxx/CCAPI/cc_setupind_match_search:

Try with the demoted called number 7534

Aug 19 08:36:26.167: //725/B07908F8816D/CCAPI/ccCallSetContext:
Context=0x46B3C0AC
Aug 19 08:36:26.167: //725/B07908F8816D/CCAPI/cc_process_call_setup_ind:
>>>>CCAPI handed cid 725 with tag 2 to app “_ManagedAppProcess_Default”
Aug 19 08:36:26.179: //725/B07908F8816D/CCAPI/ccCallProceeding:
Progress Indication=NULL(0)

Aug 19 08:36:26.183: //-1/xxxxxxxxxxxx/CCAPI/cc_setupind_match_search:
Try with the demoted called number 7534
Aug 19 08:36:26.183: //-1/xxxxxxxxxxxx/CCAPI/cc_update_feature_vsa:
Aug 19 08:36:26.183: : updating existing feature vsa
Aug 19 08:36:26.183: //-1/xxxxxxxxxxxx/CCAPI/cc_update_feature_vsa:

Aug 19 08:36:26.183:  feature call basic
Aug 19 08:36:26.203: //725/B07908F8816D/CCAPI/ccCallDisconnect:
Cause(Value=17, Tag=0x0, Call Entry(Previous Disconnect Cause=0, Disconnect Cause=0)
Aug 19 08:36:26.203: //725/B07908F8816D/CCAPI/ccCallDisconnect:

Cause Value=17, Call Entry(Responsed=TRUE, Cause Value=17)

Aug 19 08:36:26.203: //725/B07908F8816D/CCAPI/cc_api_get_transfer_info:
Transfer Number Is Null
Aug 19 08:36:26.371: //725/B07908F8816D/CCAPI/cc_api_call_disconnect_done:
Disposition=0, Interface=0x49470D5C, Tag=0x0, Call Id=725,
Call Entry(Disconnect Cause=17, Voice Class Cause Code=0, Retry Count=0)
Aug 19 08:36:26.375: //725/B07908F8816D/CCAPI/cc_api_call_disconnect_done:
Call Disconnect Event Sent
Aug 19 08:36:26.375: //-1/xxxxxxxxxxxx/CCAPI/cc_free_feature_vsa:
Aug 19 08:36:26.375: :cc_free_feature_vsa freeing 46CD4098
Aug 19 08:36:26.375: //-1/xxxxxxxxxxxx/CCAPI/cc_free_feature_vsa:

The above results show that a successful call did hit the outbound VoIP dialpeer which was pointing to CCM but the failed call was just hitting the Inbound POTS dialpeer and was not routing to the VoIP dialpeer. Why in the world one DDI of same range is routing to CCM while other is returning user busy (the cause code 17 is user busy). The phone at x7534 was registered to call manager and there were all ISDN channels available (Show isdn service). I checked the gateway configuration and found telephony-service configured on it with auto-provision none.

telephony-service
srst mode auto-provision none
srst ephone template 1
srst ephone description srst fallback auto-provision phone
srst dn template 1
srst dn line-mode dual

.

.

But I could also see all ephones and ephone-dn’s in the configuration. I found out that this failed extension x7534 was sitting there under one of the ephone-dn. I confirmed that a third party engineer configured SRST on the router previous evening and he checked everything working fine ….. what he did….he configured srst auto provision all to learn the dn’s so that he can configure the hunt groups and then locked it down using srst auto provision none. This, however, produced abnormal results as the phones which were learned by the gateway were preferred over VoIP dialpeer and a call to these numbers was not getting routed to Call manager. This is what I did to solve this issue:

Router(config)# dial-peer hunt 3
•0—Specifies longest match in phone number, explicit preference, random selection (default)
•1—Specifies longest match in phone number, explicit preference, least recent use.
•2—Specifies explicit preference, longest match in phone number, random selection.
•3—Specifies explicit preference, longest match in phone number, least recent use.
•4—Specifies least recent use, longest match in phone number, explicit preference.
•5—Specifies least recent use, explicit preference, longest match in phone number.
•6—Specifies random selection.
•7—Specifies least recent use.

ephone-dn  1  dual-line
preference 8
!
!
ephone-dn  2  dual-line
preference 8
!
!
ephone-dn  3  dual-line
preference 8
!
!
ephone-dn  4  dual-line
preference 8
!
!
ephone-dn  5  dual-line
preference 8
!
!
ephone-dn  6  dual-line
preference 8
!

to ephone-dn 45

– same –

Tested the call all working fine.

What was happening – the call was coming in and because the phone was learned as ephone it was preferred over VoIP dialpeer.

To avoid incorrect routing when you prebuild ephone-dns for Cisco Unified Communications Manager phones in Cisco Unified CME, use the preference command in ephone-dn and voip-dial-peer configuration mode to create a higher preference (0 being the highest) for the voip dial peer than the preference for the prebuilt directory number.

The concept of max-calls per button and busy trigger is quite easy but has been made complex.

max-calls-per-button is used for maximum calls (incoming and outgoing) which can go through that line.

busy-trigger-per-button is used to busy out incoming calls after the parameter set has been reached. So if an ephone has busy-trigger-per-button set to 2 and the phone has two active calls then the third call will go to voicemail (if set), busy tone or forwarded to another number if call-forward noan is set.

huntstop channel is used on a shared line for incoming calls, rest of the channels are reserved for outgoing calls.

In the following scenario, I have configured following:

– Phone 1 can only take 4 inbound calls
– Phone 2 can only take 2 inbound calls
– Shared line of Phone 1 & Phone 2 can take 5 inbound calls

ephone-dn 1 octo-line
number 3001 no-reg primary
description +56576513001
name “Phone 1”
call-forward busy 3220
call-forward noan 3220 timeout 20
!
!
ephone-dn 2 octo-line
number 3002 no-reg primary
description +56576513002
name “Phone 2”
call-forward busy 3220
call-forward noan 3220 timeout 20
!
ephone-dn 3 octo-line
number 3003 no-reg primary
description +56576513003
huntstop channel 5  << Shared line – only inbound calls
!
!
ephone 1
privacy-buton
mac-address XXXX.XXXX.XXXX
ephone-template 1
max-calls-per-button 5    << inbound & outbound
busy-trigger-per-button 4 << only inbound
button 1:1 2:3
!
ephone 2
privacy-button
mac-address XXXX.XXXX.XXXX
ephone-template 1
max-calls-per-button 5  << inbound & outbound
busy-trigger-per-button 2 << only inbound
button 1:2 2:3

Above, shared line 3003 is shared between ephone 1 and ephone 2. If there are two active calls on ephone 2 then the third incoming call will ring ephone 1 as ephone 2 will reach its busy-trigger. The third, fourth and fifth call come and ring ephone 1 but the sixth call will hit huntstop channel for shared line ephone-dn 3 and will not be handled.

CME – Automatic Line Selection

Posted: August 3, 2010 in CME
Tags:

On multiline IP phones, lifting the handset automatically selects the first ringing line on the phone or, if no line is ringing, selects the first available idle line for outgoing calls. This is the default behavior for all multiline IP phones.

It may be desired that a particular line be selected whenever an outgoing line is made.

ephone 34
auto-line 3 answer-incoming

•auto-line—Picking up the handset answers the first ringing line or, if no line is ringing, selects the first idle line. This is the default.

•auto-line button-number—Picking up the handset for an outgoing call selects the line associated with the specified button. The default if this argument is not used is the topmost available line.

•auto-line button-number answer-incoming—Picking up the handset answers the incoming call on the line associated with the specified button.

•auto-line incoming—Picking up the handset answers the first ringing line but, if no line is ringing, does not select an idle line for an outgoing call. Pressing a line button selects a line for an outgoing call.

•no auto-line—Disables automatic line selection. Pressing the Answer soft key answers the first ringing line, and pressing a line button selects a line for an outgoing call. Picking up the handset does not answer calls or provide dial tone.

Reference: CME Admin Guide

Intercom and Barge-IN:

An intercom line is a dedicated two-way audio path between two phones. Cisco Unified CME supports intercom functionality for one-way and press-to-answer voice connections using a dedicated pair of intercom directory numbers on two phones that speed-dial each other.

If we have to c0nfigure Intercom between two phones..lets say between a manager phone and his Secretary..so that both these intercom numbers are not reachable from rest of the cluster and are not dial-able. This is how we can configure this:

ephone-dn  9
description Manager
number D40 no-reg primary
intercom E50
!
ephone-dn  10
description Secretary
number E50 no-reg primary
intercom D40
!

ephone  1
button  4:9
!
ephone  2
button  4:10

In the above configuration, both users can Intercom each other when they are not busy on another line. Lets say Manager wants to Interrupt even if Secretary is on the phone. To do that we will have to configure ‘barge-in‘ at Secretary ephone-dn.

ephone-dn  9
number D40 no-reg primary
intercom E50
!
ephone-dn  10
number E50 no-reg primary
intercom D40 barge-in

ephone  1
button  4:9
!
ephone  2
button  4:10

Whisper Intercom:

When a phone user dials a whisper intercom line, the called phone automatically answers using speakerphone mode, providing a one-way voice path from the caller to the called party, regardless of whether the called party is busy or idle.

Unlike the standard intercom feature, this feature allows an intercom call to a busy extension. The calling party can only be heard by the recipient. The original caller won’t hear anything coming from called-party.
ephone-dn 24
number 3001
whisper-intercom label “Marketing”
!
ephone 24
mac-address 02EA.E789.B765
button 1:24

Here if someone dials 3001, they can say whatever they want as the user at ext 3001 will hear them but they can’t hear him.

You can use an external TFTP server to off load the TFTP server function on the Cisco Unified CME router.

This is also important if your router is not a high end router while the CME configuration is complex with many phones and expansion modules. Also Using flash memory or slot memory on the Cisco Unified CME router allows you to use different configuration files for each phone type or for each phone, which allows you to specify different user locales and network locales for different phones

To define a location other than system:/its for storing configuration files for per-phone and per-phone type configuration files, perform the following steps.

telephony-service
cnf-file location flash:
cnf-file perphone

The above configuration did resolve an issue with one of my customer where all the phones would reboot after 5 minutes.

Note: When the storage location chosen is flash memory and the file system type on this device is Class B (LEFS), check free space on the device periodically and use the squeeze command to free the space used up by deleted files. Unless you use the squeeze command, the space used by the moved or deleted configuration files cannot be used by other files. Rewriting flash memory space during the squeeze operation may take several minutes. Run this command during scheduled maintenance periods or off-peak hours.

Reference: Cisco CUCME Admin Guide

This was a very interesting scenario I came across for this customer where these two phones were not ringing at all. Any incoming call and they would just flash. No Ringtone.

I confirmed that the phones were working fine few days back but then suddenly started just flashing. One other phone in the same group was working fine. I matched the configuration of all three phones and they were all same. I know that the only way you can change the ring settings from CLI is from the button command.If you are using ‘:’ then that means Ring. Taken from Cisco as follows:

button button-number {separator} dn-tag [,dn-tag…] [button-number{x}overlay-button-number] [button-number…]

:  (colon)—Normal ring. For incoming calls on this extension, the phone produces audible ringing, a flashing icon in the phone display, and a flashing red light on the handset. On the Cisco IP Phone 7914 Expansion Module, a flashing yellow light also accompanies incoming calls.

•b—Beep but no ring. Audible ring is suppressed for incoming calls, but call-waiting beeps are allowed. Visible cues are the same as those described for a normal ring.

•c—Call waiting. Provides call waiting for secondary calls to an overlaid ephone-dn. See also the o keyword.

•f—Feature ring. Differentiates incoming calls on a special line from incoming calls on other lines on the phone. The feature-ring cadence is a triple pulse, as opposed to a single pulse for normal internal calls and a double pulse for normal external calls.

First I thought may be they are getting flashing only on shared lines but confirmed it was the same flashing if someone dial their primary number as well. Configuration of ephone-dn and ephone was similar to this:

ephone-dn  17  octo-line
number 2920
pickup-group 1
label Nicky Brian (2920)
name Nicky Brian
call-forward busy 8005
call-forward noan 8005 timeout 10
corlist incoming User-international
!

ephone  20
mac-address 0023.3XXX.XXXX
ephone-template 1
username “nbri” password welcome
type 7965 addon 1 7916-24
keep-conference endcall
button  1:17 2:187 3s186 4:180
no button  5:182 6:185 7s1 8s2
button  5:181 6:185 7s1 8s2
button  9s3 10s4 11s6 12s8
button  13s10 14s11 15s13 16s14
button  18s28 19s15 20s20 21s37
button  22s27 23s12 24s7 25s36
button  26s29 27s9
!
!

This doesn’t tell me why phones are not ringing. Configuration looks absolutely correct.

Then I decided to check the ephone configuration by running the command ‘sh ephone‘. This customer have quite a few phones with expansion modules so I had to be careful I am looking at right ephones.

This is what I found from one of the ephone which was just flashing.

ephone-20[19] Mac:0023.XXXX.XXXX TCP socket:[13] activeLine:0 whisperLine:0 REGISTERED in SCCP ver 17/12 max_streams=5
mediaActive:0 whisper_mediaActive:0 startMedia:0 offhook:0 ringing:0 reset:0 reset_sent:0 paging 0 debug:0 caps:9 privacy:0
IP:10.60.6.X 12386 7965  sub=1 keepalive 3350 max_line 30 available_line 30 DnD
Phone reports 30 Available Lines
button 1: dn 17 number 2920 CH1   IDLE         CH2   IDLE         CH3   IDLE         CH4   IDLE         CH5   IDLE         CH6   IDLE         CH7   IDLE         CH8   IDLE         shared
button 2: dn 187 number 8802 CH1   IDLE         CH2   IDLE         CH3   IDLE         CH4   IDLE         CH5   IDLE         CH6   IDLE         CH7   IDLE         CH8   IDLE         shared
button 3: dn 186 number 8803 CH1   IDLE         mwi silent-ring shared
button 4: dn 180 number 8005 CH1   IDLE         CH2   IDLE         CH3   IDLE         CH4   IDLE         CH5   IDLE         CH6   IDLE         CH7   IDLE         CH8   IDLE         shared
button 5: dn 181 number 8806 CH1   IDLE         CH2   IDLE         CH3   IDLE         CH4   IDLE         CH5   IDLE         CH6   IDLE         CH7   IDLE         CH8   IDLE         shared
button 6: dn 185 number 8804 CH1   IDLE         CH2   IDLE         CH3   IDLE         CH4   IDLE         CH5   IDLE         CH6   IDLE         CH7   IDLE         CH8   IDLE         shared
button 7: dn 1  number 2904 CH1   IDLE         CH2   IDLE         CH3   IDLE         CH4   IDLE         CH5   IDLE         CH6   IDLE         CH7   IDLE         CH8   IDLE         silent-ring shared
button 8: dn 2  number 2905 CH1   IDLE         CH2   IDLE         CH3   IDLE         CH4   IDLE         CH5   IDLE         CH6   IDLE         CH7   IDLE         CH8   IDLE         mwi silent-ring shared
button 9: dn 3  number 2906 CH1   CONNECTED    CH2   IDLE         CH3   IDLE         CH4   IDLE         CH5   IDLE         CH6   IDLE         CH7   IDLE         CH8   IDLE         silent-ring shared
button 10: dn 4  number 2907 CH1   IDLE         CH2   IDLE         CH3   IDLE         CH4   IDLE         CH5   IDLE         CH6   IDLE         CH7   IDLE         CH8   IDLE         mwi silent-ring shared
button 11: dn 6  number 2909 CH1   IDLE         CH2   IDLE         CH3   IDLE         CH4   IDLE         CH5   IDLE         CH6   IDLE         CH7   IDLE         CH8   IDLE         silent-ring shared
button 12: dn 8  number 2911 CH1   IDLE         CH2   IDLE         CH3   IDLE         CH4   IDLE         CH5   IDLE         CH6   IDLE         CH7   IDLE         CH8   IDLE         mwi silent-ring shared
button 13: dn 10 number 2913 CH1   IDLE         CH2   IDLE         CH3   IDLE         CH4   IDLE         CH5   IDLE         CH6   IDLE         CH7   IDLE         CH8   IDLE         silent-ring shared
button 14: dn 11 number 2914 CH1   CONNECTED    CH2   IDLE         CH3   IDLE         CH4   IDLE         CH5   IDLE         CH6

Carefully look at the above output and I am sure you will know why it was just flashing and not ringing.

The phone had DND enabled!