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 Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Witness and Avaya installation 1

Status
Not open for further replies.

ashtilman

IS-IT--Management
Sep 4, 2007
7
hi,

We have a problem in an AVAYA S8700 enviroment with witness contactstore. there is a connection between the contactstore server and the avaya aes server and cm (in the contact store web page we can see that the link is "up).

the problem is that the extensions we configured to "call observe" are getting a "timeout" message in the witness log. it seems that they are not able to perfrom "call observing". we have tested the ability to perfrom call observing with an IP SOFTPHONE on the witness extension and it worked great. any idea why it is not working?

thanks
 
ashtilman,

run 'list trace station' on witness ext and restart witness to see what happens. i guess most probable cause will be witness server ip address missing from ip-network-map table so s8700 doesn't know which ip-network-region it belongs and couldn't allocate ip resources for it. or may be something different, gotta see list trace output.
 
hi,

I am getting a "codec miss match" error. what can it be?

thanks
 
sorry, worng error. the error is:

Port 20901 Registration failed. Reason: CM Connection lost - protocol timeout: Normal RRQ timer, tried 3 times.Possible problem(s) include: 1. Network connection is not working or is congested


thanks
 
ashtillman,

check the network connectivity between witness and cm. also use 'list trace ras ip-addr x.x.x.x' where x.x.x.x is an ip address of the witness server to see what happens on cm side.
 
there is full connectivity between the servers. the trace shows that everything is ok between the cm and the witness.

If I change the witness to work with another clan I get the codec error that is listed above.
 
hi,

the problem was solved. the issue was that in the ip-network-map were configured the aes and witness server. when we removed them from the ip-network-map the system started to work...

thanks
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top