Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

NICE and AES (DMCC)

Status
Not open for further replies.

JuanAvaya

Technical User
Jul 27, 2015
83
AR
Hi guys
Checking if anyone has enough experience on this configuration and can help.

We are currently recording calls with the TSAPI method and want to change to the DMCC method.
I have configured everything as stated in the manuals below but the NICE guys (LOL) are still not able to register to the test virtual station created in CM and AES. Just to clarify, we have DMCC licences and traces to the CM station do not show any attempt of registration.

Manuals:
- Application Notes for configuring NICE Engage Platform R6.3 to interoperate with Avaya Aura® Communication Manager R6.3 and Avaya Aura® Application Enablement Services R6.3 using DMCC Service Observation and Single Step Conference to record calls
- Application Notes for Configuring NICE Interaction Management R4.1 with a SIP Enabled Avaya Aura® Contact Centre R6.2 and Avaya Aura® Application Enablement Services R6.1 for Call Recording
- Configuring NICE Call Recording System – CLS and VoIP Logger with Avaya Application Enablement Services Release and Avaya Communication Manager


This is the error NICE is getting:
NICE_zy8rsl.png


Any idea?
 
Do you have AES 7.0.1? NICE may be trying to authenticate using TLSv1.0. This version of TLS is disabled by default with AES 7.0.1.

Verify TLSv1.0 is enabled on AES. Networking --> TCP/TLS Settings.

This document mentions it in Section 6.8:
Application Notes for CXM 5.2 with Avaya Aura Communication Manager 7.0 and Avaya Aura® Application Enablement Services 7.0

The app notes are for a different call recording solution, but it shows the settings for AES 7.0.1
 
We have AES 6.3.1 which does not have any TLS setting.
 
usernames and passwords... tsapi has 1 user, dmcc another i believe.
 
You lost me there Kyle. I've only created a cti user for NICE to connect according to their request.
 
the Nice log is showing a login error. There's different user types that have access to different things.
Check the DMCC logs on the AES?
 
Ok, here is the log.
I see every 5 minutes it says that it cannot connect to CM from any NIC however, TSAPI service is up and running and ping is successful.

Regarding the attempt to register to ext 58001, the below string says something related to the switch connection not administered. I don't understand what it means.

Switch connection not administered for IP Address = [58001::srvvoip103:0] : has a null or empty switchName trying to acquire license on CM for extension=58001

And finally it mentions 3 possible causes which 1 and 2 do not seem to be as I mentioned before we have a service running now. I don't know where it points the 3rd point
2017-03-13 12.22.45,542 :T-34: com.avaya.mvcs.station.h323.ras.DefaultTerminalDe
vice$H323StationProxyImpl timeout
WARNING: [:srvvoip103:58001:0] : CM Connection lost - protocol timeout: GRQ timer, tried 3 times.Possible problem(s) include:
1. Network connection is not working or is congested
2. IP address to the switch is not correct
3. Switch translation for the extension is not setup correctly




