Recent content by randyrtx

in your gateway settings is profile = external? from the capture above it looks as though it is internal =sofia/internal/FreeSWITCH@2.2.2.2

so on your external profile you will see which ACL is uses by looking at the sip profile for apply-inbound-acl. Mine is set to domains so I would use the domains ACL to set the 2.2.2.2/32 and type is Allow

if your gateway is set the the internal profile it will require authentication on the SIP invite. If you use the external you can get it to authenticate it by IP.

got this issue resolved. rookie mistake. I was reloading the xml when I should have stopped / started the gateway to make my changes take effect.

So there was a DNS issue and with the CERT it was not passing the mustard so failed. that has been corrected. What I really need to know is how to only encrypt the B leg of an outbound call. I have no issue with inbound calls using TLS / SRTP 5081 is the port my box listening on - my...

So I am testing TLS / SRTP with a carrier but can't seem to get outbound calling to work. Inbound TLS calls work great. Prior to switching to TLS the gateway was working with SIP UDP using the external profile. Once I switched to TLS, I updated the port of the gateway to reflect the TLS port of...