Search results for query: *

kyle555/t2ture, do you any other comments/directions on my issue?

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 +...

kyle555, I am not using proxies for the SBC, but are you saying this is required for TLS to work?

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.

Understood, and I have all those setting correct, with TLS and the appropriate certs.

None of the interfaces changed in Server Flows from TCP to TLS, can you give me more details?

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?

That the piece I was missing...thanks.

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...

I am on release 6.3.

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.

Can you provide me your setup steps?

RedSky requires I send <sip:911@XX.XXX.8.113:5060> in the "To" header of the SIP invite.

I know RedSky is an Avaya devconnect partner, but I haven't been able to find documentation or sigma script that will modify the invite "To" line with <sip:911@XX.XXX.8.113:5060>.Can anyone point me in the right direction or provided documentation on how to make the changes in ASBCE

Come to find out the issue was because we had “SIP packet inspect” turned on in the firewall. This was causing the ACK Request URI to return with a malformed ACK.

It is getting the ACK from the carrier, and as you indicated, it is not returning it. It is an Avaya SBCE.

We are not using subdomains anywhere. I pulled another trace in SM, and all indications are the SBC is not sending and ACK back to CM. http://files.engineering.com/getfile.aspx?folder=f001db42-0b76-42d1-98d0-1090df4af72d&file=12-27-2016_9-47-43_AM.pdf

Thanks for the information Kyle. I'll start looking at the configs