Here is what I have: UC520 reconfigured to work on customer's 192.168.1.X subnet, CUE IPs are the same at 10.1.10.1 I tried changing them but it didnt work right or communicate right so I left it default and made static routes in the network to point traffic to it appropriately so I do have access to it just fine. I can ping the exchange server and open telnet sessions to it. I have enabled ALL notifications. Email notification with appropriate addresses, Group notifications, and system wide notifications. I am using the Exchange IP address directly (192.168.1.99) not a domain name. I have setup SMTP authentication with a new login and password that were created just for this purpose. Ive checked the Exchange logs when I leave a test message to see exactly where the problem lies. The CUE EHLOs in, then QUITs. No LOGIN attempts, failures, and QUITs.. just QUITs. I can't figure out why this is quitting like this without even attempting to login. The customer is running Exchange 2003 I believe. Please help. After all the trouble ive had with this system, i was expecting this to be the easiest thing. |
|||
 |
UC500.comCisco Communication Manager Express, UC520, SMB VOIP reference and community |
username format
I found that if on my demo domain (demo.com.au) if I used just username and password it would not work.
I had to log into the CUE CLI and set the SMTP authentication as "demo\username" format and it worked.