Archive for July, 2010

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.

Advertisements

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!

This is just notes to myself as after downloading the upgrade files for CUCM or Unity or anything else…we all need to follow the same process of combining them and then verifiying the hash value.

Download FCIV.

Download the files as required:

UCS_Install_UCOS_7.1.3.32900-4.sgn.iso_part1of2

UCS_Install_UCOS_7.1.3.32900-4.sgn.iso_part2of2

Run the following command to combine these files into one .iso file

COPY /B C:\UCS_Install_UCOS_7.1.3.32900-4.sgn.iso_part1of2+C:\UCS_Install_UCOS_7.1.3.32900-4.sgn.iso_part2of2 C:\UCSInstall_UCOS_7.1.3.32900-4.sgn.iso

UCSInstall_UCOS_7.1.3.32900-4.sgn.iso

Use a checksum generator to confirm that the MD5 checksum of the reunited file matches the following checksum:

d450666dafbc8f01c111ed0158f748fb

If the values do not match, the reunited file is damaged.

C:\>cd fciv

C:\FCIV>fciv.exe c:\UCSInstall_UCOS_7.1.3.32900-4.sgn.iso
//
// File Checksum Integrity Verifier version 2.05.
//
d450666dafbc8f01c111ed0158f748fb c:\ucsinstall_ucos_7.1.3.32900-4.sgn.iso

C:\FCIV>

Note: Make sure if you are writing it over a CD/DVD then it should be copied as Data and don’t expand it as an image. The file on the CD/DVD should be a .iso file as Call manager only looks for this file.

Now you can run the upgrade process either from OS Admin or CLI. I prefer CLI but any method can be used.

Disable throttle to speed up the process, Throttling prevents call processing degradation during the upgrade but may cause the upgrade to take longer. Throttling gets enabled by default and is necessary if you perform the upgrade during normal business hours.

Upgrade Process from CLI:

First of all disable ios throttle by using command utils iothrottle disable. If it’s not disabled at start, you will be asked during the upgrade as well where you may or may not disable it.

admin:show version active
Active Master Version: 7.1.2.20000-2

Active Version Installed Software Options:
uc-locale-en_GB-7.1.2.0-139.cop
admin:

admin:utils system
utils system boot*
utils system restart
utils system shutdown
utils system switch-version
utils system upgrade*

admin:utils system upg
admin:utils system upgrade ini
admin:utils system upgrade initiate

Warning: Do not close this window without first exiting the upgrade command.

To preserve system stability during upgrades, the system throttles the upgrade process, which may take considerably longer to complete.  If you are performing this upgrade during a maintenance window and want to speed up the upgrade, you can disable throttling.  Additional information is in the Special Upgrade Information section of the release notes.

Would you like to disable I/O throttling (yes/no): yes

Source:

1) Remote Filesystem
2) DVD/CD
q) quit

Please select an option (1 – 2 or “q” ): 1
Directory: \
Server: 10.9.1.3
User Name: cisco
Password: *****
Protocol:

1) sftp
2) ftp
q) quit

Please select an option (1 – 2 or “q” ): 1
Checking for valid upgrades.  Please wait…

Available options and upgrades in “10.9.1.3:\”:

1) UCSInstall_UCOS_7.1.3.32900-4.sgn.iso
q) quit

Please select an option (1 – 1 or “q” ): 1
Accessing the file.  Please wait…