2017-03-13 12.22.15,402 :T-2890: com.avaya.cmapi.intsvc.CstaTerminalImpl isTtsCa
pable
WARNING: callInfoHelpServ not available while processing registration for device
.
2017-03-13 12.22.15,489 :T-2890: com.avaya.mvcs.station.h323.ras.DefaultTerminal
Device sendLicensedStationEvent
WARNING: [:srvvoip103:58001:0] Switch connection not administered for IP Address
= [58001::srvvoip103:0] : has a null or empty switchName trying to acquire licen
se on CM for extension=58001
2017-03-13 12.22.15,531 :T-33: com.avaya.mvcs.station.h323.ras.H323ChannelListen
er handleRead
WARNING: [:srvvoip103:58001:0] Previous packet was not received by other end.
Current received packet dropped because of that exception
java.net.PortUnreachableException
at sun.nio.ch.DatagramDispatcher.read0(Native Method)
at sun.nio.ch.DatagramDispatcher.read(DatagramDispatcher.java:43)
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:218)
at sun.nio.ch.IOUtil.read(IOUtil.java:191)
at sun.nio.ch.DatagramChannelImpl.read(DatagramChannelImpl.java:542)
at com.avaya.common.nio.managed.encryptionImpl.EncryptedMediaByteChannel
.read(EncryptedMediaByteChannel.java:193)
at com.avaya.common.nio.managed.defaultImpl.ManagedByteChannel.read(Mana
gedByteChannel.java:90)
at com.avaya.common.nio.managed.defaultImpl.DefaultUDPChannel.read(Defau
ltUDPChannel.java:283)
at com.avaya.mvcs.station.h323.ras.H323ChannelListener.handleRead(H323Ch
annelListener.java:81)
at com.avaya.common.nio.managed.defaultImpl.DelegatingWritableReadChanne
lHandler.handleRead(DelegatingWritableReadChannelHandler.java:89)
at com.avaya.common.nio.channels.defaultImpl.DefaultChannelServicer.serv
iceChannels(DefaultChannelServicer.java:355)
at com.avaya.common.nio.channels.defaultImpl.SingleThreadedSocketChannel
Daemon.run(SingleThreadedSocketChannelDaemon.java:111)
at java.lang.Thread.run(Thread.java:722)
2017-03-13 12.22.25,535 :T-33: com.avaya.mvcs.station.h323.ras.H323ChannelListen
er handleRead
WARNING: [:srvvoip103:58001:0] Previous packet was not received by other end.
Current received packet dropped because of that exception
java.net.PortUnreachableException
at sun.nio.ch.DatagramDispatcher.read0(Native Method)
at sun.nio.ch.DatagramDispatcher.read(DatagramDispatcher.java:43)
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:218)
at sun.nio.ch.IOUtil.read(IOUtil.java:191)
at sun.nio.ch.DatagramChannelImpl.read(DatagramChannelImpl.java:542)
at com.avaya.common.nio.managed.encryptionImpl.EncryptedMediaByteChannel
.read(EncryptedMediaByteChannel.java:193)
at com.avaya.common.nio.managed.defaultImpl.ManagedByteChannel.read(Mana
gedByteChannel.java:90)
at com.avaya.common.nio.managed.defaultImpl.DefaultUDPChannel.read(Defau
ltUDPChannel.java:283)
at com.avaya.mvcs.station.h323.ras.H323ChannelListener.handleRead(H323Ch
annelListener.java:81)
at com.avaya.common.nio.managed.defaultImpl.DelegatingWritableReadChanne
lHandler.handleRead(DelegatingWritableReadChannelHandler.java:89)
at com.avaya.common.nio.channels.defaultImpl.DefaultChannelServicer.serv
iceChannels(DefaultChannelServicer.java:355)
at com.avaya.common.nio.channels.defaultImpl.SingleThreadedSocketChannel
Daemon.run(SingleThreadedSocketChannelDaemon.java:111)
at java.lang.Thread.run(Thread.java:722)
2017-03-13 12.22.35,538 :T-33: com.avaya.mvcs.station.h323.ras.H323ChannelListen
er handleRead
WARNING: [:srvvoip103:58001:0] Previous packet was not received by other end.
Current received packet dropped because of that exception
java.net.PortUnreachableException
at sun.nio.ch.DatagramDispatcher.read0(Native Method)
at sun.nio.ch.DatagramDispatcher.read(DatagramDispatcher.java:43)
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:218)
at sun.nio.ch.IOUtil.read(IOUtil.java:191)
at sun.nio.ch.DatagramChannelImpl.read(DatagramChannelImpl.java:542)
at com.avaya.common.nio.managed.encryptionImpl.EncryptedMediaByteChannel
.read(EncryptedMediaByteChannel.java:193)
at com.avaya.common.nio.managed.defaultImpl.ManagedByteChannel.read(Mana
gedByteChannel.java:90)
at com.avaya.common.nio.managed.defaultImpl.DefaultUDPChannel.read(Defau
ltUDPChannel.java:283)
at com.avaya.mvcs.station.h323.ras.H323ChannelListener.handleRead(H323Ch
annelListener.java:81)
at com.avaya.common.nio.managed.defaultImpl.DelegatingWritableReadChanne
lHandler.handleRead(DelegatingWritableReadChannelHandler.java:89)
at com.avaya.common.nio.channels.defaultImpl.DefaultChannelServicer.serv
iceChannels(DefaultChannelServicer.java:355)
at com.avaya.common.nio.channels.defaultImpl.SingleThreadedSocketChannel
Daemon.run(SingleThreadedSocketChannelDaemon.java:111)
at java.lang.Thread.run(Thread.java:722)
2017-03-13 12.22.45,542 :T-34: com.avaya.mvcs.station.h323.ras.DefaultTerminalDe
vice$H323StationProxyImpl timeout
WARNING: [:srvvoip103:58001:0] : CM Connection lost - protocol timeout: GRQ tim
er, tried 3 times.Possible problem(s) include:
1. Network connection is not working or is congested
2. IP address to the switch is not correct
3. Switch translation for the extension is not setup correctly
2017-03-13 12.24.31,169 :T-2889: com.avaya.cmapi.intsvc.CstaTerminalImpl isTtsCa
pable
WARNING: callInfoHelpServ not available while processing registration for device
.
2017-03-13 12.24.31,204 :T-2889: com.avaya.mvcs.station.h323.ras.DefaultTerminal
Device sendLicensedStationEvent
WARNING: [:10.100.90.24:58001:0] Switch connection not administered for IP Addre
ss= [58001::10.100.90.24:0] : has a null or empty switchName trying to acquire l
icense on CM for extension=58001
2017-03-13 12.24.31,205 :T-33: com.avaya.mvcs.station.h323.ras.H323ChannelListen
er handleRead
WARNING: [:10.100.90.24:58001:0] Previous packet was not received by other end.
Current received packet dropped because of that exception
java.net.PortUnreachableException
at sun.nio.ch.DatagramDispatcher.read0(Native Method)
at sun.nio.ch.DatagramDispatcher.read(DatagramDispatcher.java:43)
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:218)
at sun.nio.ch.IOUtil.read(IOUtil.java:191)
at sun.nio.ch.DatagramChannelImpl.read(DatagramChannelImpl.java:542)
at com.avaya.common.nio.managed.encryptionImpl.EncryptedMediaByteChannel
.read(EncryptedMediaByteChannel.java:193)
at com.avaya.common.nio.managed.defaultImpl.ManagedByteChannel.read(Mana
gedByteChannel.java:90)
at com.avaya.common.nio.managed.defaultImpl.DefaultUDPChannel.read(Defau
ltUDPChannel.java:283)
at com.avaya.mvcs.station.h323.ras.H323ChannelListener.handleRead(H323Ch
annelListener.java:81)
at com.avaya.common.nio.managed.defaultImpl.DelegatingWritableReadChanne
lHandler.handleRead(DelegatingWritableReadChannelHandler.java:89)
at com.avaya.common.nio.channels.defaultImpl.DefaultChannelServicer.serv
iceChannels(DefaultChannelServicer.java:355)
at com.avaya.common.nio.channels.defaultImpl.SingleThreadedSocketChannel
Daemon.run(SingleThreadedSocketChannelDaemon.java:111)
at java.lang.Thread.run(Thread.java:722)
2017-03-13 12.24.41,209 :T-33: com.avaya.mvcs.station.h323.ras.H323ChannelListen
er handleRead
WARNING: [:10.100.90.24:58001:0] Previous packet was not received by other end.
Current received packet dropped because of that exception
java.net.PortUnreachableException
at sun.nio.ch.DatagramDispatcher.read0(Native Method)
at sun.nio.ch.DatagramDispatcher.read(DatagramDispatcher.java:43)
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:218)
at sun.nio.ch.IOUtil.read(IOUtil.java:191)
at sun.nio.ch.DatagramChannelImpl.read(DatagramChannelImpl.java:542)
at com.avaya.common.nio.managed.encryptionImpl.EncryptedMediaByteChannel
.read(EncryptedMediaByteChannel.java:193)
at com.avaya.common.nio.managed.defaultImpl.ManagedByteChannel.read(Mana
gedByteChannel.java:90)
at com.avaya.common.nio.managed.defaultImpl.DefaultUDPChannel.read(Defau
ltUDPChannel.java:283)
at com.avaya.mvcs.station.h323.ras.H323ChannelListener.handleRead(H323Ch
annelListener.java:81)
at com.avaya.common.nio.managed.defaultImpl.DelegatingWritableReadChanne
lHandler.handleRead(DelegatingWritableReadChannelHandler.java:89)
at com.avaya.common.nio.channels.defaultImpl.DefaultChannelServicer.serv
iceChannels(DefaultChannelServicer.java:355)
at com.avaya.common.nio.channels.defaultImpl.SingleThreadedSocketChannel
Daemon.run(SingleThreadedSocketChannelDaemon.java:111)
at java.lang.Thread.run(Thread.java:722)
2017-03-13 12.24.51,213 :T-33: com.avaya.mvcs.station.h323.ras.H323ChannelListen
er handleRead
WARNING: [:10.100.90.24:58001:0] Previous packet was not received by other end.
Current received packet dropped because of that exception
java.net.PortUnreachableException
at sun.nio.ch.DatagramDispatcher.read0(Native Method)
at sun.nio.ch.DatagramDispatcher.read(DatagramDispatcher.java:43)
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:218)
at sun.nio.ch.IOUtil.read(IOUtil.java:191)
at sun.nio.ch.DatagramChannelImpl.read(DatagramChannelImpl.java:542)
at com.avaya.common.nio.managed.encryptionImpl.EncryptedMediaByteChannel
.read(EncryptedMediaByteChannel.java:193)
at com.avaya.common.nio.managed.defaultImpl.ManagedByteChannel.read(Mana
gedByteChannel.java:90)
at com.avaya.common.nio.managed.defaultImpl.DefaultUDPChannel.read(Defau
ltUDPChannel.java:283)
at com.avaya.mvcs.station.h323.ras.H323ChannelListener.handleRead(H323Ch
annelListener.java:81)
at com.avaya.common.nio.managed.defaultImpl.DelegatingWritableReadChanne
lHandler.handleRead(DelegatingWritableReadChannelHandler.java:89)
at com.avaya.common.nio.channels.defaultImpl.DefaultChannelServicer.serv
iceChannels(DefaultChannelServicer.java:355)
at com.avaya.common.nio.channels.defaultImpl.SingleThreadedSocketChannel
Daemon.run(SingleThreadedSocketChannelDaemon.java:111)
at java.lang.Thread.run(Thread.java:722)
2017-03-13 12.25.01,214 :T-34: com.avaya.mvcs.station.h323.ras.DefaultTerminalDe
vice$H323StationProxyImpl timeout
WARNING: [:10.100.90.24:58001:0] : CM Connection lost - protocol timeout: GRQ t
imer, tried 3 times.Possible problem(s) include:
1. Network connection is not working or is congested
2. IP address to the switch is not correct
3. Switch translation for the extension is not setup correctly
2017-03-13 12.26.40,774 :T-32: com.avaya.mvcs.station.h323.GatekeeperIpToInterfa
ceMapImpl$GkTimerTask pingit
WARNING: Could not connect to GK/PE IP 10.100.90.18 from any NIC.
2017-03-13 12.29.31,733 :T-2890: com.avaya.cmapi.intsvc.CstaTerminalImpl isTtsCa
pable
WARNING: callInfoHelpServ not available while processing registration for device
.
2017-03-13 12.29.31,752 :T-2890: com.avaya.mvcs.station.h323.ras.DefaultTerminal
Device sendLicensedStationEvent
WARNING: [:10.100.90.24:58001:0] Switch connection not administered for IP Addre
ss= [58001::10.100.90.24:0] : has a null or empty switchName trying to acquire l
icense on CM for extension=58001
2017-03-13 12.29.31,753 :T-33: com.avaya.mvcs.station.h323.ras.H323ChannelListen
er handleRead
WARNING: [:10.100.90.24:58001:0] Previous packet was not received by other end.
Current received packet dropped because of that exception
java.net.PortUnreachableException
at sun.nio.ch.DatagramDispatcher.read0(Native Method)
at sun.nio.ch.DatagramDispatcher.read(DatagramDispatcher.java:43)
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:218)
at sun.nio.ch.IOUtil.read(IOUtil.java:191)
at sun.nio.ch.DatagramChannelImpl.read(DatagramChannelImpl.java:542)
at com.avaya.common.nio.managed.encryptionImpl.EncryptedMediaByteChannel
.read(EncryptedMediaByteChannel.java:193)
at com.avaya.common.nio.managed.defaultImpl.ManagedByteChannel.read(Mana
gedByteChannel.java:90)
at com.avaya.common.nio.managed.defaultImpl.DefaultUDPChannel.read(Defau
ltUDPChannel.java:283)
at com.avaya.mvcs.station.h323.ras.H323ChannelListener.handleRead(H323Ch
annelListener.java:81)
at com.avaya.common.nio.managed.defaultImpl.DelegatingWritableReadChanne
lHandler.handleRead(DelegatingWritableReadChannelHandler.java:89)
at com.avaya.common.nio.channels.defaultImpl.DefaultChannelServicer.serv
iceChannels(DefaultChannelServicer.java:355)
at com.avaya.common.nio.channels.defaultImpl.SingleThreadedSocketChannel
Daemon.run(SingleThreadedSocketChannelDaemon.java:111)
at java.lang.Thread.run(Thread.java:722)
2017-03-13 12.29.41,757 :T-33: com.avaya.mvcs.station.h323.ras.H323ChannelListen
er handleRead
WARNING: [:10.100.90.24:58001:0] Previous packet was not received by other end.
Current received packet dropped because of that exception
java.net.PortUnreachableException
at sun.nio.ch.DatagramDispatcher.read0(Native Method)
at sun.nio.ch.DatagramDispatcher.read(DatagramDispatcher.java:43)
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:218)
at sun.nio.ch.IOUtil.read(IOUtil.java:191)
at sun.nio.ch.DatagramChannelImpl.read(DatagramChannelImpl.java:542)
at com.avaya.common.nio.managed.encryptionImpl.EncryptedMediaByteChannel
.read(EncryptedMediaByteChannel.java:193)
at com.avaya.common.nio.managed.defaultImpl.ManagedByteChannel.read(Mana
gedByteChannel.java:90)
at com.avaya.common.nio.managed.defaultImpl.DefaultUDPChannel.read(Defau
ltUDPChannel.java:283)
at com.avaya.mvcs.station.h323.ras.H323ChannelListener.handleRead(H323Ch
annelListener.java:81)
at com.avaya.common.nio.managed.defaultImpl.DelegatingWritableReadChanne
lHandler.handleRead(DelegatingWritableReadChannelHandler.java:89)
at com.avaya.common.nio.channels.defaultImpl.DefaultChannelServicer.serv
iceChannels(DefaultChannelServicer.java:355)
at com.avaya.common.nio.channels.defaultImpl.SingleThreadedSocketChannel
Daemon.run(SingleThreadedSocketChannelDaemon.java:111)
at java.lang.Thread.run(Thread.java:722)
2017-03-13 12.29.51,761 :T-33: com.avaya.mvcs.station.h323.ras.H323ChannelListen
er handleRead
WARNING: [:10.100.90.24:58001:0] Previous packet was not received by other end.
Current received packet dropped because of that exception
java.net.PortUnreachableException
at sun.nio.ch.DatagramDispatcher.read0(Native Method)
at sun.nio.ch.DatagramDispatcher.read(DatagramDispatcher.java:43)
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:218)
at sun.nio.ch.IOUtil.read(IOUtil.java:191)
at sun.nio.ch.DatagramChannelImpl.read(DatagramChannelImpl.java:542)
at com.avaya.common.nio.managed.encryptionImpl.EncryptedMediaByteChannel
.read(EncryptedMediaByteChannel.java:193)
at com.avaya.common.nio.managed.defaultImpl.ManagedByteChannel.read(Mana
gedByteChannel.java:90)
at com.avaya.common.nio.managed.defaultImpl.DefaultUDPChannel.read(Defau
ltUDPChannel.java:283)
at com.avaya.mvcs.station.h323.ras.H323ChannelListener.handleRead(H323Ch
annelListener.java:81)
at com.avaya.common.nio.managed.defaultImpl.DelegatingWritableReadChanne
lHandler.handleRead(DelegatingWritableReadChannelHandler.java:89)
at com.avaya.common.nio.channels.defaultImpl.DefaultChannelServicer.serv
iceChannels(DefaultChannelServicer.java:355)
at com.avaya.common.nio.channels.defaultImpl.SingleThreadedSocketChannel
Daemon.run(SingleThreadedSocketChannelDaemon.java:111)
at java.lang.Thread.run(Thread.java:722)
2017-03-13 12.30.01,762 :T-34: com.avaya.mvcs.station.h323.ras.DefaultTerminalDe
vice$H323StationProxyImpl timeout
WARNING: [:10.100.90.24:58001:0] : CM Connection lost - protocol timeout: GRQ t
imer, tried 3 times.Possible problem(s) include:
1. Network connection is not working or is congested
2. IP address to the switch is not correct
3. Switch translation for the extension is not setup correctly
2017-03-13 12.31.40,778 :T-32: com.avaya.mvcs.station.h323.GatekeeperIpToInterfa
ceMapImpl$GkTimerTask pingit
WARNING: Could not connect to GK/PE IP 10.100.90.18 from any NIC.
2017-03-13 12.36.40,782 :T-32: com.avaya.mvcs.station.h323.GatekeeperIpToInterfa
ceMapImpl$GkTimerTask pingit
WARNING: Could not connect to GK/PE IP 10.100.90.18 from any NIC.
2017-03-13 12.41.40,786 :T-32: com.avaya.mvcs.station.h323.GatekeeperIpToInterfa
ceMapImpl$GkTimerTask pingit
WARNING: Could not connect to GK/PE IP 10.100.90.18 from any NIC.
2017-03-13 12.46.40,790 :T-32: com.avaya.mvcs.station.h323.GatekeeperIpToInterfa
ceMapImpl$GkTimerTask pingit

 
Just to add some more info, a DMCC test from AES throws the below results.


