-
-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fear: Move PRIVATE_VOIP_NETWORK_CIDR configuration to Mysql #157
Comments
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: / expected","stack":"Error: Invalid argument: / expected\n at new CIDR (/home/admin/apps/sbc-inbound/node_modules/ip6addr/ip6addr.js:352:13)\n at Object.createCIDR (/home/admin/apps/sbc-inbound/node_modules/ip6addr/ip6addr.js:711:12)\n at Matcher.addNetworkClass (/home/admin/apps/sbc-inbound/node_modules/cidr-matcher/src/Matcher.js:20:24)\n at new Matcher (/home/admin/apps/sbc-inbound/node_modules/cidr-matcher/src/Matcher.js:15:14)\n at isPrivateVoipNetwork (/home/admin/apps/sbc-inbound/lib/utils.js:209:23)\n at CallSession.connect (/home/admin/apps/sbc-inbound/lib/call-session.js:190:22)\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)"},"privateNetworkCidr":"22.0.33.105","msg":"Error checking private network CIDR, probably misconfigured must be a comma separated list of CIDRs"} 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 |
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
The text was updated successfully, but these errors were encountered: