Currently it is not possible to specify the sip transport to be used for outbound calls when provisioning a carrier. For instance, twilio supports sending calls over TLS but there is no way to accomplish this in jambonz when adding twilio as a carrier (as a workaround you can send to a sips uri, but that is different).
So what we need is to change the view of the entry when adding an outbound gateway. Currently it looks like this:
Now note one thing. If this gateway is an outbound gateway (or both inbound and outbound) the netmask is actually not providing any useful information. For an outbound gateway we always want an exact IP (so the netmask is 32). Only when a gateway is inbound-only should the netmask dropdown even be enabled.
With that in mind, I would like to change the UI as follows:
If the gateway has outbound checked, hide the netmask dropdown and in it's place have a dropdown with 3 values: 'UDP','TCP','TLS'. UDP should be the default.
If the gateway is inbound-only (and new gateways should default to that) then it should show as above - netmask dropdown shows and this new transport dropdown is hidden.
This issue will require changes in webapp, api server, db helper, and sbc-outbound
Currently it is not possible to specify the sip transport to be used for outbound calls when provisioning a carrier. For instance, twilio supports sending calls over TLS but there is no way to accomplish this in jambonz when adding twilio as a carrier (as a workaround you can send to a sips uri, but that is different).
So what we need is to change the view of the entry when adding an outbound gateway. Currently it looks like this:
Now note one thing. If this gateway is an outbound gateway (or both inbound and outbound) the netmask is actually not providing any useful information. For an outbound gateway we always want an exact IP (so the netmask is 32). Only when a gateway is inbound-only should the netmask dropdown even be enabled.
With that in mind, I would like to change the UI as follows:
This issue will require changes in webapp, api server, db helper, and sbc-outbound