9971 SIP Phones fail to register to CME

Other than the below roughly make sure your SIP is bound to the same interface as your "source address" under "voice register global"... 

voice service voip

sip

bind control source-interface Loopback0

bind media source-interface Loopback0

** above the sip is bound to my interface Loopback0 and below the voice register global has the source-address mentioned as my voice vlan interface ip..... this was what prevented the 9971 phone from registering to CME, once I changed the sip bind to gi0/0.11 (same as the source-address... the phones registered)

voice service voip

    allow-connections h323 to h323

    allow-connections h323 to sip

    allow-connections sip to h323

    allow-connections sip to sip

sip

     bind control source-interface gi0/0.11 (was earlier set to Loopback0)

     bind media source-interface gi0/0.11 (was earlier set to Loopback0)

     registrar server expires max 300 min 60

voice register global

    max-dn 25

    max-pool 10

    mode cme

    source-address 142.102.66.254 port 5060

    load 9971 sip9971.9-4-1SR1-2

    authenticate register

    tftp-path flash:

    create profile

voice register dn  1

    number 3001

voice register pool  1

    id mac 5ca4.8a64.5e87

    type 9971

    number 1 dn 1

    username cisco password cisco

tftp-server flash:dkern9971.100609R2-9-4-1SR1-2.sebn

tftp-server flash:kern9971.9-4-1SR1-2.sebn

tftp-server flash:rootfs9971.9-4-1SR1-2.sebn

tftp-server flash:sboot9971.031610R1-9-4-1SR1-2.sebn

tftp-server flash:sip9971.9-4-1SR1-2.loads

tftp-server flash:skern9971.022809R2-9-4-1SR1-2.sebn

Calls from SIP 9971 phones to internal extensions takes too long to dial out (roughly 15 seconds)

adjust the t302 timer in CUCM from the Service Parameters (the lowest you can go as of CUCM version 9.x) is 3000 ms or 3 seconds.

Problem with AAR Calls - Remote H323 Gateway is not able to route the call to the CUCM

When AAR is triggered in CUCM (I mean once the phone says "Not Enough Bandwidth. Rerouting"... and attempts to dial the External Phone Number Mask entry of the destination phone, the call once routing over the PSTN with the E.164 reaches the far end router over PSTN but the return VOIP Dial Peer to CUCM does not seem to reach CUCM.

Fix:

"Bind your H323 traffic to a Voice Interface on the Remote Voice Gateway that is returning the call to CUCM and reregister the remote gateway in CUCM as H.323.



Also do the following (although the above H323 traffic binding fixed the problem)

voice service voip on both gateways and allowed-connections h to h

Also if it's a 15.0 IOS then either say "no IP Address Trusted Authenticate" or add the ip address of the source to the "IP Addresss Trusted List" under "voice service voip"

Overall UCS Connectivity between the VM's to the FI's

The above pic on shows one Blade Server on a Chassis connected to one side of the Fabric... the other side of the Fabric would have the same logic.

D-channel interface does not appear in the " sh ip int b"

make sure you've got enough DSP's in the router...

"An error has occurred while trying to resynchronized the Cisco JTAPI client ,Please try Cisco JTAPI Resync in Cisco Unified CCX Administration again,keep getting this and the uc telephony subsystem service still shows partially up.any clues?

josh finke had posted a resolution to this that I believe would solve that issue, i've posted the link below.....

you'll as well need to make sure you have ur Unified CM Telephony Subsystem configured with the group and trigger and all and restart the unified ccx engine, and after u have configured the UCM Tele Subsystem, login in to CUCM and see if your CTI ports and CTI Route Point are created and registered and also check if your jtapi user that was created during the integration has the cti ports and route point in the Controlled Devices section, just to make sure that uccx and cucm are talking to each other smoothly...

https://learningnetwork.cisco.com/thread/10881

Steps from his post:

1. Create a folder named WINNT in c:

1. Copy c:WINDOWSJava to WINNT

1. Go to Cisco JTAPI Resync in the Unified CM Telephony Subsystem to install the Cisco JTAPI Client

4. Go to System>Control Center and restart Cisco Unified CCX Engine

Integrating CUCM with CUE - JTAPI Login Failed. Error while determining CCM Version-1

..was testing the CUE (Ver. 7.0.6) integration with CUCM ver 7.0.1, all went well however when I key in the jtapi username and password (created in CUCM with control of the CTI_RP and the CTI_Ports along with the Standard CTI Enabled Role) in the CUE GUI (after entering the cucm ip and web username and password obviously), it takes like 3 mins (this is because I have a WIC-1T FRelay connection and not an HWIC-1T), it finally gives me the error "JTAPI Login Failed. Error while determining CCM Version-1"... tried reloading the image (same version) didn't work (maybe another version would work... instead of the 70.6 that i have).... what I did next was to configure the CUE module from the CLI with the cucm info... (jtapi user, ctip ports... etc..)... before you do this make sure you have the right license file for cue loaded, you could verify this using "show software licenses", if you have the cme license file loaded something like "cue-vm-license_12mbx_cme_7.0.6.pkg", then you better load the ccm license file "cue-vm-license_12mbx_ccm_7.0.6.pkg" by issuing the command "sofware install clean url ftp://x.x.x.x/cue-vm-license_12mbx_ccm_7.0.6.pkg" where (x.x.x.x is the ftp server, install the ftp software like ftpd or filezilla on your pc and give the ip of your pc in the x.x.x.x above).... will ask you to reload and will take like 7mins... you could then re-issue the "show software licenses" command to view the license... should be ccm now... .. you could then try the normal recommended config to have it integrated... Alex has posted a good post on it... or a post from "voiceonbits" at the links below;

http://alexsj9.blogspot.com/2010/03/integrating-cue-and-cucm.htmlhttp://voiceonbits.com/2010/07/17/cisco-unity-express-setup-cue-cucm/

and if all hell brakes loose with the " JTAPI Login Failed. Error while determining CCM Version-1" error then try reloading the image and still nothing then....

CUE CLI Config for CUE-CUCM Integration

ccn subsystem jtapi
ctiport 4441 4442 (note: these are already created in cucm)
ccm-manager address x.x.x.x
ccm-manager username jtapi_cue password cisco
end subsystem

reloaded the cue module and then configured the 

ccn trigger jtapi phonenumber 4440 (this is the cti route point & voice mail pilot configured in cucm)
application "voicemail"
enabled
end trigger

add the below for fallback to srst

cue subsystem sip
gateway address x.x.x.x (cue router address)
mwi sip unsolicited
exit

ccn trigger sip phonenumber 4440
application "voicemail"
enabled
end trigger

with the cti ports and all that and reloaded the module again and still did not see it register in cucm, had a reload of the router.. check to confirm if your cti route point and cti ports have registered in cucm... also issue the "show ccn status ccm-manager" command in cue cli to check the status of the integration, should show up as registered.....

Test by calling the voicemail from the phone and leaving a voicemail from another phone and test the mwi on and off... all works great although the cue module will still show up as uninitialized....