From rfuchs at sipwise.com Tue Sep 3 12:50:11 2024 From: rfuchs at sipwise.com (Richard Fuchs) Date: Tue, 3 Sep 2024 12:50:11 -0400 Subject: [Spce-user] [EXTERNAL] Unable to enable the firewall. In-Reply-To: References: Message-ID: <6d5a5452-cd57-4d41-8850-40db3d9526ba@sipwise.com> On 14/08/2024 13.34, Chinye Nke wrote: > Hi > > I am unable to enable the firewall. > > Using the default configuration in /etc/ngcp-config/config.yml, with > security.firewall.enable=yes, I am able to run 'ngcpcfg apply' with no > issues but when I run iptables-apply, i get the below error. Hi, Currently the workaround is to first stop the rtpengine service (`ngcp-service stop rtpengine`), then execute `iptables-apply`, then restart rtpengine. We should have better support for this scenario in the near future. Cheers -------------- next part -------------- An HTML attachment was scrubbed... URL: From javier.valencia at voiper.es Mon Sep 16 14:53:40 2024 From: javier.valencia at voiper.es (Javier Valencia) Date: Mon, 16 Sep 2024 20:53:40 +0200 Subject: [Spce-user] Physical interface VS virtual interface on iptables rules Message-ID: Hi there! My NGCP CE mr9.5.7 (on bullseye (11.10) 5.10.0-30-amd64 SMP) box isn't responding on sip_ext, because it's generating "/etc/iptables/rules.v4" with virtual ethernet interface instead physical ethernet interface. In example: -A INPUT -i *neth0:0* -p tcp --dport 5060 -j ACCEPT -m comment --comment "sip_ext" Must be: -A INPUT -i *neth0* -p tcp --dport 5060 -j ACCEPT -m comment --comment "sip_ext" When I delete the first line and insert into iptables (with cli commands) the second line, the server starts to respond. There an *iface* alternative variable to make a custom template? [% FOREACH iface IN hosts.$hostname.interfaces; FOREACH net IN hosts.$hostname.$iface.type; # handle certain aliases IF net != 'rtp_int' && net.match('^rtp_'); net_alias = 'rtp_ext'; ELSIF net.match('^sip_ext_'); net_alias = 'sip_ext'; ELSE; net_alias = net; END; IF rules.$net_alias && rules.$net_alias.size && iface != 'lo' && hosts.$hostname.$iface.ip; FOREACH rule IN rules.$net_alias; -%] -A INPUT -i [% *iface* %] [% rule %] -m comment --comment "[% net %]" [% END; END; END; END; -%] thx P.S: I'm so sorry about my english -------------- next part -------------- An HTML attachment was scrubbed... URL: From mprokop at sipwise.com Wed Sep 18 02:49:27 2024 From: mprokop at sipwise.com (Michael Prokop) Date: Wed, 18 Sep 2024 08:49:27 +0200 Subject: [Spce-user] [EXTERNAL] Physical interface VS virtual interface on iptables rules In-Reply-To: References: Message-ID: <2024-09-18T08-44-32@devnull.michael-prokop.at> Hi, * Javier Valencia [Mon Sep 16, 2024 at 08:53:40PM +0200]: > Hi there! > > My NGCP CE mr9.5.7 (on bullseye (11.10) 5.10.0-30-amd64 SMP) box isn't > responding on sip_ext, because it's generating "/etc/iptables/rules.v4" > with virtual ethernet interface instead physical ethernet interface. > > In example: > -A INPUT -i *neth0:0* -p tcp --dport 5060 -j ACCEPT -m comment --comment > "sip_ext" > > Must be: > -A INPUT -i *neth0* -p tcp --dport 5060 -j ACCEPT -m comment --comment > "sip_ext" > > When I delete the first line and insert into iptables (with cli commands) > the second line, the server starts to respond. [...] Aha interesting. Before we're coming up with a workaround through /etc/ngcp-config/config.yml or ngcpcfg patchtt.tt2 for this, I'd like to understand your situation and how to properly fix this. :) What kind of environment is this with this virtual ethernet interface? What's inside your /etc/ngcp-config/network.yml? What's output of `ip a` + `ip link` on your system? PS: please make sure to subscribe to the mailing list, otherwise your messages end up in moderation queue (we just let it through) and you might also miss replies. regards -mika- From dbusso at sipwise.com Wed Sep 18 03:57:40 2024 From: dbusso at sipwise.com (Dario Busso) Date: Wed, 18 Sep 2024 09:57:40 +0200 Subject: [Spce-user] [EXTERNAL] Physical interface VS virtual interface on iptables rules In-Reply-To: References: Message-ID: The rule you shared is for TCP on the interface's port 5060. I don't know if you meant enabling it or the UDP protocol. It depends on which interface you have assigned the type "sip_ext" in the network.yml file; based on that, the scripts work accordingly to create the appropriate firewall rules. Dario On Wed, Sep 18, 2024 at 8:30?AM Javier Valencia wrote: > Hi there! > > My NGCP CE mr9.5.7 (on bullseye (11.10) 5.10.0-30-amd64 SMP) box isn't > responding on sip_ext, because it's generating "/etc/iptables/rules.v4" > with virtual ethernet interface instead physical ethernet interface. > > In example: > -A INPUT -i *neth0:0* -p tcp --dport 5060 -j ACCEPT -m comment --comment > "sip_ext" > > Must be: > -A INPUT -i *neth0* -p tcp --dport 5060 -j ACCEPT -m comment --comment > "sip_ext" > > When I delete the first line and insert into iptables (with cli commands) > the second line, the server starts to respond. > > There an *iface* alternative variable to make a custom template? > [% > FOREACH iface IN hosts.$hostname.interfaces; > FOREACH net IN hosts.$hostname.$iface.type; > # handle certain aliases > IF net != 'rtp_int' && net.match('^rtp_'); > net_alias = 'rtp_ext'; > ELSIF net.match('^sip_ext_'); > net_alias = 'sip_ext'; > ELSE; > net_alias = net; > END; > > IF rules.$net_alias && rules.$net_alias.size && iface != 'lo' && > hosts.$hostname.$iface.ip; > FOREACH rule IN rules.$net_alias; > -%] > -A INPUT -i [% *iface* %] [% rule %] -m comment --comment "[% net %]" > [% > END; > END; > END; > END; > -%] > > thx > > P.S: I'm so sorry about my english > > -- > Spce-user mailing list > Spce-user at lists.sipwise.com > http://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com > -------------- next part -------------- An HTML attachment was scrubbed... URL: From javier.valencia at voiper.es Wed Sep 18 18:44:02 2024 From: javier.valencia at voiper.es (Javier Valencia) Date: Thu, 19 Sep 2024 00:44:02 +0200 Subject: [Spce-user] [EXTERNAL] Physical interface VS virtual interface on iptables rules In-Reply-To: <2024-09-18T08-44-32@devnull.michael-prokop.at> References: <2024-09-18T08-44-32@devnull.michael-prokop.at> Message-ID: Hi Mika. *What kind of environment is this with this virtual ethernet interface?* It's a virtual (neth0:0 and neth0:1) ethernet adapter over physical (neth0) one. *What's inside your /etc/ngcp-config/network.yml?* # cat /etc/ngcp-config/network.yml --- hosts: self: dbnode: '1' interfaces: - lo - neth0 - neth0:0 - neth0:1 lo: cluster_sets: - default ip: 127.0.0.1 netmask: 255.255.255.0 shared_ip: [] shared_v6ip: [] type: - sip_int - ha_int - web_ext - web_int - aux_ext - ssh_ext - api_int - rtp_int - stor_int v6ip: ::1 v6netmask: 128 neth0: dns_nameservers: - XXX.XXX.XXX.XXX - XXX.XXX.XXX.XXX gateway: XXX.XXX.XX.XXX hwaddr: XX:XX:XX:XX:XX:XX ip: XXX.XXX.XXX.100 netmask: 255.255.255.0 type: - ssh_ext neth0:0: ip: XXX.XXX.XXX.244 netmask: 255.255.255.255 type: - sip_ext - rtp_ext - ssh_ext neth0:1: ip: XXX.XXX.XXX.249 netmask: 255.255.255.255 type: - ssh_ext role: - proxy - lb - mgmt - rtp - db - storage status: online swraiddevices: [] sysdescr: '' syslocation: '' sysname: '' *What's output of `ip a` + `ip link` on your system?* # ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: neth0: mtu 1500 qdisc mq state UP group default qlen 1000 link/ether XX:XX:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff altname enp1s0f0 altname eno1 inet XXX.XXX.XXX.100/24 brd XXX.XXX.XXX.255 scope global neth0 valid_lft forever preferred_lft forever inet XXX.XXX.XXX.244/32 brd XXX.XXX.XXX.244 scope global neth0:0 valid_lft forever preferred_lft forever inet XXX.XXX.XXX.249/32 brd XXX.XXX.XXX.249 scope global neth0:1 valid_lft forever preferred_lft forever inet6 XXXX::XXXX:XXXX:XXXX:7834/64 scope link valid_lft forever preferred_lft forever 3: neth1: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether XX:XX:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff altname enp1s0f1 altname eno2 4: neth2: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether XX:XX:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff altname enp2s0f0 altname eno3 5: neth3: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether XX:XX:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff altname enp2s0f1 altname eno4 6: neth4: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether XX:XX:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff altname enp132s0f0 7: neth5: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether XX:XX:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff altname enp132s0f1 # ip link 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: neth0: mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000 link/ether XX:XX:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff altname enp1s0f0 altname eno1 3: neth1: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether XX:XX:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff altname enp1s0f1 altname eno2 4: neth2: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether XX:XX:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff altname enp2s0f0 altname eno3 5: neth3: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether XX:XX:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff altname enp2s0f1 altname eno4 6: neth4: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether XX:XX:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff altname enp132s0f0 7: neth5: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether XX:XX:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff altname enp132s0f1 Regards, JV [image: Profile picture] Javier Valencia Chief Technology Officer VoIPer Telecom, S.L. [image: Company logo] [image: facebook] [image: twitter] [image: instagram] [image: linkedin] (+34) 951 562 080 (+34) 687 486 759 javier.valencia at voiper.es voiper.es Calle R?o Benamargosa, 15, 29651 Mijas Costa (M?laga) El mi?, 18 sept 2024 a las 8:49, Michael Prokop () escribi?: > Hi, > > * Javier Valencia [Mon Sep 16, 2024 at 08:53:40PM +0200]: > > Hi there! > > > > My NGCP CE mr9.5.7 (on bullseye (11.10) 5.10.0-30-amd64 SMP) box isn't > > responding on sip_ext, because it's generating "/etc/iptables/rules.v4" > > with virtual ethernet interface instead physical ethernet interface. > > > > In example: > > -A INPUT -i *neth0:0* -p tcp --dport 5060 -j ACCEPT -m comment --comment > > "sip_ext" > > > > Must be: > > -A INPUT -i *neth0* -p tcp --dport 5060 -j ACCEPT -m comment --comment > > "sip_ext" > > > > When I delete the first line and insert into iptables (with cli commands) > > the second line, the server starts to respond. > [...] > > Aha interesting. Before we're coming up with a workaround through > /etc/ngcp-config/config.yml or ngcpcfg patchtt.tt2 for this, I'd > like to understand your situation and how to properly fix this. :) > > What kind of environment is this with this virtual ethernet interface? > What's inside your /etc/ngcp-config/network.yml? > What's output of `ip a` + `ip link` on your system? > > PS: please make sure to subscribe to the mailing list, otherwise > your messages end up in moderation queue (we just let it through) > and you might also miss replies. > > regards > -mika- > -------------- next part -------------- An HTML attachment was scrubbed... URL: From javier.valencia at voiper.es Wed Sep 18 18:53:12 2024 From: javier.valencia at voiper.es (Javier Valencia) Date: Thu, 19 Sep 2024 00:53:12 +0200 Subject: [Spce-user] [EXTERNAL] Physical interface VS virtual interface on iptables rules In-Reply-To: References: Message-ID: Hi Dar?o. It is one of several rules, I simply wanted to give an example. As you can see, these are all the affected rules in iptables: 6487 3175K ACCEPT udp -- neth0:0 * 0.0.0.0/0 0.0.0.0/0 udp dpt:5060 /* sip_ext */ 185 8576 ACCEPT tcp -- neth0:0 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:5060 /* sip_ext */ 136 7028 ACCEPT tcp -- neth0:0 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:5061 /* sip_ext */ 61 2996 ACCEPT tcp -- neth0:0 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:5222 /* sip_ext */ 30 1420 ACCEPT tcp -- neth0:0 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:5269 /* sip_ext */ When the interface specified by the iptables rules is *neth0:0* there is no traffic of any kind, however, if it is *neth0* there is no problem. This is because *sip_ext* is on neth0:0 (virtual), but iptables needs the physical network interface. The other iptables rules aren't affected. Regards, JV El mi?, 18 sept 2024 a las 9:57, Dario Busso () escribi?: > The rule you shared is for TCP on the interface's port 5060. I don't know > if you meant enabling it or the UDP protocol. > It depends on which interface you have assigned the type "sip_ext" in the > network.yml file; based on that, the scripts work accordingly to create the > appropriate firewall rules. > Dario > > On Wed, Sep 18, 2024 at 8:30?AM Javier Valencia > wrote: > >> Hi there! >> >> My NGCP CE mr9.5.7 (on bullseye (11.10) 5.10.0-30-amd64 SMP) box isn't >> responding on sip_ext, because it's generating "/etc/iptables/rules.v4" >> with virtual ethernet interface instead physical ethernet interface. >> >> In example: >> -A INPUT -i *neth0:0* -p tcp --dport 5060 -j ACCEPT -m comment --comment >> "sip_ext" >> >> Must be: >> -A INPUT -i *neth0* -p tcp --dport 5060 -j ACCEPT -m comment --comment >> "sip_ext" >> >> When I delete the first line and insert into iptables (with cli commands) >> the second line, the server starts to respond. >> >> There an *iface* alternative variable to make a custom template? >> [% >> FOREACH iface IN hosts.$hostname.interfaces; >> FOREACH net IN hosts.$hostname.$iface.type; >> # handle certain aliases >> IF net != 'rtp_int' && net.match('^rtp_'); >> net_alias = 'rtp_ext'; >> ELSIF net.match('^sip_ext_'); >> net_alias = 'sip_ext'; >> ELSE; >> net_alias = net; >> END; >> >> IF rules.$net_alias && rules.$net_alias.size && iface != 'lo' && >> hosts.$hostname.$iface.ip; >> FOREACH rule IN rules.$net_alias; >> -%] >> -A INPUT -i [% *iface* %] [% rule %] -m comment --comment "[% net %]" >> [% >> END; >> END; >> END; >> END; >> -%] >> >> thx >> >> P.S: I'm so sorry about my english >> >> -- >> Spce-user mailing list >> Spce-user at lists.sipwise.com >> http://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dbusso at sipwise.com Thu Sep 19 02:14:50 2024 From: dbusso at sipwise.com (Dario Busso) Date: Thu, 19 Sep 2024 08:14:50 +0200 Subject: [Spce-user] [EXTERNAL] Physical interface VS virtual interface on iptables rules In-Reply-To: References: Message-ID: That's by design: as you can see, you have correctly set up the type "sip_ext" to net0:0 (virtual interface), and the NGCP framework uses that one in the FW rules to protect the external access, allowing only the ports connected to the services. We will check and see if there is a bug in the created FW rules and provide a fix. Thank you for your report. Dario On Thu, Sep 19, 2024 at 12:53?AM Javier Valencia wrote: > Hi Dar?o. > > It is one of several rules, I simply wanted to give an example. > > As you can see, these are all the affected rules in iptables: > > 6487 3175K ACCEPT udp -- neth0:0 * 0.0.0.0/0 > 0.0.0.0/0 udp dpt:5060 /* sip_ext */ > 185 8576 ACCEPT tcp -- neth0:0 * 0.0.0.0/0 > 0.0.0.0/0 tcp dpt:5060 /* sip_ext */ > 136 7028 ACCEPT tcp -- neth0:0 * 0.0.0.0/0 > 0.0.0.0/0 tcp dpt:5061 /* sip_ext */ > 61 2996 ACCEPT tcp -- neth0:0 * 0.0.0.0/0 > 0.0.0.0/0 tcp dpt:5222 /* sip_ext */ > 30 1420 ACCEPT tcp -- neth0:0 * 0.0.0.0/0 > 0.0.0.0/0 tcp dpt:5269 /* sip_ext */ > > When the interface specified by the iptables rules is *neth0:0* there is > no traffic of any kind, however, if it is *neth0* there is no > problem. This is because *sip_ext* is on neth0:0 (virtual), but iptables > needs the physical network interface. > > The other iptables rules aren't affected. > > Regards, > JV > > > El mi?, 18 sept 2024 a las 9:57, Dario Busso () > escribi?: > >> The rule you shared is for TCP on the interface's port 5060. I don't know >> if you meant enabling it or the UDP protocol. >> It depends on which interface you have assigned the type "sip_ext" in the >> network.yml file; based on that, the scripts work accordingly to create the >> appropriate firewall rules. >> Dario >> >> On Wed, Sep 18, 2024 at 8:30?AM Javier Valencia < >> javier.valencia at voiper.es> wrote: >> >>> Hi there! >>> >>> My NGCP CE mr9.5.7 (on bullseye (11.10) 5.10.0-30-amd64 SMP) box isn't >>> responding on sip_ext, because it's generating "/etc/iptables/rules.v4" >>> with virtual ethernet interface instead physical ethernet interface. >>> >>> In example: >>> -A INPUT -i *neth0:0* -p tcp --dport 5060 -j ACCEPT -m comment >>> --comment "sip_ext" >>> >>> Must be: >>> -A INPUT -i *neth0* -p tcp --dport 5060 -j ACCEPT -m comment --comment >>> "sip_ext" >>> >>> When I delete the first line and insert into iptables (with cli >>> commands) the second line, the server starts to respond. >>> >>> There an *iface* alternative variable to make a custom template? >>> [% >>> FOREACH iface IN hosts.$hostname.interfaces; >>> FOREACH net IN hosts.$hostname.$iface.type; >>> # handle certain aliases >>> IF net != 'rtp_int' && net.match('^rtp_'); >>> net_alias = 'rtp_ext'; >>> ELSIF net.match('^sip_ext_'); >>> net_alias = 'sip_ext'; >>> ELSE; >>> net_alias = net; >>> END; >>> >>> IF rules.$net_alias && rules.$net_alias.size && iface != 'lo' && >>> hosts.$hostname.$iface.ip; >>> FOREACH rule IN rules.$net_alias; >>> -%] >>> -A INPUT -i [% *iface* %] [% rule %] -m comment --comment "[% net %]" >>> [% >>> END; >>> END; >>> END; >>> END; >>> -%] >>> >>> thx >>> >>> P.S: I'm so sorry about my english >>> >>> -- >>> Spce-user mailing list >>> Spce-user at lists.sipwise.com >>> http://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com >>> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From mmalkov at sipwise.com Mon Sep 23 12:41:11 2024 From: mmalkov at sipwise.com (Mykola Malkov) Date: Mon, 23 Sep 2024 19:41:11 +0300 Subject: [Spce-user] New Sipwise C5 CE mr12.5.1 is now available Message-ID: <3b494981-c940-429a-932b-3669bbe7289c@sipwise.com> Hello everyone, We would like to inform you that a new release of Sipwise C5, version mr12.5.1, is now available! You can find a list of new features and changes on our website at https://www.sipwise.com/sipwise-c5-mr12-5-1-released/ mr12.5.1 will be supported is supported until mr13.0.1. You can find the detailed release plan on our public calendar at https://www.sipwise.com/releases/ We have uploaded the Install-CD media, Vagrant box, Virtualbox, and AMI images. Please refer to the handbook at https://www.sipwise.com/doc/mr12.5.1/spce for further details. If you encounter any issues, please report them to this mailing list. Thank you for being part of our community! -- WBR --- Mykola Malkov From edo.ekunwe at gmail.com Sun Sep 29 06:19:48 2024 From: edo.ekunwe at gmail.com (Edo) Date: Sun, 29 Sep 2024 05:19:48 -0500 Subject: [Spce-user] How to setup subscriber as SIP Trunk Message-ID: All I am looking for example configuration(s) of how to setup a subscriber as a SIP trunk as mentioned below. I am really trying to handle multiple users behind another IP PBX system with IP authentication [image: image.png] I looked at subscriber preferences but could not find any idea leading to success. Please assist. -- ----- Ekunwe Tel: 601.497.3932 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 85741 bytes Desc: not available URL: From walter at myrepublic.net Mon Sep 30 20:57:05 2024 From: walter at myrepublic.net (Walter Klomp) Date: Tue, 1 Oct 2024 08:57:05 +0800 Subject: [Spce-user] How to setup subscriber as SIP Trunk In-Reply-To: References: Message-ID: [image: Signature header] Hi Edo There is no difference between a subscriber and a sip trunk. > > A sip trunk just has optional multiple numbers and more channels than a > subscriber. > > I think you need to set e164 to ruri for the ddi to be sent to the sip > trunk client. > > Obviously you also need to set the numbers in allowed ddi and the add the > aliases. > > There will be only 1 authentication, which is typically the main sip trunk > number. You can use ip authentication as well. But you have to create a > static registration entry otherwise inbound calls to the sip trunk will not > work. The PBX connected to the sip trunk doesn?t need to authenticate in > this case. > > Note the users will connect to the PBX and NOT Sipwise in this case. > > [image: Signature header] > [image: Signature image] > Walter Klomp > Head of Voice Network > [image: Email] walter at myrepublic.net > Beyond Work : > 11 Lorong 3 Toa Payoh, #04-11/15, Jackson Square, Block B, Singapore 319579 > www.myrepublic.net > * [image: Facebook-f] * * > [image: Instagram] * * > [image: Twitter] * * > [image: Linkedin-in] * > The information in this message is privileged and confidential. If you are > not the intended recipient of this email, please don't read, copy, use, > distribute or tell anyone about it; kindly destroy it and notify the sender > by return email. Please advise immediately if you or your employer does not > consent to email for messages of this kind. Any content that is not > concerned with MyRepublic business reflects the views of the sender only > and not those of MyRepublic. > > > On Mon, 30 Sep 2024 at 19:00, Edo wrote: > >> All I am looking for example configuration(s) of how to setup a >> subscriber as a SIP trunk as mentioned below. I am really trying to handle >> multiple users behind another IP PBX system with IP authentication >> > I looked at subscriber preferences but could not find any idea leading to >> success. >> >> Please assist. >> >> >> -- >> ----- >> Ekunwe >> Tel: 601.497.3932 >> -- >> Spce-user mailing list >> Spce-user at lists.sipwise.com >> http://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com >> > -- The contents of this email and any attachments are confidential and may also be privileged. You must not disseminate the contents of this email and any attachments without permission of the sender. If you have received this email by mistake, please delete all copies and inform the sender immediately. You may refer to our company's Privacy Policy here . -------------- next part -------------- An HTML attachment was scrubbed... URL: From stefanormc at gmail.com Mon Sep 30 10:23:09 2024 From: stefanormc at gmail.com (Stefano Rogna Manassero di Costigliole) Date: Mon, 30 Sep 2024 10:23:09 -0400 Subject: [Spce-user] How to setup subscriber as SIP Trunk In-Reply-To: References: Message-ID: Hello Edo, I usually register the trunk with user/pwd as usual and it works fine. You can also authenticate on the IP as described but I never had the need to. Hope it helps. Ciao Stefano On 30 September 2024 at 13:01:05, Edo (edo.ekunwe at gmail.com) wrote: All I am looking for example configuration(s) of how to setup a subscriber as a SIP trunk as mentioned below. I am really trying to handle multiple users behind another IP PBX system with IP authentication [image: image.png] I looked at subscriber preferences but could not find any idea leading to success. Please assist. -- ----- Ekunwe Tel: 601.497.3932 -- br/>Spce-user mailing list < Spce-user at lists.sipwise.com http://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ii_m1nffsez0 Type: application/octet-stream Size: 85741 bytes Desc: not available URL: From edo.ekunwe at gmail.com Mon Sep 30 12:18:04 2024 From: edo.ekunwe at gmail.com (Edo) Date: Mon, 30 Sep 2024 11:18:04 -0500 Subject: [Spce-user] How to setup subscriber as SIP Trunk In-Reply-To: References: Message-ID: Hi, Please could you send me some steps and where to make the configuration? I have tried to configure it under subscriber but the username and DID aliases is giving me the blues. I need to use a wildcard for the incoming numbers cos I have no way of telling what the incoming did will be as they are coming from ALL possible number ranges. Thanks On Mon, Sep 30, 2024 at 9:23?AM Stefano Rogna Manassero di Costigliole < stefanormc at gmail.com> wrote: > Hello Edo, > > I usually register the trunk with user/pwd as usual and it works fine. You > can also authenticate on the IP as described but I never had the need to. > > Hope it helps. > > Ciao > > Stefano > > > > On 30 September 2024 at 13:01:05, Edo (edo.ekunwe at gmail.com) wrote: > > All I am looking for example configuration(s) of how to setup a subscriber > as a SIP trunk as mentioned below. I am really trying to handle multiple > users behind another IP PBX system with IP authentication > [image: image.png] > I looked at subscriber preferences but could not find any idea leading to > success. > > Please assist. > > -- > ----- > Ekunwe > Tel: 601.497.3932 > -- br/>Spce-user mailing list < > Spce-user at lists.sipwise.com > http://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com > > -- ----- Ekunwe Tel: 601.497.3932 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ii_m1nffsez0 Type: application/octet-stream Size: 85741 bytes Desc: not available URL: From edo.ekunwe at gmail.com Mon Sep 30 13:43:27 2024 From: edo.ekunwe at gmail.com (Edo) Date: Mon, 30 Sep 2024 12:43:27 -0500 Subject: [Spce-user] How to setup subscriber as SIP Trunk In-Reply-To: References: Message-ID: Thanks for the advice. I will try that and update the thread. Thanks again On Mon, Sep 30, 2024 at 11:42?AM Walter Klomp wrote: > There is no difference between a subscriber and a sip trunk. > > A sip trunk just has optional multiple numbers and more channels than a > subscriber. > > I think you need to set e164 to ruri for the ddi to be sent to the sip > trunk client. > > Obviously you also need to set the numbers in allowed ddi and the add the > aliases. > > There will be only 1 authentication, which is typically the main sip trunk > number. You can use ip authentication as well. But you have to create a > static registration entry otherwise inbound calls to the sip trunk will not > work. The PBX connected to the sip trunk doesn?t need to authenticate in > this case. > > Note the users will connect to the PBX and NOT Sipwise in this case. > > [image: Signature header] > [image: Signature image] > Walter Klomp > Head of Voice Network > [image: Email] walter at myrepublic.net > Beyond Work : > 11 Lorong 3 Toa Payoh, #04-11/15, Jackson Square, Block B, Singapore 319579 > www.myrepublic.net > * [image: Facebook-f] * * > [image: Instagram] * * > [image: Twitter] * * > [image: Linkedin-in] * > The information in this message is privileged and confidential. If you are > not the intended recipient of this email, please don't read, copy, use, > distribute or tell anyone about it; kindly destroy it and notify the sender > by return email. Please advise immediately if you or your employer does not > consent to email for messages of this kind. Any content that is not > concerned with MyRepublic business reflects the views of the sender only > and not those of MyRepublic. > > > On Mon, 30 Sep 2024 at 19:00, Edo wrote: > >> All I am looking for example configuration(s) of how to setup a >> subscriber as a SIP trunk as mentioned below. I am really trying to handle >> multiple users behind another IP PBX system with IP authentication >> [image: image.png] >> I looked at subscriber preferences but could not find any idea leading to >> success. >> >> Please assist. >> >> >> -- >> ----- >> Ekunwe >> Tel: 601.497.3932 >> -- >> Spce-user mailing list >> Spce-user at lists.sipwise.com >> http://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com >> > > The contents of this email and any attachments are confidential and may > also be privileged. You must not disseminate the contents of this email and > any attachments without permission of the sender. If you have received this > email by mistake, please delete all copies and inform the sender > immediately. You may refer to our company's Privacy Policy here > . -- ----- Ekunwe Tel: 601.497.3932 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 85741 bytes Desc: not available URL: