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

IP Office E-Mail Alerts 1

Status
Not open for further replies.

kef65

MIS
Jun 20, 2001
24
0
0
US
We have an IP Office 403. E-mail alerts worked when the switch and server had a public address but now both have private addresses and are behind a firewall on the same subnet. Also, the is an e-mail server in the DMZ that relays to the private network.

Another change that was made is the key server and voicemail server plug directly into the phone switch where as before they were plugged into a lan switch.

Before I go down the road of opening ports on the firewall or allowing the DMZ server to relay I want to make sure there isn't any wrong on the IP Office end, so...


1. Is there a way to test that the alerts are working but are not being "relayed" or sent? Who should be logged into the server; i.e. the administrator or mapi client?

2. What should I check to make sure the configurations didn't get goofed up during the reconfig of addresses? The internal address of the e-mail server is specified in the configs.

3. Does the internal e-mail server also have to be the LDAP server or is it that by default if it is a domain controller? IP Office uses LDAP queries to get the info it needs, right?.

There is a MAPI client installed on the voicemail server and it can send mail.

Any help would be appreciated.

Thanks
 
Sorry,

the MAPI connection is only invoked when someone tries to use the VoiceMail Email functionality.


Can you restart the voicemail, leave a message for a mailbox that will forward the message to email then post it.



Mar sin leat

endpoint
(when you get here there's no where else to go!)

 
I stopped and restarted the VMpro service as well as the MS Messenger service and was able to get a MAPI logon failure message. It only appears when I restart the service and leave a message afterwards


[2328] 394:0 mailboxes were open (but not active) when flushed
[2328] 394:CreateMailboxList 122
[2328] 394:SendBulkInfo 192.168.21.17
[2328] 394:BulkInfo Response 50 192.168.21.17
[2328] 394:BulkInfo Response 50 192.168.21.17
[2328] 394:BulkInfo Response 22 192.168.21.17
[2328] 394:Updating campaign park slot information
[2328] 174:Loading VMP configuration...
[2328] 174:New VMAIL Client
[2328] 174:Receive OPEN for session 114, call-id 19 (DISC Tone Length 0 secs)
[2328] 174:Access = ACCESS_LEAVE_VOICEMAIL:
[2328] 174: mailbox: withheld
[2328] 174: calling_party: ###
[2328] 174: display_string: withheld>withheld
[2328] 174: greeting_modifier:
[2328] 174: language: enu
[2328] 174: Acall_ident: 19
[2328] 174: - Internal: !Internal!=Y
[2328] 174:Receive ACTIVE for session 114, call-id 19
[2328] 3c0:Disk space free to record C:\Program Files\Avaya\IP Office\Voicemail Pro\VM\Accounts is 27712 MB, maximum recording is 120 secs
[2328] 3c0:Disk space free to record C:\Program Files\Avaya\IP Office\Voicemail Pro\VM\Greetings\MSG04277.WAV is 27712 MB, maximum recording is 120 secs
[2328] 3c0:StartRecording C:\Program Files\Avaya\IP Office\Voicemail Pro\VM\Greetings\MSG04277.WAV
[2328] 174:Receive CLOSE for session 114, call-id 0
[2328] 174:Removed 29920 bytes from recording (1.870000 secs)
[2328] 174:EndRecording
[2328] 174:IntuityRecordNode - the length of the recorded message is too short 1889ms < 3000ms
[2328] 174:Mailbox name retrieved=withheld new=0 old=0 saved=1
[2328] 3c0:Kill [Buffers 100 25 25 52 0] [Counts 0 0 0 0 0 5 0]
[2328] 174:New VMAIL Client
[2328] 174:Receive OPEN for session 115, call-id 21 (DISC Tone Length 0 secs)
[2328] 174:Access = ACCESS_LEAVE_VOICEMAIL:
[2328] 174: mailbox:withheld
[2328] 174: calling_party: ###
[2328] 174: display_string:withheld>withheld
[2328] 174: greeting_modifier:
[2328] 174: language: enu
[2328] 174: Acall_ident: 21
[2328] 174: - Internal: !Internal!=Y
[2328] 174:Receive ACTIVE for session 115, call-id 21
[2328] 3b0:Disk space free to record C:\Program Files\Avaya\IP Office\Voicemail Pro\VM\Accounts is 27712 MB, maximum recording is 120 secs
[2328] 3b0:Disk space free to record C:\Program Files\Avaya\IP Office\Voicemail Pro\VM\Greetings\MSG04278.WAV is 27712 MB, maximum recording is 120 secs
[2328] 3b0:StartRecording C:\Program Files\Avaya\IP Office\Voicemail Pro\VM\Greetings\MSG04278.WAV
[2328] 174:Receive CLOSE for session 115, call-id 0
[2328] 174:EndRecording
[2328] 174:New Mail Notify(1) withheld
[2328] 174:IntuityRecordNode - Sent recording to mailbox: &quot;###&quot;
[2328] 174:Mailbox name retrieved=withheld new=1 old=0 saved=1
[2328] 3b0:Kill [Buffers 100 25 25 52 0] [Counts 0 0 0 0 0 5 0]
[2328] 174:MapiUserLogin=domain\user
[2328] 394:MAPI Logon Failed 2
 
This seems to have stumped everyone. An IP Office Technician took a look and said to wait for version 2.0 which is due out this month. He said he was surprised we ever had the Alert/Forwarding working at all. We may be forced to use IMS.

 
Just got this working on our IP 403... Service has to be run under the logged in account on the VM PC.. and in VM Pro Administration->Preferences->MAPI tab... you have to enter the name and password for the outlook profile.... hope this helps ;o)
 
If you cannot still get this going, consider upgrading to version 2. The VM Pro VM to Email Feature, no longer uses MAPI but uses SMTP. Works everytime !!

ipo.gif
 
Thanks for the info -- we will be upgrading to the newer version first part of March. I will let you know how it goes.
 
March came and went. We haven't heard from you since Mt. Laurel was shut down. Let us know.
 
March came and went twice. The upgrade to 2.0 did correct the issue I was having. But now I have another issue that need I need to post. We migrated the e-mail server to a new box; keeping the same version, now the alerts are no longer working. IMS client is a dog so we decided to not use it. I thought it may be a corrupt MAPI profile but creating a new one didnt fix it. Is there a file where the e-mail server name needs to be changed? I thought this was all controlled by the MAPI/SMTP client? What's EasyMail?

jlewis1957 -- Nothing left in Ashburn either.
 
Glad the upgrade to 2.0 solved the problem. Apparently you stuck with MAPI rather than go to SMTP as MrIPO suggested.

Ashburn to ashes, a shame. Gotta love the french, non? But we all need to move on. Give me a call when you have a moment.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top