New error in Exchange 07 with PBX

[Tom Waterman]

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

[pbx support]

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?

[Tom Waterman]

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