03-07-2011 04:52 PM - edited 03-16-2019 03:50 AM
It's been a few years since I've had the misfortune of dealing with CME/CUE.
Router is a 2901 running 15.1.3
I've set up the ISM with ip unnumbered.
I've assigned an IP to the service-module
I've added the static route for the service-module
When I try to connect to CUE with "service-module ISM0/0 session" I get "connection closed by foreign host"
I can ping the address of the service module.
I can even telnet to it - but don't know the credentials (I tried the routers)
I can't connect to it via http
Anyone have any ideas? I've spent the last 2 hours looking everything over and I don't see anything wrong.
Any help is apprecaited.
Thanks,
Craig
03-07-2011 06:41 PM
you can probably just do a show session to see which session ID has the Unity Module open. Then you can disconnect that session. After that, try to access the module once more.
03-07-2011 06:49 PM
No it's not that simple... I tried it already, but here it is again.
7359-2901-RTR1#sh session
% No connections open
7359-2901-RTR1#sh line
Tty Line Typ Tx/Rx A Modem Roty AccO AccI Uses Noise Overruns Int
0 0 CTY - - - - - 0 0 0/0 -
1 1 AUX 9600/9600 - - - - - 0 0 0/0 -
I 0/1/0 19 TTY - - - - - 0 473 0/0 Ce0/1/0
67 67 TTY 115200/115200- - - - - 0 0 0/0 -
* 388 388 VTY - - - - - 6 0 0/0 -
Line 67 is what the service-module says it's listening on.
*************************************************
FAILED CONNECTION
*************************************************
7359-2901-RTR1#service-module ISM0/0 session
Trying 10.154.243.1, 2067 ... Open
[Connection to 10.154.243.1 closed by foreign host]
*************************************************
Module Status (notice line 67)
*************************************************
7359-2901-RTR1#service-module ISM0/0 status
Service Module is Cisco ISM0/0
Service Module supports session via TTY line 67
Service Module is in Steady state
Service Module heartbeat-reset is enabled
Getting status from the Service Module, please wait..
Cisco Unity Express 8.0.2
CUE Running on ISM
Module resource information:
CPU Frequency: 1064 MHz
Memory Size: 513168 MB
Disk 0 Size: 7456 MB
No install/uninstall in progress
Local Partition Info - (0 apps)
=====================
Retrieving partition information
Thanks,
Craig
03-08-2011 10:48 AM
50 views and no one has any idea? Come on I know you guys are smarter than that. lol
03-08-2011 07:52 PM
Hi,
I got the problem same you. Can you try it? Could you unplug the CUE module and Plug into the Router, Couldn't you?
I try it and I can connect to CUE, but I just got a problem like that again. I can ping and connect by HTTP, but I can't connect to CUE from Router.
So I want to open the TAC case about my problem.
and I have an other question to you about AA script. After I got a problem like that, so I can't to use the AA new script, I also use the AA script default. because when i use the new script, it didn't work, my new sccript work fine before I got the CUE problem. Did you got like that?
Could you help me about AA Script? I got a example script from the Cisco. when I call the phone number, the AA script will run first, The AA script ask me to press 1, if i know the extention and press 0 to Operator, So I don't want to press 1 to dial extension, I want to direct dial to extension. Could you give me the script?
My email: longpt@hpt.vn or phamthienlong2005@yahoo.com
Thanks and regards
03-09-2011 07:33 PM
Hi,
Anybody has any idea
Thanks
03-14-2011 11:10 AM
We were able to figure it out after TAC sent us a new router and that didn't fix the issue.
We removed:
03-23-2011 02:05 PM
Looks like dlsw and the module are looking for the same port. Dlsw uses
tcp 2065 and 2067 to setup its peers. From the module output
Service Module supports session via TTY line 67
looks like it is going to 2067 (tty lines are 2000 + line number).
You might be able to workaround this with dlsw version 2 peers. I think they use 2065 only.
I'll check in the lab tomorrow and let you know.
Matthew
03-23-2011 02:16 PM
Matthew,
You may be right on this, we chose to move the voice to it's own VLAN so that the DLSW peer would be using it's own address. This has fixed the issue. I just wish that TAC would have looked over the configuration and caught this, instead of wasting time sending us new hardware.
thanks for the feed back,
Craig
03-24-2011 12:58 AM
It looks like we use 2067 for the UDP explorers. I tried with dlsw v2 but haad some issues.
However, disabling the udp-explorers should resolve the issue.
Matthew
r222#sh dls pe
Peers: state pkts_rx pkts_tx type drops ckts TCP uptime
TCP 192.168.1.221 CONNECT 19 17 prom 0 1 0 00:01:11
Total number of connected peers: 1
Total number of connections: 1
r222#sh ip socket det
Proto Remote Port Local Port In Out Stat TTY OutputIF
17 255.255.255.255 0 192.168.1.222 2067 0 0 100001 0
Queues: output 0
input 0 (drops 0, max 50, highwater 1)
r222#conf t
Enter configuration commands, one per line. End with CNTL/Z.
r222(config)#dlsw udp-
r222(config)#dlsw udp-disable
r222(config)#^Z
r222#sh r
*Mar 24 07:56:43: %SYS-5-CONFIG_I: Configured from console by console
r222#sh runn | incl dlsw
dlsw local-peer peer-id 192.168.1.222 promiscuous
dlsw udp-disable
r222#sh ip socket det
r222#
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: