Solved Calls to Exchange not sent to trunk

[c.holloway]

Good afternoon!

I'm working on a client that is running version 15.5 sp5. I am running into issues with a SIP trunk I have set up for MS Exchange.

I took a packet capture and what I'm seeing is that the call hits 3CX properly but instead of hitting the pilot number of the trunk and going into Exchange, 3CX appears to be looking locally and the call fails with "Server Internal Error". More specifically, I see a single invite for 5001 (Exchange trunk pilot) @3cxip:5060 but NO follow up Invite for 5001@exchangeserverIP:5060

I have another SIP trunk set up to a paging appliance. When I call this trunk, in the capture I see two invites. First an invite is set to 7001(the pilot of this trunk)@3cxip:5060. Then immediately after, an invite is sent to 7001@pagingsystemip:5060. This trunk works without issues so I'm assuming that what the first dialog is missing is the followup invite that points the call into the correct IP for Exchange

I'm happy to provide more information on this, thank you in advance for your help!

 

[leejor]

If one works and the other doesn't...you have to ask...what, in 3CX, is set-up differently between 5001 and 7001? If you call 5001 number from an extension, does that call route correctly? Could 5001 exist elsewhere? SIP ID?

Will 5001 work when used for paging, will 7001 work when used for MS exchange? Is it a number issue, or something with the final destination?

 

[c.holloway]

If one works and the other doesn't...you have to ask...what, in 3CX, is set-up differently between 5001 and 7001? If you call 5001 number from an extension, does that call route correctly? Could 5001 exist elsewhere? SIP ID?

Will 5001 work when used for paging, will 7001 work when used for MS exchange? Is it a number issue, or something with the final destination?

All of these calls are taking place from an extension, without the Exchange portion I can't take the system live for outside calls.

I will doublecheck but am certain 5001 is not used anywhere else as everything in the 5xxx range is reserved for VM and AA pilots.

I neglected to mention this but I can't swap the pilot numbers as I'm migrating them from CME to 3CX and the pilot numbers are also used by trunks in CME (which work fine)

 

[c.holloway]

Hey guys I found my issue, it was in Exchange.

Even though I had the other UM IP Gateway disabled (the one that pointed at the CME gateway) this setup would not work until i deleted the CME IP gateway entirely. After that calls started coming in to Exchange without further issue

 

[YiannisH_3CX]

Glad to see the issue has been resolved and thank for updating the thread with your solution