[Spce-user] Allow inbound peering without defining as outbound server

Wed May 18 09:28:29 EDT 2022

Yes!
create different peering groups and add the servers (peers) there and then with outbound rules and inbound rules you can create different behaviors for all the peering groups.

Or do you mean different IP addresses of your SPCE server? If this is the case you have to add additional network interfaces and give them the right roles in the network.yml to listen for SIP packages.

Von: Roman Dissauer <roman.dissauer at rdi.at> 
Gesendet: Mittwoch, 18. Mai 2022 15:05
An: Leighton Brennan <leightonbrennan at gmail.com>
Cc: spce-user at lists.sipwise.com
Betreff: Re: [Spce-user] Allow inbound peering without defining as outbound server

I understand, but is their either a way to:

allow inbound traffic for several host addresses (inbound only peers)

or

disable a single peer host to not sending any calls to it

Thx

Roman

Von: Leighton Brennan <leightonbrennan at gmail.com <mailto:leightonbrennan at gmail.com> >
Datum: Mittwoch, 18. Mai 2022 um 14:57
An: Roman Dissauer <roman.dissauer at rdi.at <mailto:roman.dissauer at rdi.at> >
Cc: Walter Klomp <walter at myrepublic.net <mailto:walter at myrepublic.net> >, spce-user at lists.sipwise.com <spce-user at lists.sipwise.com <mailto:spce-user at lists.sipwise.com> >
Betreff: Re: [Spce-user] Allow inbound peering without defining as outbound server

You need to have the IP added as a peer address in order to accept the invites as otherwise anybody could send SIP invites to your customers and you would have no way to stop them. 

Best Regards

Leighton Brennan

On 18 May 2022, at 13:47, Roman Dissauer <roman.dissauer at rdi.at <mailto:roman.dissauer at rdi.at> > wrote:

Hi, this is intended behavior. The peer has separate servers for inbound and outbound traffic.

Thx!

Roman

  _____  

Von: Walter Klomp <walter at myrepublic.net <mailto:walter at myrepublic.net> >
Gesendet: Tuesday, May 17, 2022 11:33:40 AM
An: Roman Dissauer <roman.dissauer at rdi.at <mailto:roman.dissauer at rdi.at> >
Cc: spce-user at lists.sipwise.com <mailto:spce-user at lists.sipwise.com>  <spce-user at lists.sipwise.com <mailto:spce-user at lists.sipwise.com> >
Betreff: Re: [Spce-user] Allow inbound peering without defining as outbound server 

If you don’t create outbound peering rule then it would not send calls there ever. 

On Tue, 17 May 2022 at 16:07, Roman Dissauer < <mailto:roman.dissauer at rdi.at> roman.dissauer at rdi.at> wrote:

Hi,

is there a way to allow traffic from an inbound peering server without defining the same IP as outbound peering server in global peerings?

Thx!

Roman

-- 
Spce-user mailing list
 <mailto:Spce-user at lists.sipwise.com> Spce-user at lists.sipwise.com
 <http://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com> http://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com

-- 

  <https://scribe-mail.myrepublic.net/s2/e7labgpn.gif> 

 <https://scribe-mail.myrepublic.net/s2/46qarekj> 

Walter Klomp 

Head of Voice Network 

  <https://scribe-mail.myrepublic.net/s2/0ukrxotx.png> 

 <tel:+6568161120> +6568161120

  <https://scribe-mail.myrepublic.net/s2/nhmt84oe.png> 

 <mailto:walter at myrepublic.net> walter at myrepublic.net

Beyond Work: VR Sim Racing, F1, Travel

11 Lorong 3 Toa Payoh, #04-11/15, Jackson Square, Block B, Singapore 319579 

 <https://scribe-mail.myrepublic.net/s2/t1t0okpn> www.myrepublic.net

 <https://scribe-mail.myrepublic.net/s2/fk13nj3k> 

 <https://scribe-mail.myrepublic.net/s2/z96g2lp1> 

 <https://scribe-mail.myrepublic.net/s2/y3q7szjh> 

 <https://scribe-mail.myrepublic.net/s2/njigpzvx> 

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. 

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 <https://myrepublic.net/sg/legal/terms-of-use-policies/privacy-policy/> .

-- 
Spce-user mailing list
Spce-user at lists.sipwise.com <mailto: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: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20220518/06407348/attachment-0002.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5022 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20220518/06407348/attachment-0002.p7s>