cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1891
Views
0
Helpful
7
Replies

Inherited IP phone system - need to connect to CallManager GUI

TURBOxSPOOL
Level 1
Level 1

Hello all,

First, a disclaimer: I am a complete and utter newbie with Cisco IP phones and networking. I was given the task of picking up the pieces where those before me left off, and I have nothing but access to routers. No documentation, nada. I only know what I can interpret from the router configs.

EDIT: so the main problem is that this auto-attendant isn't working. I dial 298 and all I get is a busy signal. "The guy before me" said he had a ticket open with Cisco because he had errors when he tried to configure it. Unfortunately he left and I was asked to fix everything. I can learn what I don't know, but hopefully you can help me make this process a little more simple.

So, I can log into the service module which is where the Cisco callmanager software  is (should be) installed. I can see the configuration for the auto-attendant (which is what I need to fix). I want to be able to use the Cisco GUIs to configure this.

Also, part of the configuration points to an attendant script:

script "aasimple.aef"

How can I launch the script editor to view/edit this script? Also, where is the file even located?

Will I need physical access to the module?

Here is the running config from the service module (with some info omitted):

clock timezone America/New_York

hostname se-100-1-21-10

ip domain-name unspecified

software download server url "ftp://127.0.0.1/ftp" credentials hidden "6u/dKTN/hsEuSAEfw40XlF2eFHnZfyUTSd8ZZNgd+Y9J3xlk2B35j0nfGWTYHfmPSd8ZZNgd+Y9J3xlk2B35jwAAAAA="

groupname Administrators create

groupname Broadcasters create

groupname Administrators member admin

groupname Administrators privilege superuser

groupname Administrators privilege ManagePrompts

groupname Administrators privilege ManagePublicList

groupname Administrators privilege ViewPrivateList

groupname Broadcasters privilege broadcast

backup server url "ftp://127.0.0.1/ftp" credentials hidden "EWlTygcMhYmjazXhE/VNXHCkplVV4KjescbDaLa4fl4WLSPFvv1rWUnfGWTYHfmPSd8ZZNgd+Y9J3xlk2B35jwAAAAA="

calendar biz-schedule systemschedule

open day 1 from 00:00 to 24:00

open day 2 from 00:00 to 24:00

open day 3 from 00:00 to 24:00

open day 4 from 00:00 to 24:00

open day 5 from 00:00 to 24:00

open day 6 from 00:00 to 24:00

open day 7 from 00:00 to 24:00

end schedule

ccn application autoattendant

description "autoattendant"

enabled

maxsessions 8

script "aasimple.aef"

parameter "allowExternalTransfers" "false"

parameter "BusinessOpenPrompt" "AABusinessOpen.wav"

parameter "MaxRetry" "3"

parameter "BusinessClosedPrompt" "AABusinessClosed.wav"

parameter "PlayExtensionsPrompt" "AASPlayExtensions.wav"

parameter "HolidayPrompt" "AAHolidayPrompt.wav"

parameter "WelcomePrompt" "AAWelcome.wav"

parameter "BusinessSchedule" "systemschedule"

parameter "ExtensionLength" "1"

end application

ccn application ciscomwiapplication

description "ciscomwiapplication"

enabled

maxsessions 8

script "setmwi.aef"

parameter "strMWI_OFF_DN" "8001"

parameter "strMWI_ON_DN" "8000"

parameter "CallControlGroupID" "0"

end application

ccn application promptmgmt

description "promptmgmt"

enabled

maxsessions 1

script "promptmgmt.aef"

end application

ccn application voicemail

description "voicemail"

enabled

maxsessions 8

script "voicebrowser.aef"

parameter "logoutUri" "http://localhost/voicemail/vxmlscripts/mbxLogout.jsp"

parameter "uri" "http://localhost/voicemail/vxmlscripts/login.vxml"

end application

ccn engine

end engine

ccn subsystem jtapi

ccm-manager address 0.0.0.0

end subsystem

ccn subsystem sip

gateway address "100.1.21.1"

end subsystem

ccn trigger sip phonenumber 297

application "promptmgmt"

enabled

maxsessions 1

end trigger

ccn trigger sip phonenumber 298

application "autoattendant"

enabled

maxsessions 8