2017_04_12_13_00_57_AES_Management_Console_irhvu0.png



Meanwhile, list trace ras shows 3 GRQ received in a 20 seconds interval.



LIST TRACE

time data

12:43:48 TRACE STARTED 04/12/2017 CM Release String cold-03.0.124.0-21106
12:44:21 rcv GRQ ext 58001
endpt [10.100.94.17]:31311
switch [10.100.90.18]:1719
12:44:21 snd GCF ext 58001
endpt [10.100.94.17]:31311
switch [10.100.90.18]:1719
12:44:31 rcv GRQ ext 58001
endpt [10.100.94.17]:31311
switch [10.100.90.18]:1719
12:44:31 snd GCF ext 58001
endpt [10.100.94.17]:31311
switch [10.100.90.18]:1719
12:44:41 rcv GRQ ext 58001
endpt [10.100.94.17]:31311
switch [10.100.90.18]:1719
12:44:41 snd GCF ext 58001
endpt [10.100.94.17]:31311
switch [10.100.90.18]:1719
12:55:09 RAS TRACE COMPLETE ext
 
Is there a firewall involved?

Take Care

Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.
 
What's 10.10.90.24 referencing in your traces?
Obviously registrations are getting through to CM, and CM is responding in the affirmative. Why the AES isn't correlating that acceptance to the request it made, I do not know. Are you registering to procr? CLANs? Do you have the active IP configured correctly in AES and not the IP of the active server? Smells like some config issue.
 
