Prerequisites for Presence Service on CME

Prerequisites for Presence Service

•Cisco Unified CME 4.1 or a later version.

•Cisco Unified IP Phones 7911G, 7941G, 7941GE, 7961G, 7961GE, 7970G, and 7971GE require firmware load 8.2(1) or a later version.’

This basically means we cannot use presence on 79{46}0

via Cisco Unified Communications Manager Express System Administrator Guide – Configuring Presence Service  [Cisco Unified Communications Manager Express] – Cisco Systems.

Difference Between a Line and a Button

Note that a line is similar to, but not exactly the same as, a button on the phone. A line represents a phone’s capability to make a call connection, so each button that can make a call connection becomes a line. (For example, unoccupied buttons or speed-dial buttons are not lines.) Note also that a line is not the same as an ephone-dn. A button with overlaid ephone-dns is only one line, regardless of whether it has several ephone-dns (extension numbers) associated with it. In most cases an ephone’s line numbers do match its button numbers, but in a few cases they do not.

via Cisco Unified Communications Manager Express System Administrator Guide – Configuring Headset Auto-Answer  [Cisco Unified Communications Manager Express] – Cisco Systems.

ephone-dn s and dial-peers

Cisco Unified CME automatically creates one POTS dial peer for each ephone-dn when it is assigned a primary number. If the ephone-dn is assigned a secondary number, it creates a second POTS dial peer. If the dialplan-pattern command is used to expand the primary and secondary numbers for ephone-dns, it creates two more dial peers, resulting in the creation of the following four dial peers for the ephone-dn:

•A POTS dial peer for the primary number

•A POTS dial peer for the secondary number

•A POTS dial peer for the primary number as expanded by the dialplan-pattern command

•A POTS dial peer for the secondary number as expanded by the dialplan-pattern command

Call forwarding is normally applied to all dial peers created for an ephone-dn. Selective call forwarding allows you to apply call forwarding for busy or no-answer calls only for the dial peers you have specified, based on the called number that was used to route the call to the ephone-dn.

For example, the following commands set up a single ephone-dn (ephone-dn 5) with four dial peers:

telephony-service

dialplan-pattern 1 40855501.. extension-length 4 extension-pattern 50..

ephone-dn 5

number 5066 secondary 5067

via Cisco Unified Communications Manager Express System Administrator Guide – Configuring Call Transfer and Forwarding  [Cisco Unified Communications Manager Express] – Cisco Systems.

CME sip phone without “username” and “number”

Apr 6 01:58:35.400: TFTP: Looking for SIP0019AAACDF8A.cnf
Apr 6 01:58:35.400: TFTP: Opened flash:/SIP0019AAACDF8A.cnf, fd 7, size 773 for process 271
Apr 6 01:58:35.404: TFTP: Finished flash:/SIP0019AAACDF8A.cnf, time 00:00:00 for process 271
Apr 6 01:58:54.145: TFTP: Looking for CTLSEP001D45438DCD.tlv
Apr 6 01:58:54.297: TFTP: Looking for Ring1.raw
Apr 6 01:58:54.361: TFTP: Looking for SEP001D45438DCD.cnf.xml
Apr 6 01:58:54.361: TFTP: Opened flash:/SEP001D45438DCD.cnf.xml, fd 7, size 2629 for process 271
Apr 6 01:58:54.369: TFTP: Finished flash:/SEP001D45438DCD.cnf.xml, time 00:00:00 for process 271
Apr 6 01:59:03.497: TFTP: Looking for English_United_States/mk-sip.jar
Apr 6 01:59:03.997: TFTP: Looking for United_States/g3-tones.xml
Apr 6 01:59:04.685: TFTP: Looking for softkeyDefault_kpml.xml
Apr 6 01:59:04.685: TFTP: Opened flash:/softkeyDefault_kpml.xml, fd 7, size 3579 for process 271
Apr 6 01:59:04.717: TFTP: Finished flash:/softkeyDefault_kpml.xml, time 00:00:00 for process 271
Apr 6 01:59:06.557: TFTP: Looking for SIP0019AAACDF8A.cnf
Apr 6 01:59:06.557: TFTP: Opened flash:/SIP0019AAACDF8A.cnf, fd 7, size 773 for process 271
Apr 6 01:59:06.565: TFTP: Finished flash:/SIP0019AAACDF8A.cnf, time 00:00:00 for process 271
Apr 6 01:59:35.842: TFTP: Looking for CTLSEP001D45438DCD.tlv
Apr 6 01:59:35.986: TFTP: Looking for Ring1.raw
Apr 6 01:59:36.046: TFTP: Looking for SEP001D45438DCD.cnf.xml
Apr 6 01:59:36.046: TFTP: Opened flash:/SEP001D45438DCD.cnf.xml, fd 7, size 2629 for process 271
Apr 6 01:59:36.054: TFTP: Finished flash:/SEP001D45438DCD.cnf.xml, time 00:00:00 for process 271
Apr 6 01:59:37.726: TFTP: Looking for SIP0019AAACDF8A.cnf
Apr 6 01:59:37.726: TFTP: Opened flash:/SIP0019AAACDF8A.cnf, fd 7, size 773 for process 271
Apr 6 01:59:37.734: TFTP: Finished flash:/SIP0019AAACDF8A.cnf, time 00:00:00 for process 271

