Helps when you set the date/time. Was staring me in the face. I had not configured the date/time source yet, so of course the cert was going to be invalid. Setting the date/time to something current solved the issue for that problem.
I generated it on SMGR (EJBCA) for testing.
Same PKCS12 cert works fine with AAfD and One-X communicator.
Just getting "identity certificate rejected" on hard phone with password in 46xxsettings and also after manually entering password at prompt.
Turned out to be a firmware issue on the phone. Even though the phone was getting the 7.1.9 tar file as shown above it never updated from 7.0.4. I noticed this right before I decided to try a different 7.1 firmware. When I switched to 7.1.8, the application actually updated this time and then...
JimboJimbo: Thanks for the info! After researching this, I will go with a third party SCEP server for mass deploy and I will use the staging process. For testing I am trying to use the "PKCS12 SETTINGS" section and the "SET PKCS12URL" parameter, but the phone (SIP 7.1.9) is not even reaching out...
Thanks for the info Kyle555! I do have Subscriber flows restricted by User Agent. I will have to look at configuring the URI Groups, that is a good idea.
For the DOS protections, are you referring to the Domain Dos profile or under Dos/DDoS? It didn't look like much could be configured under...
Greetings,
Just reading up on Mutual Auth TLS for Remote Workers via an SBC and wanted to see if anyone has a link to a good application note or document they recommend that shows how to implement with SMgr/SBC. I already have TLS implemented with reverse proxies, but would like to take the...
The sentinel driver for the dongle will not work properly (at least in my experience). It will not see the dongle. Has to be Windows XP or Server 2003.
jhengel,
Being the first Avaya SBC I will be installing (normally we just use firewalls..Cisco ASA's etc..)I am just looking at the application notes I posted a link to up above. And in the application notes it shows for remote worker + sip trunk you have to have 3 IP addresses/virtual...
Sounds like you deployed what Avaya refers to as the "one-wire deployment, also referred to as the screened subnet". So you had a firewall in front of your SBC, which means you have to sell the customer a firewall in addition to the SBC if they do not already have one. I guess if you created an...
Application notes for configuring remote worker with a sip trunk. It shows in the first diagram (figure 1) and talks about it through the notes. Just wanted real world feed back on if this is what it actually takes based on install experience or if there was another way around this. I assume it...
All the documentation I see regarding the SBC when used for SIP trunking and Remote Worker shows it requires 3 public IP addresses. Can anyone with experience implementing an SBC with those requirements confirm it has to have 3 public IP addresses? If you put a router/firewall in front of it I...
UMS was working for a customer of ours on 9.0.2.0.860 with Exchange 2010, but the TUI problem (trying to listen to messages after the header by pressing 0) was not. We upgraded the customer to 9.0.3.0.941 to fix that issue and it broke UMS. Anyone else experiencing the same issue?
If Avaya is...
The help file for System -> Lan1/2 -> VoIP has the following under the H323 Remote Extn Enable section
- Currently, only 9600 Series phones are supported as H.323 remote extensions.
I have a customer with a BCM 400 (SW Version 4.0.2.21d) and a BCM 50 (SW version 6.0.2.05.237) linked together via sip trunks over a MPLS. When either location calls by 4 digit dialing the other sites extensions it shows the calling party's info as anonymous. The private network type (under...
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.