Try this setup:
• The type of server used (IMAP)
• Account (User's) name and password (user's voice mailbox number and password)
• Email Address – Extension Number @ voice mail server IP address
• Incoming voice mail/messaging server name (voice mail / CS IP address)
• Outgoing voice mail/messaging server name (the user's default messaging server name / IP @)
• Hit "Next" - you should get a warning asking you to change the email address – NO
• Test
Cannot connect to 4635 imap server
Re: Cannot connect to 4635 imap server
We don't see things the way they are; we see things the way we are!
Re: Cannot connect to 4635 imap server
This setup made no difference.
- cavagnaro
- Alcatel Unleashed Certified Guru
- Posts: 7014
- Joined: 14 Sep 2005 19:45
- Location: Brasil, Porto Alegre
- Contact:
Re: Cannot connect to 4635 imap server
I have no more ideas, only left is you to run wireshark and see what is really happening on the negotiation of the protocol.
Ignorance is not the problem, the problem is the one who doesn't want to learn
OTUC/ICS ACFE/ACSE R3.0/4.0/5.0/6.0
Certified Genesys CIV 8.5
Certified Genesys Troubleshooting 8.5
Certified Genesys BEP 8.x
Genesys Developer
OTUC/ICS ACFE/ACSE R3.0/4.0/5.0/6.0
Certified Genesys CIV 8.5
Certified Genesys Troubleshooting 8.5
Certified Genesys BEP 8.x
Genesys Developer
Re: Cannot connect to 4635 imap server
jbower - In your first post you said that you did a bascul.
I suggest that you stop telephony on the backup CPU (Swinst¬ Option1¬ Option 7 - Stop before telephony) and reboot the main. With a simple bascul i doubt if your OPS locks have been activated. Lock 314 has conditions for rebooting or not!
I suggest that you stop telephony on the backup CPU (Swinst¬ Option1¬ Option 7 - Stop before telephony) and reboot the main. With a simple bascul i doubt if your OPS locks have been activated. Lock 314 has conditions for rebooting or not!
We don't see things the way they are; we see things the way we are!
Re: Cannot connect to 4635 imap server
I just wanted to thank both of you for your help. Problem has been solved. The voice network is on it's own vlan. After going into the core switch permissions were not given for the voice vlan to communicate with the DNS servers. After giving permissions it immediately worked. So once again thanks for your input.