Don Posted November 9, 2010 Report Share Posted November 9, 2010 We just converted a PBX that has 3 Domains from 3.X to 4.X. This PBX has several incoming Trunks loaded in the LOCALHOST domain. Previously we simply routed the calls to the appropriate domain by setting the destination IP address in the M600 (Audiocodes) based on the incoming number. So for example: 850xxxxxxx (x = valid DID number) is sent to ip address "resortsands" and we have a domain built that = "resortsands" * (wildcard for all not matched numbers) is sent to ip address 10.10.4.5 (PBXnSIP private IP address) As stated this works fine in 3.4.0.3201 but when we went to 4.0.1.3499 all incoming calls are getting a 404 not found. It seems that the PBX is not looking in the resortsands domain for a match even though that is the IP address that is being delivered. Is there a new datafill or parameter requirement in 4.X that we are missing? Quote Link to comment Share on other sites More sharing options...
Don Posted November 9, 2010 Author Report Share Posted November 9, 2010 It runs out that we had to build the trunk as an incoming only trunk in each of the other domains for the calls to be delivered there even though they are routed to that specific domain from the M600 (Audiocodes) directly. This is apparently a change from 3.X. FYI to all. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.