I used the following Avaya documentation, along with the you tube for provisioning the certs.
https://www.devconnectprogram.com/fileMedia/download/366344a8-4558-4110-a4a3-5bb740ff4664
The SBC is 7.2.2 and the SM/SMGR/CM is all 8.0.
The TLS handshake is between the SM and SBC. I am not using Remote Worker. I believe there might be a cert issue too but I am not sure how to resolve it.
I followed this link to provision the certs - https://www.youtube.com/watch?v=PweEPzNTkvE
I am running 7.2.2.0-11-15522 and it's an EMS +...
The "Remote Access" is not configured but what relationship does it have with the SBC?
- Remote Access Configurations are used by Session Manager to map the SIP Proxy's Public IP Address to a Session Manager private SIP addresses.
Moving SBC from TCP to TLS and all the provisioning in SM is completed, along with the required certificates, but I cannot get a link established Between SM and the SBC. I validated there are no firewall restrictions. The SBC traces show rst after TLS hello. What can I check to resolve this issue?
Currently the carrier gets the invite from our public address, and they are responding with a 401 but they say we need to check the NAT so it is not masking the contact and via headers in the register.
In the registration (contact/via) below it is sending the B1 interface IP instead of the...
The grace period expired before I could activate my new licensing, and now it won't take the new license from the external WEBLM. Is there anything stopping the process because the grace period is over?
I am adding another diverse carrier to my Avaya SBC and I need to know if there are any configurations that would conflict with my primary carrier? The items I think might be impacting are port ranges, Media Interface, Signaling Interface or UDP.
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.