Phone booting process

1. CTLSEP MAC File—For example, CTLSEP003094C25D2E.tlv.
2. SEP MAC File—For example, SEP003094C25D2E.cnf.xml.
3. SIP MAC File—For example, SIP003094C25D2E.cnf.
4. MGCP MAC File—For example, MGC003094C25D2E.cnf.
5. XML Default File—For example, XMLDefault.cnf.xml.
6. SIP Default File—For example, SIPDefault.cnf.
7. MGCP Default File—For example, MGCDefault.cnf.

Call forwarding

Call forwarding does not work well (does not work at all) with sip endpoints on CME , connected with gatekeeper.

Some debugs below:

Call Activity Monitoring and Call History Logging

The Cisco Unified CME GUI provides call history table information so that a network administrator can monitor the call history information for unknown callers and use this information to disallow calling activities based on select calling patterns. The call history log should be configured to perform forensics and accounting and allow the administrator to track down fraudulent calling patterns. Configure the following commands to log call activity and call history:

dial-control-mib retain-timer 10080
dial-control-mib max-size 500
!
gw-accounting syslog

example

%VOIPAAA-5-VOIP_CALL_HISTORY: CallLegType 1, ConnectionId D3F36CC5 1E0D11DE 8BB78A89 A8F80E94, SetupTime 12:06:00.888 EST Wed Apr 1 2009, PeerAddress 18883621425, PeerSubAddress , DisconnectCause 10 , DisconnectText normal call clearing (16), ConnectTime 12:06:23.928 EST Wed Apr 1 2009, DisconnectTime 12:06:40.888 EST Wed Apr 1 2009, CallOrigin 1, ChargedUnits 0, InfoType 2, TransmitPackets 1909, TransmitBytes 38180, ReceivePackets 1907, ReceiveBytes 38140

Lab #1

Register phones according to table 1 of http://bitswap.wordpress.com/2009/03/25/t/

1D 7940 as SIP on CME1
43 7960+7914 as SCCP on CME1
CD 7961 as SIP on CME2
8A 7940 as SCCP on CME2
E7 7960 as SIP on CM
9B 7960 as SIP on CM
31 7941 as SCCP on CM

Test call completion, calling/ed name presentation , issues
CM1->CM2(forwarded to neighbor)
CM1->CM2(forwarded to CM1)
CM1->CM2(forwarded to CM)

CM->CM2(forwarded to neighbor)
CM->CM2(forwarded to CM1)
CM->CM2(forwarded to CM2)

Connect CM & CME via H323 trunk (full mesh)
Test call completion, calling/ed name presentation , issues

1. Default configuration.
2. H.450 extension turned on

Connect CM & CME via gatekeeper-controlled H.323 trunk
1. Default configuration.
2. H.450 extension turned on

Connect CM & CME SIP trunk(full mesh)
1. Default configuration.
2. REFER off

Connect CM & CME via ip-ip gateway (SIP)
1. Default configuration.

CME with SIP and SKINNY phones

• 7960 firmware P0S3-07-5-00 does NOT work with cme 7.0(1) (Phone doesn’t recognize “USECALLMANAGER” item in SIPDefault.cn
• 7960 firmware P0S3-08-6-00 does work with cme 7.0(1)
• CME & SIP implementation guide