end trigger

ccn trigger sip phonenumber 299

application "voicemail"

enabled

maxsessions 8

end trigger

voicemail default mailboxsize 21120

voicemail broadcast recording time 300

end

I apologize for the hastily written post, but I am under pressure to get things working. I was just hoping some of the experienced users can give some detailed advice which will allow me to quickly get on the right track.

Thanks for reading!

7 Replies 7

keanej
Level 3
Level 3


So,  I can log into the service module which is where the Cisco callmanager  software  is (should be) installed. I can see the configuration for the  auto-attendant (which is what I need to fix). I want to be able to use  the Cisco GUIs to configure this.

Also, part of the configuration points to an attendant script:

script "aasimple.aef"

How can I launch the script editor to view/edit this script? Also, where is the file even located?

Will I need physical access to the module?

Here is the running config from the service module (with some info omitted):

Where do I start with this one !!!

Firstly lets explain what you have here -(as I imagine it!)

You have a switch with a number of phones -

You have a router running Call Manager Express

You have a Module (I'm guessing NM-CUE) as you have 8 session available.

Your prompt management is on 297

Your Auto Attendent is on 298

Your Voicemail is on 299.

Are 297 and 299 working ??

The script is edited using a CUE Script editor. You need to know what version of module (Show Software Version).

I would recommend taking the sample script - aasample.aef - but I'd imagine its been hacked a little now !

Let me know what version you are on - I can help you get started -

Where to start indeed! Thanks for bearing with me!

297 + 299 seem to work just fine.

Here are the software versions:

se-100-1-21-10> show software version

Installed Packages:

- Installer  2.1.3

- Bootloader (Primary)  2.1.2

- Infrastructure  2.1.3

- Global  2.1.3

- GPL Infrastructure  2.1.3

- Voice Mail  2.1.3

- Bootloader (Secondary)  2.1.2

- Core  2.1.3

- Auto Attendant  2.1.3

Installed Languages:

- English language pack  2.1.3

I can pick up on things rather quickly, however the sheer volume of information on cisco networking devices making getting into things rather difficult. I was able to reconfigure a number of phones so I hope I can get this done.

Thanks for looking!

What I would recommend is to install a simple script.

Now the editor I have included is for version 3 - unfortunately you are on version 2 (SORRY This forum doesnt allow exe files !)

The version you are on is one of the earliest versions I have seen - its about 6 years old. I would strongly recommend upgrading to version 7.0.6, which is about as far as you can go with that hardware. To upgrade the module you need a FTP server and TFTP server reachable from the router (your PC) - and download a few files & Licenses.

Anyway - back to your problem. I believe this sample script should work fine (just to get you going)

Basically the way it works is - you 'callin' to an auto attendent number - this 'application' has a script associated with it.

The script will have a number of parameters (which need to be valid)

To get going - upload the aa_sample1.aef into your module - goto scripts and upload

then go into auto attendant - and change the script from the current one to this sample one - correct any invalid parameters.

Now you should at least hear something from the auto attendent.

You need to use the editor to create a new script - you can butcher the sample if you like (just save it as something else!)

To get the editor - you need to goto

Download Software | Voice and Unified Communications | Unified Communications Applications | Voicemail and Unified Messaging | Cisco Unity Express | Cisco Unity Express Version 2.3.1

Its stored there !

Wow, I must say I really appreciate your response. Thanks very much.

Anyway, I have been side-tasked for the last day or so, but I am about to try your suggestions right now. I'll report back with the results.

Thanks again!

Ok, having trouble uploading the script. I posted this in a similar discussion:

https://supportforums.cisco.com/message/3245809#3245809

I have an http server running on my local lan, and I want to copy in the script from there.

se-100-1-21-10> ccn copy url "http://172.16.2.253/storage/aa_sample1.aef" script "aa_sample1.aef"

(7) Connect failed; Success

Any ideas? Apparently I can't even ping the server:

se-100-1-21-10> ping 172.16.2.2

PING 172.16.2.2 (172.16.2.2) 56(84) bytes of data.

64 bytes from 172.16.2.2: icmp_seq=1 ttl=255 time=0.385 ms

64 bytes from 172.16.2.2: icmp_seq=2 ttl=255 time=0.268 ms

64 bytes from 172.16.2.2: icmp_seq=3 ttl=255 time=0.228 ms

64 bytes from 172.16.2.2: icmp_seq=4 ttl=255 time=0.227 ms

64 bytes from 172.16.2.2: icmp_seq=5 ttl=255 time=0.225 ms

--- 172.16.2.2 ping statistics ---

5 packets transmitted, 5 received, 0% packet loss, time 1ms

rtt min/avg/max/mdev = 0.225/0.266/0.385/0.063 ms, ipg/ewma 0.378/0.323 ms

se-100-1-21-10> ping 172.16.2.253

PING 172.16.2.253 (172.16.2.253) 56(84) bytes of data.

--- 172.16.2.253 ping statistics ---

5 packets transmitted, 0 received, 100% packet loss, time 4030ms

, ipg/ewma 1007.628/0.000 ms

se-100-1-21-10>

The router where CUE is has the 172.16.2.2 ip address, the server is 172.16.2.253.

Any ideas on why I can't connect to something on the local lan? Will I need physical access to the module or something? Can the router be configured to allow traffic on the local LAN?

Thanks for all the help!

Ok, I got the script loaded.

I had to move the service module to a different network in order to be able to upload the script, but I was able to get the script copied.

After resetting the original configuration, I modified the "autoattendant" application to use the new script:

se-100-1-21-10(config)> ccn application autoattendant

Modifying existing application

se-100-1-21-10(config-application)>  description "autoattendant"

se-100-1-21-10(config-application)>  enabled

se-100-1-21-10(config-application)>  maxsessions 8

se-100-1-21-10(config-application)> script "aa_sample.aef"

end application
Application created successfully, but might not be fully functional due to internal errors

Obviously there is still a problem, and I don't get anything when trying the auto-attendant (298). I am now trying to reload the configuration....

A couple of things -

You should be able to hit the GUI for the service module.

Turn off the proxy server for you PC and try to hit the address of the service module.

You need something similar to below to get working

!

int gig 0/1

ip address 192.168.10.1 255.255.255.0

no shut

! This interface needs to be up

!
interface Service-Engine1/0
ip unnumbered GigabitEthernet0/1
service-module ip address 192.168.10.8 255.255.255.0
service-module ip default-gateway 192.168.10.1

!

ip route 192.168.10.8 255.255.255.255 Service-Engine1/0

!

! I also add the following time-savers

alias exec cue-status service-module service-Engine 1/0 status
alias exec cue-shut service-module service-Engine 1/0 shut
alias exec cue-sess service-module service-Engine 1/0 sess
alias exec cue-reset service-module service-Engine 1/0 reset

!

if you still have no joy geting to the web gui

!

you should seriously consider the upgrade

!

To upgrade add an FTP and TFTP server to your PC,at C:\upload

now add a user to you ftp server -

Username: CISCO

password: password

Ser the root folder for this user to

c:\upload

Now goto the Cisco Website and download the following files

CUCE-Editor-Installer-7.0.3.exe
cue-installer.nm-aim.7.0.3
cue-vm-en_US-langpack.nm-aim.7.0.3.prt1
cue-vm-full-k9.nm-aim.7.0.3.prt1
cue-vm-installer-k9.nm-aim.7.0.3.prt1
cue-vm-k9.nm-aim.7.0.3.pkg
cue-vm-langpack.nm-aim.7.0.3.pkg
cue-vm-license_100mbx_ccm_7.0.3.pkg
cue-vm-license_100mbx_cme_7.0.3.pkg
cue-vm-license_12mbx_ccm_7.0.3.pkg
cue-vm-license_12mbx_cme_7.0.3.pkg
cue-vm-license_25mbx_ccm_7.0.3.pkg
cue-vm-license_50mbx_ccm_7.0.3.pkg
cue-vm-license_50mbx_cme_7.0.3.pkg

Place these files in the upload directory -

Now go to the command line and reset the module.

key ***

during the reboot -

upload the installer file

cue-installer.nm-aim.7.0.3

When prompted load the package

cue-vm-k9.nm-aim.7.0.3.pkg.

Using the GUI you can setup the module again - its really simple

You can now use the

CUCE-Editor-Installer-7.0.3.exe

to make your scripts.