I have two questions, but both are somewhat related.
I have call admission control and AAR configured on a 9 sites with a central Call Manager 7 cluster.
One site which has only a 128k link into it has 3 ISDN lines (6 channels). All inbound calls hit an Unity Auto Attendant through the WAN so with 6 ISDN channels there’s potential of easily over subscribing the 128K WAN.
On testing this, I’ve come to realise that the CAC/AAR is not functioning correctly, but only where the CTI route point in concerned. When the calls come in, they’re directed to a CTI Route Point which puts the call into Unity. I have the CTI RP set up the same way as any extension on that site. As a test, if I lower the bandwidth allocation of the remote site to something that wont’ even allow one call and I attempt to call another phone across the WAN, CAC/AAR kicks in and the call is rerouted out through the PSTN. However if I try to call the CTI Route point extn#, the CAC kicks in but it doesn’t reroute the call, so the call is prevented from connecting across the WAN but not rerouted out to the PSTN.
When I call into the site externally, where the incoming call is translated to the CTI Route Point, the caller hears ringback. This doesn’t make sense as if the call got through the route point, the AutoAttendant would answer.
So basically, AAR isn’t working for my CTI Route Point, and callers are hearing ringback even though CAC has prevented the call from connecting to the route point.
I have read something about route point and AAR and I will keep digging but I don’t even know what to look for regarding the ringback when nothing is actually ringing.
Thanks in advance,
CAMP-THUR-RTR01# 040313: Jan 30 13:40:27: ISDN BR0/0/0 Q931: RX <- SETUP pd = 8 callref = 0x2D Sending Complete Bearer Capability i = 0x8090A3 Standard = CCITT Transfer Capability = Speech Transfer Mode = Circuit Transfer Rate = 64 kbit/s Channel ID i = 0x89 Exclusive, B1 Calling Party Number i = 0x2183, 'XXXXXXXXX' Plan:ISDN, Type:National Calling Party Number i = 0x2183, 'XXXXXXXXX' Plan:ISDN, Type:National Called Party Number i = 0x81, '1444' Plan:ISDN, Type:Unknown 040314: Jan 30 13:40:27: ISDN BR0/0/0 Q931: TX -> CALL_PROC pd = 8 callref = 0xAD Channel ID i = 0x89 Exclusive, B1 CAMP-THUR-RTR01# 040315: Jan 30 13:40:27: ISDN BR0/0/0 Q931: TX -> DISCONNECT pd = 8 callref = 0xAD Cause i = 0x80A2 - No circuit/channel available 040316: Jan 30 13:40:28: ISDN BR0/0/0 Q931: RX <- RELEASE pd = 8 callref = 0x2D THIS IS WHERE I SHOULD BE DISCONNECTED 040317: Jan 30 13:40:28: ISDN BR0/0/0 Q931: TX -> RELEASE_COMP pd = 8 callref = 0xAD CAMP-THUR-RTR01# 040318: Jan 30 13:40:37: ISDN BR0/0/0 Q931: RX <- RELEASE pd = 8 callref = 0x2D THIS IS WHERE I ACTUALLY HUNG UP Cause i = 0x8090 - Normal call clearing CAMP-THUR-RTR01# 040319: Jan 30 13:40:39: %ISDN-6-LAYER2DOWN: Layer 2 for Interface BR0/0/0, TEI 115 changed to down CAMP-THUR-RTR01# 040320: Jan 30 13:40:39: ISDN BR0/0/0 Q931: Ux_DLRelInd: DL_REL_IND received from L2
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.