Hi Tata, Yes, the call is being forwarded back to the SBC to the remapped user, but for some reason the call gets passed back to the Brekeke Server. Rule registered=sip:12345678(sip:12345678-12345678-AlIaS-A13693E7C5836E--@1.2.3.4:5060/UDP) & tsbc_inbound_calls 12345678 = registered user and 1.2.3.4 ...

Hi Tata, Yes we can and the UA is registered on registered clients page and on my SIP application. The 12345678 is just the number I'm dialing to(the registered user). First rule: Matching Pattern $request = ^INVITE To = sip:12345678@ Deploy Pattern To = sip:12345678@ Second rule: Matching Pattern ...

1. Brekeke Product Name and Version: Brekeke SIP Server 3.9.1.3/510 2. Java version: java version "1.8.0_201" Java(TM) SE Runtime Environment (build 1.8.0_201-b09) Java HotSpot(TM) 64-Bit Server VM (build 25.201-b09, mixed mode) 3. OS type and the version: 4.9.0-8-amd64 #1 SMP Debian 4.9.144-3 (2019 ...

Hi Tata, Thank you, the call is no longer getting denied. So far we have outbound working perfectly and a registered user can make calls via the SIP proxy. The issue comes in with the incoming calls now. When a call comes into our SBC it then pushes it to the SIP proxy, but what happens now is that ...

1. Brekeke Product Name and Version: Brekeke SIP Server 3.9.1.3/510 2. Java version: java version "1.8.0_201" Java(TM) SE Runtime Environment (build 1.8.0_201-b09) Java HotSpot(TM) 64-Bit Server VM (build 25.201-b09, mixed mode) 3. OS type and the version: 4.9.0-8-amd64 #1 SMP Debian 4.9.144-3 (2019 ...

Hi Jan,

Thank you, that was it!

1. Brekeke Product Name and Version: Brekeke SIP Server 3.9.1.3/510 2. Java version: java version "1.8.0_201" Java(TM) SE Runtime Environment (build 1.8.0_201-b09) Java HotSpot(TM) 64-Bit Server VM (build 25.201-b09, mixed mode) 3. OS type and the version: 4.9.0-8-amd64 #1 SMP Debian 4.9.144-3 (2019 ...