hosted Posted April 22, 2010 Report Share Posted April 22, 2010 I upgraded our dev box to V4 RC and the global trunks arnt so global anymore.. everything is 404 now. Quote Link to comment Share on other sites More sharing options...
pbx support Posted April 23, 2010 Report Share Posted April 23, 2010 I upgraded our dev box to V4 RC and the global trunks arnt so global anymore.. everything is 404 now. In the RC, at log level 5, you should see the log that says(at least on the incoming calls), whether the trunk is global or not. Do you see any such message? Quote Link to comment Share on other sites More sharing options...
hosted Posted April 23, 2010 Author Report Share Posted April 23, 2010 2010/04/23 07:18:31: Global trunk INBOUND 31@localhost could not identify user for 8012149000 rolled back to 4.0.1.3452 (Linux) and its just fine. Quote Link to comment Share on other sites More sharing options...
shopcomputer Posted April 23, 2010 Report Share Posted April 23, 2010 2010/04/23 07:18:31: Global trunk INBOUND 31@localhost could not identify user for 8012149000 rolled back to 4.0.1.3452 (Linux) and its just fine. Global trunk vitelity in@pbx.company.com could not identify user for 7185696635 same here, running win32. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted April 25, 2010 Report Share Posted April 25, 2010 Global trunk vitelity in@pbx.company.com could not identify user for 7185696635 same here, running win32. I did a quick try here. If I am using the "Explicitly list addresses for inbound traffic" then it works; without that setting I also get not found. We changed some things in the way the PBX treats trunks. Previously, the outbound proxy was also the inbound proxy. That caused a lot of confusion, so we decided to add an explicit setting for the inbound traffic. Seems for "normal" domain trunks that algororithm is backward compatible. But for global trunks it does not. Will further investigate; but setting the inbound addresses seems to be the solution for global trunks now. Quote Link to comment Share on other sites More sharing options...
hosted Posted April 26, 2010 Author Report Share Posted April 26, 2010 but setting the inbound addresses seems to be the solution for global trunks now. What does this mean? Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted April 26, 2010 Report Share Posted April 26, 2010 What does this mean? Put the address of the service provider into "Explicitly list addresses for inbound traffic", for example "12.32.12.32" or a DNS A/AAAA name like "sip.proxy.com". Quote Link to comment Share on other sites More sharing options...
shopcomputer Posted May 4, 2010 Report Share Posted May 4, 2010 Put the address of the service provider into "Explicitly list addresses for inbound traffic", for example "12.32.12.32" or a DNS A/AAAA name like "sip.proxy.com". Just upgraded again and put the address in the "Explicitly list addresses for inbound traffic", still global trunk was not finding inbound users, so I downgraded again to 4.0.1.3452 (Win32) 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.