Brekeke Forum - Search : Brekeke PBX, Brekeke SIP Server, Multi-Tenant Hosted PBX

I ended up with a sidecar approach, using fluentd. This appears to not be a Brekeke SIP Server issue and more with how docker/Cloudwatch work.

Thanks for your help.

Hi Harold,

Yes, I can get the PIDs -

$ sudo docker top 4139f011f70a
UID PID PPID C STIME TTY TI ...

Hi Harold,

Yes, you're correct, I see the other java processes. The problem as I see it is that the Brekeke stream is not being outputted to the main process of the container (PID 1 inside the con ...

Hi Harold,

Thanks for the reply. Yes, SIP Session is checked in [Diagnostics]->[Debug Logs]. We're not using registration. Here's what I've discovered -

If I run a ps -ef on the Brekeke S ...

Hi Harold,

Unfortunately that didn't help.

I've got the following in
file.log.plugin=com.brekeke.common.LoggingConsole
file.log.session.plugin=com.brekeke.common.LoggingConsole
sv.enable.con ...

Thank you for the response. I have tried those settings and do see the log data is no longer being written to disk, but I also do not see anything in stdout.

Any thoughts?

Thanks,
Mike

1. Brekeke Product Name and Version:
3.14.7.4, Advanced

2. Java version:
openjdk-11-jdk

3. OS type and the version:
AWS ECS / docker - amzn2.x86_64

4. UA (phone), gateway or other hardware ...

1. Brekeke Product Name and Version:
Brekeke SIP Server, Version 3.4.7.2, Advanced

2. Java version:
1.8.0_92

3. OS type and the version:
Red Hat Enterprise Linux Server release 6.8 (Santiago) ...

I'm also interested in this feature. We receive a SIP 403 from one of our providers if we run our of credit, with the following included:

Reason: Q.850;cause=52;text="OUTGOING_CALL_BARRED&quo ...

James, your solution worked. Thanks a lot for the assistance.

Regards,
Mike

Do you have any reason to use $nat=false"?

James, thanks for the response. Your question got me thinking so I ran a number of tests and it's not $nat=false that we need different from both ca ...

We'd need to set $nat = false for Carrier B.

Thanks,
Mike

1. Brekeke Product Name and Version:
BSS 3.4.7.2 Advanced Edition

2. Java version:
1.7.0_25-b15 64-Bit

3. OS type and the version:
RHEL6 x86_64

4. UA (phone), gateway or other hardware/sof ...

1. Brekeke Product Name and Version:
Version 3.2.4.3 Advanced

2. Java version:
1.6.0_45

3. OS type and the version:
Red Hat Enterprise Linux Server release 5.11 (Tikanga)

4. UA (phone), ga ...

Thanks. I didn't realize the variable accepted multiple codecs.

Regards,
Mike

1. Brekeke Product Name and Version:
3.2.4.3 Advanced

2. Java version:
1.6.0_45-b06

3. OS type and the version:
RHEL 5

4. UA (phone), gateway or other hardware/software involved:

5. You ...

Ahh, indeed it is Very Happy

, on our >3.2.2.3 version hosts. That'll work, thanks!

Thanks JanP.

One more question -

When the concurrent call limit is reached and dial plan rule returns the 503 I don't see any evidence of that in the Brekeke server logs. I can can only see the ...

Hope/James,

Thanks for the help. I was able to accomplish this using two dial plan entries:

1st

Matching Patterns
$request = ^INVITE
$addr = ^172\.16\.2\.
To = sip:(\+)(1203)(.+)
$route. ...

James,

Thanks, but when I use that plan false is never returned as a value, regardless of how many concurrent calls I make through the server, e.g. with 4 concurrent sessions the following is still ...

1. Brekeke Product Name and Version:
3.2.4.3 Advanced

2. Java version:
1.6.0_45-b06

3. OS type and the version:
RHEL 5

4. UA (phone), gateway or other hardware/software involved:

5. Y ...

Much appreciated, thanks!

Thanks, yep, I now see it in the 3.2.2.9 version I have running elsewhere. It might be worthwhile to update the wiki to avoid any further confusion amongst the community.

Thanks,
Mike

1. Brekeke Product Name and Version:
Version 3.1.9.0 Advanced

2. Java version:
1.6.0_45-b06

3. OS type and the version:
RHEL 5

4. UA (phone), gateway or other hardware/software involved:
...

1. Brekeke Product Name and Version:
3.1.9.0 Advanced

2. Java version:
1.6.0_31

3. OS type and the version:
Red Hat Enterprise Linux Server release 5.3 (Tikanga) x86_64

4. UA (phone), gate ...