|
Home > Archive > Voice over IP Cisco > March 2006 > Attendant console pc with two ip addresses
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Attendant console pc with two ip addresses
|
|
| Ruben Montes \(EU\) 2006-03-23, 8:46 pm |
| Hi,
I'm running into a little problem... I'm installing the attendant console in a customer environment where all the PCs have two ip addresses: one logical network connection with an ip address used for a specific application, and then the normal ehernet connection to access all the resources in the network.
The problem is that the Assistant console is taking this first special ip instead the second one, which must be used: the application takes so many time to start and we have problems for example, to park a call, which is not permited. If we put manually the ip address in the assistant console configuration (the nework ip), then we still having some problems.
If we disable the logical interface all works fine...
Any idea what could be happening or how can I investigate this issue deeper?
Thanks in advance,
Ruben
| |
| Fedorov, Konstantin 2006-03-23, 8:46 pm |
| Hi,
What kind of problem you have when configure ip address manually in the
AC ??
I think that this is right way to hard tie ip address with AC when PC
have two ip addresses.
To deeper analyze problem collect TCD traces in the CCM.
-----------------------
Sincerely Yours,
Konstantin Fedorov
_____
From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Ruben Montes
(EU)
Sent: Wednesday, March 22, 2006 2:08 PM
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] Attendant console pc with two ip addresses
Hi,
I'm running into a little problem... I'm installing the attendant
console in a customer environment where all the PCs have two ip
addresses: one logical network connection with an ip address used for a
specific application, and then the normal ehernet connection to access
all the resources in the network.
The problem is that the Assistant console is taking this first special
ip instead the second one, which must be used: the application takes so
many time to start and we have problems for example, to park a call,
which is not permited. If we put manually the ip address in the
assistant console configuration (the nework ip), then we still having
some problems.
If we disable the logical interface all works fine...
Any idea what could be happening or how can I investigate this issue
deeper?
Thanks in advance,
Ruben
|
|
|
|
|