10.100.90.24 is the eth1 of AES however client, switch and media is configured in eth0.
We are registering to the procr and the ip of CM is the virtual one so no chance of going to the standby server.

Now based on your questions, I took a look and see AES is configured in node-names with one ip
list node-names all

NODE NAMES

Type Name IP Address
IP SRVVOIP103 10.100.94.17




but status aesvcs link shows 10.100.90.24

status aesvcs link

AE SERVICES LINK STATUS

Srvr/ AE Services Remote IP Remote Local Node Msgs Msgs
Link Server Port Sent Rcvd

01/01 SRVVOIP103 57601 procr 5603 1987
10.100.90.24




I have not much experience with AES, where did CM take that IP from?
 
Ha. OK. So, to get a AES to a CM, it's in "change ip-services" You must match nodename = AES hostname and AES must use the "switch password" you define in that form.

Now, if AES's IP routing sends it out eth1 and not eth0, it's still presenting from the same hostname, but the IP isn't right.

I'll bet that's where your mixup is.

Is your AES supposed to be dual NIC config? It makes total sense that AES says at the IP layer "well, eth0 is in the same subnet as procr, I'm using that!" and then CM has the listed node name bearing the IP in the other subnet. So, when the right hostname makes a aes connection, CM shows you the traces from the IP associated to that node - not explicitly the ip of the interface AES actually sent it on.

Make sense?

ifconfig eth1 down :)
 
I follow you. Anyway, node-names has the 94.17 ip and NOT the 90.24 so why does CM know about 90.24???

My inquiry is, if I put the eth1 down, would I break the actual recording config?
 
AES is using .90.24 because it has 2 interfaces - 1 in the same subnet as CM, so it doesn't require a gateway/router to get to CM, so it uses that.

If you are using a dual nic config, you'd think that the one in CM's subnet would be for CM and the other for your applications. What if you change the node-name to the .90 address?
 
It's set as single-NIC

If I change the ip of AES in CM node-names, should I also change client, switch and media to eth1(90.24)in AES?
 
If that's the desired operation, then that makes sense!
 
And what is the impact of that change to the working configuration? Anyone knows if it requires a restart?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top