Can you not use the technique used with chan_sip, of having all the trunks enter by the same context, and separating them based on the contact user provided when you registered. It is possible that you would have to choose one for the IP address match, and put something harmless in the other ones.
However, I still think you have the wrong product.
hi, yes the currently not working trunks do work when registered via softphone. They do receive incoming calls.
All endpoints are 1/1 identical , I have checked them over and over again. I generate the sql insert statement from file, so I know all settings are the same because the only thing that does change is the trunk number and password.
Hi , I tried this approach . I added the not working (for inbound) trunks to the same context and added the IP as the match parameter. When I do this, I get 404 not found. When I inspected the debug log, it was trying to match the call from trunk A to trunk B and still says “extension not found in context test(this was the context I made up)” if I remove the IP and try to match it via SIPheader: /number/, then I keep getting 401 not authorized. Strange as I did not define any auth (for incoming).
The authorisation request will be to confuse attackers. It stops them distinguishing between unknown users and valid users with incorrect passwords.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.