CCAPI: Internal Error (Software Error)

We changed a customer from PRI to SIP trunk and after the change, the Exchange UM stopped working for calls coming in from the outside.  We found the following error in the logs: %VOICE_IEC-3-GW: CCAPI: Internal Error (Software Error): IEC=1.1.180.1.13.112 on callID 78 Some posts mentioned upgrading the firmware (which we did with no effect).  The dial-peer pointed to Exchange had some volume adjustments on it.  Once we removed the adjustments, the error went away and calls went through. dial-peer voice 100 voip description Dial-peer for Exchange VM destination-pattern 60. session protocol sipv2 session target ipv4:10.5.99.11:5065 session transport tcp dtmf-relay rtp-nte audio incoming level-adjustment -5 audio outgoing level-adjustment -15 codec g711ulaw no vad Other things to check would be codec changes or TCP/UDP changes as either would cause...

Outbound faxes from a Dialogic SR140 not using T.38

Had an issue with an IP fax server (RelayFax with a Dialogic SR140 connecting via SIP trunk to an Adtran SBC) where inbound faxes were working fine and using T38 but outbound faxes were never negotiating T.38 and falling back to G.711 passthrough.  As a result we were having some unreliable outbound faxes. In the Brooktrout Configuration Tool under the T.38 Parameters tab we had to change the delay time for media renegotiation.  The “Media Renegotiate Delay Outbound, msec” was set to “-1” and I changed this to 5000 msecs.  See...

Trouble with Exchange UM and arbitration mailbox corruption

One of our clients had an issue where their Unified Messaging arbitration mailbox had become corrupted.  We were unable to change the audio files on the auto-attendants and we were seeing errors like this in the application logs: Event ID 1431 UM can’t save the Call Data Record message to the EDiscovery mailbox. More information “The number of call data record messages being processed in the Unified Messaging pipeline has exceeded the maximum limit. Please check whether the EDiscovery mailbox with DistinguishedName CN=SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9},CN=Users,DC=domain,DC=com or MailboxDatabase CN=UM-Mailbox-DB,CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=domain,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=com is down.”. Event ID 1099 User “SYSTEM” attempted to modify a custom prompt for auto attendant “AA 001”. The operation failed. Make sure that the user is assigned the UM Prompt role or UM Management role. More information: “An error occurred while accessing the custom prompt publishing point. The underlying connection was closed: An unexpected error occurred on a send.”. After unsuccessful attempts to repair the arbitration mailbox we deleted and recreated the mailbox.  First we removed the arbitration mailbox: Disable-Mailbox “SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}” -Arbitration Note: We did not opt to delete the user account associated with the UM mailbox in this particular case.  If both the UM arbitration mailbox and user account are somehow corrupted then it may also be necessary to delete the “SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}” user account under the AD Users folder after disabling the mailbox.  To recreate that user run “setup.exe /PrepareAD” from the Exchange installation folder and the user will be created again. Then we recreated the mailbox: Enable-Mailbox -Arbitration -Identity “SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}” Then we set the display name to the correct value “Microsoft Exchange”, because the default setting was wrong: Set-Mailbox -Arbitration -Identity “SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}” -DisplayName...

Registering voice-ports from a Cisco 881 SRST router to CME / UC500

The Cisco 881 router comes in an SRST flavor (C881SRST-K9) which includes 1 FXO and 4 FXS ports.  We recently ran into a problem at a customer’s new install where the service provider did not run new FXO lines in time for the installation.  So seeing that we had some FXS ports available, and being familiar with integrating the VG224 and VG204 to CME, I set out to see if the FXS ports in the 881 could be registered via SCCP to the CME across the WAN.  The answer is yes! Here are the relevant parts of the config in the 881: stcapp ccm-group 1 stcapp ! interface FastEthernet0 ip address 192.168.2.1 255.255.255.0 ! voice-port 0 timeouts ringing infinity caller-id enable ! voice-port 1 timeouts ringing infinity caller-id enable ! sccp local FastEthernet0 sccp ccm 10.1.1.1 identifier 1 version 3.1 sccp ! sccp ccm group 1 associate ccm 1 priority 1 ! dial-peer voice 100 pots service stcapp port 0 ! dial-peer voice 101 pots service stcapp port 1 And on the CME interface Vlan100 ip address 10.1.1.1 255.255.255.0 ! ephone-dn 35 number 1234567 description Remote 881 ! ephone 1 device-security-mode none description 881 FXS Port 0 mac-address 0000.1234.5678 max-calls-per-button 2 type anl button 1:35 ! For me the ephone showed up automatically, but you might need to add it manually.  If that’s the case use the following command on the 881 to determine the mac address for port 0:  “show stcapp device voice-port 0”  In the output under the “Device Name” field the mac address will be the last 12 characters of the...

Music On Hold Streaming from an FXO port on CME 8.8

Here’s another CME feature that did not work quite as expected when reading the documentation.  As with the conference bridge, I read along and followed the documentation from Cisco for “Configuring Music on Hold from a Live Feed” (the link is below) and the feature was still not working.  When placed on hold, all callers heard was the default Cisco MOH audio file.  This showed that the fall back portion of the config was working fine but overall something was missing. “http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/admin/configuration/guide/cmemoh.html#wp1010511 According to Cisco all that is required is a cable to connect to your live feed device, a fxo or e&m port, a dial-peer and an ephone-dn. The cable we made on our own out of a bit of cat5, a RJ11 head and male to mail 3.5mm audio cable. For those interested, the 3.5mm cable was the type with one wire running through the middle and another wrapped around like a sheath.  The blue pair of the cat5 was then connected to the two lines from the audio cable using a couple of butt splices.  These were then wrapped individually with electrical tape to prevent interference and then all wrapped together to make the finished product a little less rough (pictured below). A RJ11 head was then connected to the other end of the cat5 using the blue pair in the middle two pins. I initially thought the issue might be with my homemade cable as it does look a little kludgy but I wanted to continue researching to eliminate all configuration issue. Again, another user saved the day by providing portions of a working config...