[KDownloaded 2 MB. [KDownloaded 5 MB. [KDownloaded 8 MB. [KDownloaded 11 MB.
[KDownloaded 15 MB. [KDownloaded 18 MB.[KDownloaded 21 MB.[KDownloaded 24 MB.
[KDownloaded 27 MB.[KDownloaded 31 MB.[KDownloaded 34 MB.[KDownloaded 37 MB.
[KDownloaded 40 MB.[KDownloaded 43 MB.[KDownloaded 45 MB.[KDownloaded 48 MB.

.

.

KDownloaded 3206 MB.[KDownloaded 3209 MB.[KDownloaded 3211 MB.[KDownloaded 3214 MB.
[KDownloaded 3216 MB.[KDownloaded 3219 MB.[KDownloaded 3222 MB.[KDownloaded 3225 MB.
[KDownloaded 3227 MB.[KDownloaded 3230 MB.[KDownloaded 3233 MB.[KDownloaded 3236 MB.

Checksumming the file…

KDownloaded 3236 MB.File validated.

A system reboot is required when the upgrade process completes or is canceled.  This will ensure services affected by the upgrade process are functioning properly.

Downloaded: UCSInstall_UCOS_7.1.3.32900-4.sgn.iso
File version: 7.1.3.32900-4
File checksum: d4:50:66:6d:af:bc:8f:01:c1:11:ed:01:58:f7:48:fb

Automatically switch versions if the upgrade is successful (yes/no): no

Start installation (yes/no): yes
The upgrade log is install_log_2010-08-26.10.41.10.log
Upgrading the system.  Please wait…
08/26/2010 10:41:10 file_list.sh|Starting file_list.sh|<LVL::Info>
08/26/2010 10:41:10 file_list.sh|Parse argument method=sftp|<LVL::Debug>
08/26/2010 10:41:10 file_list.sh|Parse argument source_dir=\|<LVL::Debug>
08/26/2010 10:41:10 file_list.sh|Parse argument dest_file=/var/log/install/downloaded_versions|<LVL::Debug>
08/26/2010 10:41:10 file_list.sh|Parse argument remote_host=10.9.1.3|<LVL::Debug>
08/26/2010 10:41:10 file_list.sh|Parse argument user_name=cisco|<LVL::Debug>
08/26/2010 10:41:10 file_list.sh|Calling SFTP command with metering off|<LVL::Debug>
08/26/2010 10:41:11 file_list.sh|SFTP command complete (0)|<LVL::Debug>
08/26/2010 10:41:11 file_list.sh|List file (pre-filtered):|<LVL::Debug>
08/26/2010 10:41:11 file_list.sh|(CAPTURE) UCSInstall_UCOS_7.1.3.32900-4.sgn.iso|<LVL::Debug>

.

.

08/26/2010 12:18:22 upgrade_install.sh|CSA Status = 0|<LVL::Debug>
08/26/2010 12:18:22 upgrade_install.sh|/etc/init.d/ciscosec start|<LVL::Info>
08/26/2010 12:18:24 upgrade_install.sh|(CAPTURE) Starting ciscosec:  [  OK  ]|<LVL::Debug>
08/26/2010 12:18:24 upgrade_install.sh|IOWAIT monitor stopped|<LVL::Info>
08/26/2010 12:18:24 upgrade_install.sh|0|<LVL::Debug>
08/26/2010 12:18:24 upgrade_install.sh|Upgrade Complete — (0)|<LVL::Info>

Successfully installed UCSInstall_UCOS_7.1.3.32900-4.sgn.iso

The system upgrade was successful.  Please switch versions to activate the upgrade or reboot the system to ensure services affected by the upgrade process are functioning properly.

admin:

admin:

admin:utils system swi
admin:utils system switch-version

Active Master Version: 7.1.2.20000-2

Inactive Master Version: 7.1.3.32900-4

If you are switching to an earlier release, you must run:

utils dbreplication reset all

from the publisher after all the nodes are switched over.

Do you really want to switch between versions ?

Enter (yes/no)? yes

Switching Version and Restarting the Appliance …

Switch version duration can vary depending on the database size
and platform configuration.  Please continue to monitor the
switchover process from here.

Waiting …………………………………………………………………………………………………………………………..

Broadcast message from root (Thu Aug 26 12:30:09 2010):

The system is going down for reboot NOW!

.

Operation succeeded

RESTART NOW!
admin:

After this restart the server@

admin: utils system restart

Once it come  back up, check the services

admin:utils service list

{ The box I was upgrading was a Subscriber so I had to make sure if replication is all f ine }

Pub:

admin:file view activelog cm/trace/dbl/sdi/ReplicationStatus.2010_08_26_15_38_33.out

SERVER                 ID STATE    STATUS     QUEUE  CONNECTION CHANGED
———————————————————————–
g_darcuc_ccm7_1_3_32900_4    2 Active   Local           0
g_goscuc_ccm7_1_3_32900_4    3 Active   Connected       0 Aug 26 15:34:16

————————————————-

No Errors or Mismatches found.
Replication status is good on all available servers.

admin:
admin:
admin:show perf query class “Number of Replicates Created and State of Replication”
==>query class :

– Perf class (Number of Replicates Created and State of Replication) has instances and values:
ReplicateCount  -> Number of Replicates Created   = 427
ReplicateCount  -> Replicate_State                = 2

Sub:

admin:utils dbreplication status

——————– utils dbreplication status ——————–

Replication status check is now running in background.
Use command ‘utils dbreplication runtimestate’ to check its progress

The final output will be in file cm/trace/dbl/sdi/ReplicationStatus.2010_08_26_15_39_17.out

Please use “file view activelog cm/trace/dbl/sdi/ReplicationStatus.2010_08_26_15_39_17.out ” command to see the output
admin:file view activelog cm/trace/dbl/sdi/ReplicationStatus.2010_08_26_15_39_17.out

SERVER                 ID STATE    STATUS     QUEUE  CONNECTION CHANGED
———————————————————————–
g_darcuc_ccm7_1_3_32900_4    2 Active   Connected       0 Aug 26 15:34:16
g_goscuc_ccm7_1_3_32900_4    3 Active   Local           0

————————————————-
No Errors or Mismatches found.
Replication status is good on all available servers.

options: q=quit, n=next, p=prev, b=begin, e=end (lines 1 – 20 of 20) :
admin:
admin:
admin:
admin:show perf query class “Number of Replicates Created and State of Replication”
==>query class :

– Perf class (Number of Replicates Created and State of Replication) has instances and values:
ReplicateCount  -> Number of Replicates Created   = 427
ReplicateCount  -> Replicate_State                = 2

If the count is ‘3’ then you may have replication issues. Follow the steps to resolve replication issues:

  • Utils debreplication stop on Subscriber
  • Utils debreplication stop on Publisher (once you stopped Subscriber)
  • Utils dbreplication reset all (from Publisher)
  • If needed restart Subscriber

This will fix the issue. Sometimes I did came across a misleading message after repairing replication. It was like:

admin:utils dbreplication reset all
Replication reset is in progress. Replication setup will continue in background.
Please watch RTMT replication state on all nodes. It should go from 0 to 2.
When all subs have an RTMT Replicate State of 2, replication setup is complete.
If RTMT Replicate State shows 4, there is an error in replication setup.
DbMon correctly signalled
command failed — Enterprise Replication not active (62)

command failed — Enterprise Replication not active (62)

If you come across this, there is no reason to get panic. It’s a Cisco Bug CSCso82088.

The replication has been successful. You can use the above perf query commands to verify replication status. It should be ‘2’ for good replication.


If replication status still not synches try this:

utils dbreplication stop on sub wait for it to stop.
utils dbreplication stop on pub.

utils dbreplication dropadmindb on pub, wait for syscdr to drop.

utils dbreplication dropadmindb on sub.

Once that is done utils dbreplication reset all from pub.

Another useful command to check replication:

admin:utils dbreplication runtimestate

DB and Replication Services: ALL RUNNING

Cluster Replication State: Only available on the PUB

DB Version: ccm7_1_3_32900_4
Number of replicated tables: 427

Cluster Detailed View from SUB (2 Servers):

PING            REPLICATION     REPL.   DBver&  REPL.   REPLICATION SETUP
SERVER-NAME     IP ADDRESS      (msec)  RPC?    STATUS          QUEUE   TABLES  LOOP?   (RTMT)
———–     ————    ——  —-    ———–     —–   ——- —–   —————–
DAR  172.22.6.x    0.352   Yes     Connected       0       match   N/A     (2)
GOS  172.22.5.x    0.026   Yes     Connected       0       match   N/A     (2)

admin:

To check Database Integrity:

show cuc dbconsistency unitydirdb

show cuc tech dbserver integrity

 

Useful Commands for Cluster:

Show tech network hosts

Show network cluster

Show tech dbstateinfo

utils diagnose test

utils network hosts

utils network host xxxxx – you can put the name of the CCM server which will resolve to ip address. if you put ip address this will give you the name of the server. This will prove that DNS is working correctly.

 

I was looking into this issue for a customer where a Conference phone, Cisco 7936, was not registering to Call manager.

When I looked the MAC address of it in Call manager, it was in the status of ‘unregistered’ and there was an IP address assigned to it as well.

This suggests that it somehow reached to Call manager but then got unregistered OR this phone was registered to Call manager some time in back.

There were some other 7936 phones as well which were all registered fine.

I asked them to do a factory reset of the 7936 phone which they did but no joy. After that I asked them to disable DHCP and manually assign TFTP address but even that didn’t resolve the issue. Phone was stuck in a loop ‘TFTP server not found’.

Surprising bit was that both Call manager and Phone could ping each other that means there was no network issue. I asked them to hook another 7936 to the same port to see if that makes any difference. The other 7936 phone got registered fine. This proved the port was also fine.

I decided to jump onto the access switch where this phone is connected and see what messages it is sending. That proved a nightmare as we only had information regarding their main Inbound/outbound gateway. I had to track it down all the way from that gateway to distribution switches to that one particular access switch which was showing this MAC address connected to its port. I ran commands like debug tftp events and debug tftp packet but I didn’t see any response from the phone.

Frustrated I was, decided to google the issue. I found out that it’s a bug which has been hitting this phone.

Bug id# CSCsg95361

Symptom:
7936 phones fail to upgrade to a different load when upgrade is attempted immediately after re-registration to CCM. This situation happens when the phones unregister first due to callmanager getting restarted or upgraded.

Conditions:
The 7936 phones running either cmterm_7936.3-3-1-0.bin or cmterm_7936.3-3-2-0.bin loads can fail to upgrade to new load if the phones first unregister from CCM, followed by re-registration and firmware upgrade attempt.

Workaround:
Change the default load on the CCM to cmterm_7936.3-3-3-0.bin or newer and upgrade the 7936 phones without stopping CCM service first. If the phones experience this problem due to proactive workaround not performed, power cycling the phone recovers them in most cases.

In my case, nothing resolved the issue so I asked the customer to raise a RMA request with Cisco.

Also read this Field notice:

http://tinyurl.com/36uhpna

You may come across a situation where you need to reset the password Unity Admin.

You can do it through command prompt:

Microsoft Windows [Version 5.2.3790]

(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator>cd …

C:\Documents and Settings\Administrator>g:

G:\>cd Cisco Unity Connection\TechTools

G:\Cisco Unity Connection\TechTools>pwreset.bat uksupport p36lmn

G:\Cisco Unity Connection\TechTools\pwreset.js(17, 5) Microsoft OLE DB Provider

for SQL Server: The credential matches a previous credential for this user.

G:\Cisco Unity Connection\TechTools>pwreset.bat uksupport Bfnm.lk

G:\Cisco Unity Connection\TechTools\pwreset.js(17, 5) Microsoft OLE DB Provider

for SQL Server: The credential matches a previous credential for this user.

G:\Cisco Unity Connection\TechTools>pwreset.bat uksupport Bfnm.kl@P

Password has been set.

G:\Cisco Unity Connection\TechTools>

If there is already a MOH file running at the CME router, follow the below steps to change it to a new one.

Sh flash:

55        7200 Dec 09 2008 10:53:52 Pulse1.raw
56        4000 Dec 09 2008 10:53:54 Ring1.raw
57        4000 Dec 09 2008 10:53:54 Ring2.raw
58        4000 Dec 09 2008 10:53:54 Ring3.raw
59        4000 Dec 09 2008 10:53:54 Ring4.raw
60        4000 Dec 09 2008 10:53:56 Ring5.raw
61        4000 Dec 09 2008 10:53:56 Ring6.raw
62        4000 Dec 09 2008 10:53:56 Ring7.raw
63         495 Dec 09 2008 10:53:56 RingList.xml
64       10800 Dec 09 2008 10:53:58 Sax1.raw
65       14160 Dec 09 2008 10:53:58 Sax2.raw
66       16080 Dec 09 2008 10:53:58 Vibe.raw
67           0 Jan 05 2009 13:28:42 configs
68       21903 Jan 05 2009 13:29:24 configs/config-050109-upgrade
69     1209168 May 19 2010 15:34:26 MOH2010.wav
70     1219613 Jun 08 2010 14:45:44 Delawarenew.wav

telephony-service
sdspfarm units 4
sdspfarm tag 1 CFP001e7a78c7d0
conference hardware
no auto-reg-ephone
load 7936 cmterm_7936.3-3-15-0
load 7941 SCCP41.8-3-3S
load 7961 SCCP41.8-3-3S
max-ephones 42
max-dn 144
ip source-address 10.95.254.3 port 2000
timeouts interdigit 5
network-locale GB
time-zone 21
date-format dd-mm-yy
voicemail 35090
max-conferences 8 gain -6
call-forward pattern .T
call-forward system redirecting-expanded
moh flash:Delawarenew.wav
multicast moh 239.0.2.1 port 2000 route 10.95.254.3

dn-webedit
time-webedit
transfer-system full-consult
transfer-pattern 9.T
secondary-dialtone 9

Upload the file:

1.       Copy the music file onto the flash of the router by using

command to run at the router # copy tftp://x.x.x.x/new_file.wav flash:

2.       Enable

3.       Conf terminal

4.       telephony-service

5.       no moh flash:Delawarenew.wav

6.       moh MOHJuly2010.wav

7.       multicast moh 239.1.1.1 port 2000

8.       create cnf-files

9.       exit

Verify:

UK-CME#sh ephone summ

hairpin_block:
ephone-1[0] Mac:001E.138C.D8D8 TCP socket:[9] activeLine:0 REGISTERED
mediaActive:0 offhook:0 ringing:0 reset:0 reset_sent:0 debug:0  primary_dn: 20*
IP:10.95.254.116 7961  keepalive 63119  1:20 2:1 3:3
sp1:35089 sp2:907789690073#

ephone-2[1] Mac:0021.A087.2538 TCP socket:[20] activeLine:0 REGISTERED
mediaActive:0 offhook:0 ringing:0 reset:0 reset_sent:0 debug:0  primary_dn: 134*
IP:10.95.254.125 7941  keepalive 176020  1:134

ephone-3[2] Mac:001D.A266.CD0B TCP socket:[4] activeLine:0 REGISTERED
mediaActive:0 offhook:0 ringing:0 reset:0 reset_sent:0 debug:0  primary_dn: 3*
IP:10.95.254.111 7961  keepalive 170599  1:3 2:18
sp1:35076 sp2:35066 sp3:35068 sp4:35065

.

.

.

.

.

Max Conferences 8 with 0 active (8 allowed)
Skinny Music On Hold Status
Active MOH clients 0 (max 210), Media Clients 0, B-ACD Clients 0
File flash:MOHJuly2010.wav type WAVE Media_Payload_G711Ulaw64k  160 bytes
Moh multicast on 239.0.2.1 port 2000 via 10.95.254.3

Customer reported an issue with their MWI. They were using Unity connection 7.0(1).

When a new message was left, the MWI light will not come up so there was no way to tell if a new message has arrived. User were logging into their mailboxes to check if there are new messages. Also, if there were more than two new messages and they delete one of them, MWI light was coming up. The issue was intermittent. Sometimes it works fine, sometimes it doesn’t.

I checked the configuration at Call manager which looks fine. The fact that it was intermittent suggested there is no CSS/PT issue. I went into Unity connection servers (they were using two Active/Active UC servers) and re-sync the MWI. It solved the issue for few but not for all. I then decided to investigate the logs of Unity connection server.

For MWI, you need to go into Macro traces and turn on SCCP phone MWI. After doing that I collected traces from RTMT for Connection conversation Manager & Connection Notifier. Going through the traces for a known duration for extension 334, I found below:

/27/2010 11:12:14.713 |14264,,,Notifier,12,CCsDeviceTask::LoadBasicInfoFromNamedProps found result context: ‘(null)’|
07/27/2010 11:12:14.713 |14264,,,Notifier,12,CCsDeviceTask::LoadBasicInfoFromNamedProps found switch objectid: ‘618bf9a6-7fbf-4cb8-87ba-ed03796b6e86’|
07/27/2010 11:12:14.713 |14264,,,Notifier,12,Error getting value of named property MsgID for Ewan McDonald. HRESULT:80004005|
07/27/2010 11:12:14.713 |14264,,,Notifier,12,CCsMWIDevice::TransferPropertiesToTask found mwi on/off type 1|
07/27/2010 11:12:14.713 |14264,,,Notifier,12,CCsMWIDevice::TransferPropertiesToTask found mwi extension ‘334’|
07/27/2010 11:12:14.713 |14264,,,Notifier,12,CCsMWIDevice::TransferPropertiesToTask found mwi port object id ”|
07/27/2010 11:12:14.713 |14264,,,Notifier,12,CCsMWIDevice::TransferPropertiesToTask found mwi object id ‘a575e681-7481-42fa-b8bd-bdc3a266dbd3’|
07/27/2010 11:12:14.713 |14264,,,Notifier,12,CCsMWIDevice::TransferPropertiesToTask found suspend update flag 0|
07/27/2010 11:12:14.713 |14264,,,Notifier,12,CCsMWIDevice::TransferPropertiesToTask found always update flag 1 (when true will send message counts)|
07/27/2010 11:12:14.713 |14264,,,Notifier,12,CCsDeviceTask::LoadBasicInfoFromNamedProps found urgent voice count: 0|
07/27/2010 11:12:14.713 |14264,,,Notifier,12,CCsDeviceTask::LoadBasicInfoFromNamedProps found urgent fax count: 0|
07/27/2010 11:12:14.713 |14264,,,Notifier,12,CCsDeviceTask::LoadBasicInfoFromNamedProps found saved voice count: -2|
07/27/2010 11:12:14.713 |14264,,,Notifier,12,CCsDeviceTask::LoadBasicInfoFromNamedProps found saved fax count: 0|
07/27/2010 11:12:14.713 |14264,,,Notifier,12,CCsDeviceTask::LoadBasicInfoFromNamedProps found saved urgent voice count: 0|
07/27/2010 11:12:14.713 |14264,,,Notifier,12,CCsDeviceTask::LoadBasicInfoFromNamedProps found saved urgent fax count: 0|
07/27/2010 11:12:14.713 |14264,,,Notifier,12,Queued MWI task=[user=’Ewan McDonald’ extension=’334′ type=RESYNC_MWI_OFF mwiType=0=Port phoneSystem=Cisco Call Manager (618bf9a6-7fbf-4cb8-87ba-ed03796b6e86)]|
07/27/2010 11:12:14.714 |12862,,,Arbiter,13,Port 3=Cisco Call Manager PG1-015 has been reserved|
07/27/2010 11:12:14.714 |14264,,,Notifier,20,Ticket d17e0001 request made for resource -1 (switch=0 caps=4) for Task Ewan McDonald  taskid 29129|
07/27/2010 11:12:14.714 |14264,,,Notifier,20,Ticket d17e0001 pending for requested resource -1|
07/27/2010 11:12:14.714 |12862,,,Notifier,20,Ticket d17e0001 found for requested resource -1|
07/27/2010 11:12:14.714 |12862,,,Notifier,20,Ticket d17e0001 granted for resource 3 (requested -1)|
07/27/2010 11:12:14.714 |12874,,,Notifier,12,Execute MWI port=3 task=[user=’Ewan McDonald’ extension=’334′ type=RESYNC_MWI_OFF mwiType=0=Port phoneSystem=Cisco Call Manager (618bf9a6-7fbf-4cb8-87ba-ed03796b6e86)]|
07/27/2010 11:12:14.715 |12874,,,Arbiter,13,Setting port Cisco Call Manager PG1-015 active=Yes activeRefs=0|
07/27/2010 11:12:14.715 |12874,,,Arbiter,13,Switch 0=Cisco Call Manager portCounts change [portsFree=9 answerPorts=8 answerPortsFree=8] to [portsFree=8 answerPorts=8 answerPortsFree=8]|
07/27/2010 11:12:14.715 |12874,,,Arbiter,13,PerfCounters: port modified [name=’Cisco Call Manager PG1-015′ inService=true active=false deleted=false]->[name=’Cisco Call Manager PG1-015′ inService=true active=true deleted=false]|
07/27/2010 11:12:14.715 |12874,,,Arbiter,13,PerfInterval end eUNITY_PERFCTRPHONESYS_PORTIDLEDURATION ID=’PortIdle-21361154-027d-418b-a857-733120514c90′ instance=” [stopping counter]|
07/27/2010 11:12:14.715 |12874,,,Arbiter,13,PerfInterval start eUNITY_PERFCTRPHONESYSPORT_PORTUSAGEDURATION ID=’PortBusy-21361154-027d-418b-a857-733120514c90′ instance=’Cisco Call Manager PG1-015′ [starting counter]|
07/27/2010 11:12:14.715 |12874,,,Arbiter,13,SetPortActive: port=Cisco Call Manager PG1-015 ID=3 switch=Cisco Call Manager (ID=0) available=No caps=0x7c->Enabled|MWI|Notification |
07/27/2010 11:12:14.715 |12874,,,Arbiter,13,PortActivity, MWI Dial out, Port No: Cisco Call Manager PG1-015, Lines in use: 1, Lines available for taking calls: 8|
07/27/2010 11:12:14.716 |12874,,,MiuGeneral,26,Enter EnterThrottle |
07/27/2010 11:12:14.716 |12874,,,MiuGeneral,26,MWIThrottle: wait for concurrent request completion -> state: numQueuedMinInterval=0 numQueuedMaxConcurrent=1 numInProgress=0 maxConcurrentMwi=4 minMwiInterval=0|
07/27/2010 11:12:14.716 |12874,,,MiuGeneral,26,MWIThrottle: done waiting for concurrent request completion|
07/27/2010 11:12:14.716 |12874,,,MiuGeneral,26,MWIThrottle complete -> state: numQueuedMinInterval=0 numQueuedMaxConcurrent=0 numInProgress=1 maxConcurrentMwi=4 minMwiInterval=0|
07/27/2010 11:12:14.716 |12874,,,MiuGeneral,26,Exit EnterThrottle=0x00000000=S_OK|

Something was not normal. I could see message count in negative.

I decided to jump on Call manager and get some traces from there as well to find out what Call manager did after getting MWI request.

This is what I found in CCM traces.

07/27/2010 11:10:55.964 CCM|MGCPHandler received msg from: 172.22.1.252
NTFY 690173580 *@DARVG01. MGCP 0.1
X: 0
O:
|<CLID::StandAloneCluster><NID::172.22.1.253><CT::2,100,134,1.2080654><IP::172.22.1.252><DEV::><LVL::Significant><MASK::2000>
07/27/2010 11:10:55.965 CCM|<CLID::StandAloneCluster><NID::172.22.1.253><CT::2,100,134,1.2080654><MN::MGCPEndPoint><MV::*><DEV::><LVL::All><MASK::ffff>
07/27/2010 11:10:55.965 CCM|MGCPHandler send msg SUCCESSFULLY to: 172.22.1.252

/27/2010 11:12:14.591 CCM|StationD:    (0042516) KeypadButton KeyPadButton=3(Three).|<CLID::StandAloneCluster><NID::172.22.1.253><CT::2,100,39,1.223562436><IP::172.22.0.47><DEV::SEP001D457DCFFD><LVL::State Transition><MASK::0020>
07/27/2010 11:12:14.678 CCM|CMProcMon – ——Entered Router Verification|<CLID::StandAloneCluster><NID::172.22.1.253><LVL::Arbitrary><MASK::0800>
07/27/2010 11:12:14.678 CCM|CMProcMon – —-Exited Router Verification|<CLID::StandAloneCluster><NID::172.22.1.253><LVL::Arbitrary><MASK::0800>
07/27/2010 11:12:14.741 CCM|StationInit: (0042502) StationMwiNotificationMessage mwiTarget=334 mwiCtrl=88997 msgsWaiting=0 totalVm(0/-2) priVm(0/0) totalFax(0/0) priFax(0/0)|<CLID::StandAloneCluster><NID::172.22.1.253><CT::2,100,39,1.223562438><IP::172.22.1.251><DEV::CiscoUM1-VI15><LVL::State Transition><MASK::0020>
07/27/2010 11:12:14.741 CCM|StationD:    (0042502) TX StationMwiResponse: mwiTarget=334 result=3.|<CLID::StandAloneCluster><NID::172.22.1.253><CT::2,100,39,1.223562438><IP::172.22.1.251><DEV::CiscoUM1-VI15><LVL::Detailed><MASK::0800>
07/27/2010 11:12:14.741 CCM|StationD:    (0042502) StationMwiNotification is rejected due to invalid msg count.|<CLID::StandAloneCluster><NID::172.22.1.253><CT::2,100,39,1.223562438><IP::172.22.1.251><DEV::CiscoUM1-VI15><LVL::Significant><MASK::0800>

Confirmed from Call manager traces that message count is indeed in negative which call manager is rejecting saying ‘invalid message count’.

I dig deep to find out the Unity connection famous Bugs:

– CSCsy17809 : Message count may go negative if same message deleted simultaneously

– CSCtc32553 : unity connection 7.x negative mailbox size diagnostics

Symptom:

When a message is accessed and deleted at the exact same time in more than one place, the current message count may drop below zero. Therefore a new message left may not light MWI (until enough new messages exist for the message count to be greater than zero again).

Bug Link:

http://tinyurl.com/33q5msr

A temporary workaround is to run the following command from Unity connection CLI (Admin rights)

"run cuc dbquery unitymbxdb1 execute procedure csp_MailboxesRefreshSize()"

A permanent fix is to upgrade to CUC 7.1(3).

I have a virtual machine where I have several RTMT versions installed. I use it whatever suits customer version.

Today came across an interesting situatuation when my Unity RTMT didn’t work.  I decided to download the plugin and install it fresh.  All went fine until I ran the installation. I was getting this error:

RTMT version already installed and you cannot have same version blah blah..

I went into the Add/remove program and uninstalled the RTMT. All good.

I then went to Programs > Cisco > CallManager Serviceability > Unsinstall RTMT 8.1

Got an error > Cannot locate the uninstall file.

I was kind of stuck,  I had to run the RTMT and my RTMT was not working. I statred looking for it on the internet but no joy.

After spending some time on the Internet I found the solution posted by a TAC.  This fixed the issue.

I thought it’s worth Sharing.

Go to C:/Program Files/ Zero G Registry open the file “.com.zerog.registry.xml” in a text editor. It’s a hidden folder so make sure you view hidden files/folders as well.

Open the file ‘.com.zerog.registry.xml’  in a wordpad and remove the entries correspondonding to RTMT 8.1. Make sure you remove within the XML tags.

I had this output from that file:

<?xml version="1.0" encoding="UTF-8" ?>
- <registry install_date="2010-06-28 10:49:42" version="1.1" last_modified="2010-07-23 

11:44:03">
- <products>
- <product name="Real-Time Monitoring Tool 8.1" id="764ff1c4-1ee5-11b2-a2b1-9ff21e0a5268" 

version="8.1.0.0" copyright="2008" info_url="" support_url="" location="C:\Unity 

Connection" last_modified="2010-06-28 10:49:42">
 <vendor name="" id="764ff1c3-1ee5-11b2-a2b1-9ff21e0a5268" home_page="" email="" />
- <feature name="Application" last_modified="2010-06-28 10:49:42">
- <![CDATA[ This installs the application feature.
 ]]>
 <component ref_id="764ff221-1ee5-11b2-a2cc-9ff21e0a5268" version="8.1.0.0" 

location="C:\Unity Connection\Uninstall_Real-Time Monitoring Tool 8.1\Uninstall Real-Time 

Monitoring Tool 8.1.exe" />
 <component ref_id="09316d9f-1eef-11b2-96a7-8c96050bbc8d" version="8.1.0.0" 

location="C:\Unity Connection\JRtmt.exe" />
 <component ref_id="764ff222-1ee5-11b2-a2ce-9ff21e0a5268" version="8.1.0.0" 

location="C:\Unity Connection\jre" />
 </feature>
 </product>
 </products>
- <components>
 <component id="09316d9f-1eef-11b2-96a7-8c96050bbc8d" version="8.1.0.0" name="Rtmt Common" 

location="C:\Unity Connection\JRtmt.exe" />
 <component id="764ff222-1ee5-11b2-a2ce-9ff21e0a5268" version="8.1.0.0" 

name="InstallAnywhere VM Component" location="C:\Unity Connection\jre" />
 <component id="764ff221-1ee5-11b2-a2cc-9ff21e0a5268" version="8.1.0.0" 

name="InstallAnywhere Uninstall Component" location="C:\Unity Connection\Uninstall_Real-

Time Monitoring Tool 8.1\Uninstall Real-Time Monitoring Tool 8.1.exe" />
 </components>
 </registry>

This is what I did:

<?xml version="1.0" encoding="UTF-8"?>
<registry install_date="2010-06-28 10:49:42" version="1.1" last_modified="2010-07-23 11:54:19">
 <products>
 </products>
 <components>
 </components>
</registry>

 

This was an interesting issue one of my colleague at work came across.

Customer called and said they cannot transfer calls to mobile number. He can make calls to mobile number fine but when he was transferring an external (PSTN) call to mobile number, the call drops immediately. Transfer to any local or national number works perfectly fine.

External caller Mr. A (PSTN) ———— > Ext 114 —— > Hold —-> dial mobile number —- > Speaks to mobile caller —– > Hit transfer Key —— > Call drops

First of all I checked the service parameter Block OffNet To OffNet Transfer which has a default value of false but I made sure it is false. If we set it to true then transfer to any external number won’t work.

Next bit, I checked if it’s a dsp issue. Found out that their Voice traffic is quite high with almost 19-20 channels always busy out of 21 channels. I thought may be at the time of transfer the call is not getting a channel available to place call and hence dropping. I called him, asked to make a call to mobile number while I started running isdn q931 debugs.


This is the call I made from my PSTN phone to Customer extension

Jul 19 16:01:58.808: ISDN Se0/0/0:15 Q931: RX <- SETUP pd = 8  callref = 0x0008
Sending Complete
Bearer Capability i = 0x8090A3
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98388
Exclusive, Channel 8
Calling Party Number i = 0x2181, ‘XXXXXX1395’
Plan:ISDN, Type:National
Called Party Number i = 0x81, ‘214029’

Plan:ISDN, Type:Unknown
*Jul 19 16:01:58.824: ISDN Se0/0/0:15 Q931: TX -> CALL_PROC pd = 8  callref = 0x8008
Channel ID i = 0xA98388
Exclusive, Channel 8
*Jul 19 16:01:58.944: ISDN Se0/0/0:15 Q931: TX -> ALERTING pd = 8  callref = 0x8008
Progress Ind i = 0x8188 – In-band info or appropriate now available
*Jul 19 16:01:59.144: ISDN Se0/0/0:15 Q931: TX -> CONNECT pd = 8  callref = 0x8008
*Jul 19 16:01:59.212: ISDN Se0/0/0:15 Q931: RX <- CONNECT_ACK pd = 8  callref = 0x0008

Call connected successfully (callref = 0x0008)

OEH-VG-01#
OEH-VG-01#
*Jul 19 16:01:59.216: %ISDN-6-CONNECT: Interface Serial0/0/0:7 is now connected to XXXXXX1395 N/A
*Jul 19 16:01:59.216: %ISDN-6-CONNECT: Interface Serial0/0/0:7 is now connected to XXXXXX1395 N/A
*Jul 19 16:01:59.216: %ISDN-6-CONNECT: Interface Serial0/0/0:7 is now connected to XXXXXX1395 N/A
OEH-VG-01#
OEH-VG-01#
OEH-VG-01#
OEH-VG-01#
OEH-VG-01#
OEH-VG-01#
OEH-VG-01#
OEH-VG-01#
*Jul 19 16:02:05.216: %ISDN-6-CONNECT: Interface Serial0/0/0:7 is now connected to XXXXXX1395 N/A
OEH-VG-01#
OEH-VG-01#
OEH-VG-01#
OEH-VG-01#
OEH-VG-01#
OEH-VG-01#
OEH-VG-01#
OEH-VG-01#
OEH-VG-01#
OEH-VG-01#

While putting me on hold, customer dials mobile number and call is established (callref = 0x929E)

*Jul 19 16:02:28.708: ISDN Se0/0/0:15 Q931: Applying typeplan for sw-type 0x12 is 0x0 0x0, Calling num 4000
*Jul 19 16:02:28.712: ISDN Se0/0/0:15 Q931: Applying typeplan for sw-type 0x12 is 0x0 0x0, Called num 0787XXXXXXX
*Jul 19 16:02:28.712: ISDN Se0/0/0:15 Q931: TX -> SETUP pd = 8  callref = 0x129E
Bearer Capability i = 0x8090A3
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98395
Exclusive, Channel 21
Calling Party Number i = 0x00A1, ‘4000’ <<< Outgoing calls
Plan:Unknown, Type:Unknown
Called Party Number i = 0x80, ‘0787XXXXXXX’
Plan:Unknown, Type:Unknown
*Jul 19 16:02:28.936: ISDN Se0/0/0:15 Q931: RX <- SETUP_ACK pd = 8  callref = 0x929E
Channel ID i = 0xA98395
Exclusive, Channel 21
Progress Ind i = 0x8288 – In-band info or appropriate now available
*Jul 19 16:02:29.884: ISDN Se0/0/0:15 Q931: RX <- CALL_PROC pd = 8  callref = 0x929E
*Jul 19 16:02:35.196: ISDN Se0/0/0:15 Q931: RX <- ALERTING pd = 8  callref = 0x929E
*Jul 19 16:02:39.900: ISDN Se0/0/0:15 Q931: RX <- CONNECT pd = 8  callref = 0x929E
*Jul 19 16:02:39.900: %ISDN-6-CONNECT: Interface Serial0/0/0:20 is now connected to 0787XXXXXXX N/A
*Jul 19 16:02:39.900: %ISDN-6-CONNECT: Interface Serial0/0/0:20 is now connected to 0787XXXXXXX N/A
*Jul 19 16:02:39.900: %ISDN-6-CONNECT: Interface Serial0/0/0:20 is now connected to 0787XXXXXXX N/A
*Jul 19 16:02:39.904: ISDN Se0/0/0:15 Q931: TX -> CONNECT_ACK pd = 8  callref = 0x129E

Customer now connected to my mobile phone, he could speak to me as well.

Now he hits transfer key to transfer my Original call to my mobile phone.

*Jul 19 16:03:15.960: %ISDN-6-DISCONNECT: Interface Serial0/0/0:20  disconnected from 0787XXXXXXX , call lasted 36 seconds
*Jul 19 16:03:15.960: ISDN Se0/0/0:15 Q931: TX -> DISCONNECT pd = 8  callref = 0x129E
Cause i = 0x80AF – Resource unavailable, unspecified

*Jul 19 16:03:16.040: %ISDN-6-DISCONNECT: Interface Serial0/0/0:7  disconnected from XXXXXX1395 , call lasted 76 seconds
*Jul 19 16:03:16.040: ISDN Se0/0/0:15 Q931: TX -> DISCONNECT pd = 8  callref = 0x8008
Cause i = 0x80AF – Resource unavailable, unspecified

*Jul 19 16:03:16.112: ISDN Se0/0/0:15 Q931: RX <- RELEASE pd = 8  callref = 0x929E
*Jul 19 16:03:16.112: ISDN Se0/0/0:15 Q931: TX -> RELEASE_COMP pd = 8  callref = 0x129E
*Jul 19 16:03:16.208: ISDN Se0/0/0:15 Q931: RX <- RELEASE pd = 8  callref = 0x0008
*Jul 19 16:03:16.212: ISDN Se0/0/0:15 Q931: TX -> RELEASE_COMP pd = 8  callref = 0x8008

You can see both call drop immediately (0x8008 & 0x929E)

There is no proper description of this ISDN error so that was not helpful at all.

I did enable the dspfarm which was disabled and applied the local bypass to hairpin the call without DSPs.

R(config)#voice-card 1
R(config-voicecard)#?
Voice-card configuration commands:
codec Manage codec configuration parameters for voice card
default Set a command to its defaults
dsp Manage DSP configuration for the voice card
exit Exit from voice card configuration mode
local-bypass Enable TDM hairpinning
no Negate a command or set its defaults

Even this didn’t resolve the issue and call was dropping as soon as he hits transfer.

This is where me and my colleague started getting frustrated. We then asked the customer to hit ‘?’ key when we make call to his extension which he did. He told us the codec used was G711ulaw. We asked them to repeat the process when he makes an outbound call to mobile phone and this time the codec was G711alaw which is quite normal for our region (UK). So, the problem was mis-match of codecs as the call was coming in as G711ulaw and was getting transferred to G711alaw. I quickly found out the voice class codec 1 as follows:

voice class codec 1
 codec preference 1 g711ulaw
 codec preference 2 g729r8

I added  the codec pref 3 g711alaw line and that fixed the issue.

voice class codec 1
 codec preference 1 g711ulaw
 codec preference 2 g729r8
 codec preference 3 g711alaw

I think, this is something I didn’t try but if I had removed the pref 1 codec from G711ulaw to G711alaw, things would have worked as well.

voice class codec 1
 codec preference 1 g711alaw
 codec preference 2 g729r8