Jump to content
Vodia PBX forum
Sign in to follow this  
Tom Waterman

New error in Exchange 07 with PBX

Recommended Posts

Ok I managed to work through the first error but I am stumped on thei one. When I send the call to exchange it states:

 

Event Type: Warning

Event Source: MSExchange Unified Messaging

Event Category: UMCore

Event ID: 1109

Date: 4/15/2010

Time: 2:10:11 PM

User: N/A

Computer: JASCOMX

Description:

The Unified Messaging server has received an inbound call that has an invalid extension "3300" for UM dial plan "PBXnSIP". The call ID is "e8e8c8e9@pbx".

 

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

 

Now I know it is getting the right extension number because 3300 is the one I want. In my UM Dial plan I have 3300 listed under the Associated Subscriber access.

 

Also the Exchange server is sending bac a 302 Moved Temporarily error.

 

Can anyone tell me what I am doing wrong?

 

Thank you for your help.

 

Tom

Share this post


Link to post
Share on other sites
Ok I managed to work through the first error but I am stumped on thei one. When I send the call to exchange it states:

 

Event Type: Warning

Event Source: MSExchange Unified Messaging

Event Category: UMCore

Event ID: 1109

Date: 4/15/2010

Time: 2:10:11 PM

User: N/A

Computer: JASCOMX

Description:

The Unified Messaging server has received an inbound call that has an invalid extension "3300" for UM dial plan "PBXnSIP". The call ID is "e8e8c8e9@pbx".

 

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

 

Now I know it is getting the right extension number because 3300 is the one I want. In my UM Dial plan I have 3300 listed under the Associated Subscriber access.

 

Also the Exchange server is sending bac a 302 Moved Temporarily error.

 

Can anyone tell me what I am doing wrong?

 

Thank you for your help.

 

Tom

 

On the trunk settings page, can you choose "Trunk Destination:" to be "Microsoft Exchange" and see that takes care of the issue?

Share this post


Link to post
Share on other sites
On the trunk settings page, can you choose "Trunk Destination:" to be "Microsoft Exchange" and see that takes care of the issue?

 

 

Well I finnaly fixed the issue. This client is still on the version 3. I found that if you have exchange 2007 and you install SP1 which this customer did, it more often than not will break UM. I just delete the entire config from exchange and started over. Within 45 minutes it was working. Thanks Microsoft.

 

 

Tom

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
Sign in to follow this  

×
×
  • Create New...