Delta Server Failed to Connect

[nitz01]

I have read other threads, but did not find any really helpful information regarding this. We just upgraded our
406v1 to 3.0.69, VMPro to 3.0.19, and Delta Server to 5.0.23. The information below came from the

http://localhost:8080/

configuration page and is installed on the VMPro PC (Windows 2000 SP4). I noticed after upgrading the 406v1 to 3.0.69 that the old version of the delta server (one that did not run as a service) could not connect either. This prompted me to try the new version bundled with the 3.0.69 ADMIN release, with the same results. Can anyone shed some light on this issue? Is there a configuration page/file to point the delta server to the correct IP address? Where can I find documentation? Thanks in advance

Comms Status : Init Comms
refresh
Events

Start Time Type Info
09:42:29 service Delta Server Service Available 4.0.5
09:42:29 Could not find Server on
09:42:29 Failed Local Connect

Page Created : December Thursday 08 2005 9:45:50 AM

Delta Server Version 5.0.23

 

[intrigrant]

http://support.avaya.com/elmodocs2/ip_office/R3.1/delta_server_smdr.pdf

 

[victor5908]

Hi there-the browser won't open until the service is running.I also set the recovery properties for the service to always restart.
Once you have the service running and the browser open you go to the COMM page and select your IP Office-the Delta Server should find it for you.
Then click apply and wait for the COMMS Restored message.
You may have to click apply more than once-don't ask me why,but it sometimes fails on the first try.
On toolkit under the CCC install doc's there is a pretty elaborate description of the Delta server,or try and find something on the Avaya website.
Good Luck-V Chip

 

[nitz01]

thanks guys for the quick replies, i actually found some information in the 3.0 docs cd. i had to specifically go to the comms page

http://localhost:8080/management?page=comms

and click apply once i selected the correct ipoffice system to monitor. in addition, the smdr csv log file

http://localhost:8080/management?page=smdr,

would not be created if i specified the SMDR path & file name, only the path was required. upon saving absolute paths were changed to UNC.
e.g.
C:\Program Files\AVAYA\IP Office\SMDR.csv
would not work.
C:\Program Files\AVAYA\IP Office
would work, and would be changed to
\\SERVER_NAME\C$\Program Files\AVAYA\IP Office

thanks guys

 

[nitz01]

ok.. so i spoke to soon ..
the smdr csv file is only initially written to when i restart the service or make an smdr configuration change. after that no new records are added.. any suggestions

thanks

 

[dmthames]

I'm having a similar issue connecting...in my case the correct ip address is listed, but in the event viewer it lists a different addy on the connect attempt. The documentation says to add the right addy on in the "&search" field, but that does not turn it up either.

Did you make any headway?

 

[nitz01]

to tell you the truth, it sort of got itself working after a reboot and choosing and applying the right control unit in the

http://server:8080/management?page=comms

settings page.
in addition i went back to specifying the actual smdr.csv file name in the

http://SERVER:8080/management?page=smdr

settings page.

eg.
\\SERVER\E$\Avaya\CCC\DeltaServer\SMDR Output\SMDR.CSV

sorry i could not have been of more help

 

[Morrack]

dmthames, is your delta server on the same network segment as the IPO?

It almost sounds like your passing through a NAT device.



Peter Sherwood
Morrack Consulting
Affordable World Class Off-site Backup!

http://www.morrack.com

 

[dmthames]

yes...they're on the same segment.

we ended up cycling the service and it came back functional with the right addy for the ip office. it was still attempting to connect to the addy we had the system on originally when we built it back at the main office...rebooting and restarting services are kinda like duct tape i guess.

Thks for the help.