Closed vdharashive closed 1 month ago
what is the scenario where it would ever need to change, once set? Short of moving the system to a new network, I don't understand the need for this feature
@davehorton when jambonz is used to connect with multiple client as sas service , in that case there will be new client getting added , some client choose to connect over private network using VPN, in that case need to provide these private ips to send media and sip ack over private IP rather then public ips of jambonz
@davehorton when we put single ip in Private Network CIDR for example : 22.0.33.105 then it wont work giving below error:
43|sbc-inbound | {"level":30, "time": "2024-08-16T09:26:44.033Z","pid":46534,"hostname":"ip-22-0-30-164","err":{"type":"Error","message":"Invalid argument:
when we add multiple ip like these : 22.0.33.105/32,22.0.33.0/24 its working fine...
you must add that single arg as 22.0.33.105/32, ie with netmask
you must add that single arg as 22.0.33.105/32, ie with netmask
Without a comma its working fine i have used only [22.0.33.105/32] now.
PRIVATE_VOIP_NETWORK_CIDR any change in this require restart of services, which is not feasible , hence this configuration to move at db level