Yes, the problem persists with the current deploy patterns shown.

1. Brekeke Product Name and Version: SIP Server Advanced, 3.14.7.4 2. Java version: Redhat OpenJDK 11.0.21-1 3. OS type and the version: Windows Server 2019 datacenter 4. UA (phone), gateway or other hardware/software involved: Voicent IVR 5. Your problem: I am receiving an INVITE from carrier via ...

Thanks for your help.

I resolved this by placing another $session = com.myplugin after the redirect on the outbound deploy pattern. Not sure why I had to do 2 of them but the additional hook worked for the outbound leg just fine.

Mark as resolved.

The Dial Plan shown is the Priority 1, the first. Also, I did not add the $continue when I first posted. The full deploy is actually: [Matching Pattern] $request = ^INVITE [Deploy Pattern] $session = com.myplugin $continue = true Later, there is a rule that completes the outbound call with some ...

1. Brekeke Product Name and Version: Brekeke SIP Server, Version 3.13.0.0, Advanced 2. Java version: Redhat JDK 11 3. OS type and the version: Windows Server 2019 4. UA (phone), gateway or other hardware/software involved: Standard IP Phones public IP 5. Your problem: I cannot get the session plugin ...

The public domain, from the internet, as an example is publicdomain.com. This is where stations are located and outside the local network where the BSS is. The firewall will port forward by hostname to the BSS. The privatedomain.com is internal and on the same network as the BSS, not external. It ...

1. Brekeke Product Name and Version: Brekeke Sip Server 3.10.6.5 2. Java version: Redhat OpenJDK 11.0.11-1 3. OS type and the version: Windows Server 2019 Standard 4. UA (phone), gateway or other hardware/software involved: FusionPBX 4.2.2 5. Your problem: I am attempting to use BSS as an SBC front ...