Hi team,
I'm working to enhance security for my remote workers services.
I need to change NGINX default message (404), but I don't find the file to change. NGINX on Avaya SBCE directory seems to be located in different locations.
Same thing for IPO, I blocked the access to 46xxsettings.txt...
Hi team,
I'm looking for an information that I cannot find on Avaya documents (installation & configuration doc, offer definition doc, etc).
I need to know, how many entry can I create on the SBCE ? for example, on the SIP Server tab, how many "ADD" can I make for Trunk Server type / call...
I like working on Avaya solutions Ameliorations.
I'll request a GIRP for that fonctionnality.
I requested a GIRP for SBCE license usage in real time with IPO and my request was released on SBCE 8.1.2 (license compliance) :)
have a nice day !
Hi team,
So I maked some configuration that's look fine to block attacks !
- I created one URI-Group (BLOCK) that block all domains.
- I created anotehr URI-Group (ALLOW) that allow only my domain
- I affected the ALLOW URI-Group to my subscriber/server flows
Now attacks are directlly...
I'm deploying the SBCE 8.1.2 this afternoon and I will test LDAP function for MAC address and URI groups to allow/deny subnets and domains.
I'll keep you in touch about the result.
Thank you all for your ideas.
Thank you Tek-Tips for this community !
Another way to secure Avaya systems, maybe that Avaya find a way to crypt the 46xxsettinps.txt & other settings files readable from Internet.
These files contains importants informations about phone system: SIP protocols/ports etc...
I use many type of phone:
- IX Workplace on iOS
- IX Workplace on Android
- IX Workplace on Windows
- J100 phones
I will change login codes to make it complex if no other solution on SBCE for that..
Hi team,
I have an Avaya SBCE (release 8.0.1) installed with an Avaya IPO (reelase 11.0.4).
I have a remote worker service running on SBCE.
Since yesterday, I received many fraudulent REGISTER and I don't know how to block that correctly.
I have already activaed DDoS options but that doesn't...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.