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 IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Octel visual messenger 1
- Thread starter nortel23
- Start date
-
1
- #2
What did you change on the OAS server side? What is not working? Is the OAS red in the gateway? What version of Visual messenger are you on?
Ken Means
"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)
Ken Means
"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)
- Thread starter
- #3
We have 4.0. The server will not lauch. Nothing was changed on the OAS. I found on the Avaya web site that:
The OctelAccess Server does not have to be a member of a Domain. It cannot be configured as a Domain Controller and should not hold any of the FSMO roles in the Active Directory. It must be Stand Alone. Visual Desktop Messaging clients communicate with the OctelAccess Server directly via TCP/IP and are not required to be authenticated by Windows 2000.
I am think this is part of active directory and needs to be stand alone.
This all started when they put this on Active directory.
The OctelAccess Server does not have to be a member of a Domain. It cannot be configured as a Domain Controller and should not hold any of the FSMO roles in the Active Directory. It must be Stand Alone. Visual Desktop Messaging clients communicate with the OctelAccess Server directly via TCP/IP and are not required to be authenticated by Windows 2000.
I am think this is part of active directory and needs to be stand alone.
This all started when they put this on Active directory.
- Thread starter
- #4
The pasword is in the Octel under the applications that it uses but that would not have changed. Are they blocking any ports on the network after the changeout?
You can run the trace on the OAS and see where it is failing.
If you want we can do a gotomeeting and i can look at it with you
Ken Means
"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)
You can run the trace on the OAS and see where it is failing.
If you want we can do a gotomeeting and i can look at it with you
Ken Means
"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)
The documentation is on the OAS CD if you still have it. The question on my mind is whether or not the OAS server is connecting to the Octel 250/350 (the "green light" from the OctelAccess Adminstrator program) or whether the Visual Messenger client application is connecting to the OAS server. Like Ken Means has stated, you can run the OctelAccess Server Trace Viewer program on the OAS server to see what is going on. You can also verify that you can ping the IP address of the Octel 250/350 from the OAS server and that you can ping the IP address of the OAS server from the Octel 250/350 Lan card.
Chuck
RCT Technologies
Chuck
RCT Technologies
- Thread starter
- #7
After you connect we can chat in the meeting
Please join my meeting at
Ken Means
"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)
Please join my meeting at
Ken Means
"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)
So it was a rights issue for the user running the service right?
Ken Means
"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)
Ken Means
"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)
- Thread starter
- #10
- Thread starter
- #11
There are some passwords which are required for Visual Messenger server to connect to the octel system. They are as follows and are needed.
IMS Connection: Password Enter the same password that is configured on the Aria.
ASA Connection: Password Enter the same password that is configured on the Aria.
IVR Connection: Password Enter the same password that is configured on the Aria.
Mailbox Enter the same mailbox that is configured on the Aria.
SUD Connection: Password Enter the same password that is configured on the Aria.
They are having problems with visual messenger passwords.
IMS Connection: Password Enter the same password that is configured on the Aria.
ASA Connection: Password Enter the same password that is configured on the Aria.
IVR Connection: Password Enter the same password that is configured on the Aria.
Mailbox Enter the same mailbox that is configured on the Aria.
SUD Connection: Password Enter the same password that is configured on the Aria.
They are having problems with visual messenger passwords.
So the error you are getting said that the password is not right for the ASA,SUD and so on?
That would mean that someone has changed the passwords in the OAS or on the Octel side.
Have you checked the passwords on both ends?
Ken Means
"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)
That would mean that someone has changed the passwords in the OAS or on the Octel side.
Have you checked the passwords on both ends?
Ken Means
"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)
- Thread starter
- #13
you have to know the App numbers to access them. Can you call me
Ken Means
"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)
Ken Means
"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)
Octel 250/350 Message Server, verify:
? IP address and subnet mask (Menu 22.1)
? Features 9, 10, 40 and 73 installed
(Menu 13.7) ? Yes ? No
? Creation of applications in Menu 17.2.1.
Use the same password for each application:
- ID 239 with 10 sessions (password)
- ID 240 with 144 sessions (password and mailbox)
- ID 241 with 24 sessions (password)
- ID 253 with 1 session (password)
? Type 40 mailbox created for AP ID 240 ? Yes ? No
? Type 0 mailboxes created for Visual Messenger users with
client access feature enabled (Menu 7) ? Yes ? No
? Fax Mail Plus™ feature (Menu 7) ? Yes ? No
Ken Means
"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)
? IP address and subnet mask (Menu 22.1)
? Features 9, 10, 40 and 73 installed
(Menu 13.7) ? Yes ? No
? Creation of applications in Menu 17.2.1.
Use the same password for each application:
- ID 239 with 10 sessions (password)
- ID 240 with 144 sessions (password and mailbox)
- ID 241 with 24 sessions (password)
- ID 253 with 1 session (password)
? Type 40 mailbox created for AP ID 240 ? Yes ? No
? Type 0 mailboxes created for Visual Messenger users with
client access feature enabled (Menu 7) ? Yes ? No
? Fax Mail Plus™ feature (Menu 7) ? Yes ? No
Ken Means
"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)
- Thread starter
- #16
I was able to get to the passwords and found them . Thanks. I was using those pass words.
Wer are able to ping Octel server. He was not able to vping the octel server from the visual messenger server. Do you know if 2000 is the only operating system this server can run on?
If possible can I call you on this later?
Wer are able to ping Octel server. He was not able to vping the octel server from the visual messenger server. Do you know if 2000 is the only operating system this server can run on?
If possible can I call you on this later?
only 2000 and yes
Ken Means
"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)
Ken Means
"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)
- Status
Similar threads
- Locked
- Question