retronetworking
/
yate
12
0
Fork 2
Code Issues Pull Requests Projects Releases Wiki Activity

zapcard: use DAHDI_POLICY_WHEN_FULL for B-channel buffers #4

Merged
laforge merged 2 commits from Manawyrm/yate:manawyrm-zapcard-buffer-policy into master 2023-09-07 11:40:14 +00:00
Conversation 1 Commits 2 Files Changed 1 +20 -3
Manawyrm commented 2023-09-06 23:49:56 +00:00
Owner
Copy Link

Latency impact on the B channels needs to be investigated. The Argus tester can use a loopback/echo test to measure ping/end-to-end latency. I think I'll build such a setup and take some measurements in the different modes.

For good measure, I also set the
priority=highest
in zapcard.conf (affects the data service thread priority), but that didn't really seem to have any effect (still probably the correct setting).

Yate is able to survive a 30min BERT with these changes:

Latency impact on the B channels needs to be investigated. The Argus tester can use a loopback/echo test to measure ping/end-to-end latency. I think I'll build such a setup and take some measurements in the different modes. For good measure, I also set the `priority=highest` in zapcard.conf (affects the data service thread priority), but that didn't really seem to have any effect (still probably the correct setting). Yate is able to survive a 30min BERT with these changes: ![](https://screenshot.tbspace.de/tnufegcwmjr.jpg)
Manawyrm added 1 commit 2023-09-06 23:49:56 +00:00
Manawyrm force-pushed manawyrm-zapcard-buffer-policy from 154f579630 to fa6b4ad14a 2023-09-07 10:29:16 +00:00 Compare
Manawyrm changed title from [Draft] zapcard: use DAHDI_POLICY_WHEN_FULL for B-channel buffers to zapcard: use DAHDI_POLICY_WHEN_FULL for B-channel buffers 2023-09-07 10:29:45 +00:00
Manawyrm commented 2023-09-07 10:32:55 +00:00
Author
Owner
Copy Link

I've built an echo/test B-channel loopback service now (using the external/playrec mechanism) and have tested the latency using the Argus.

DAHDI_POLICY_IMMEDIATE - 99.8ms
DAHDI_POLICY_HALF_FULL - 103.2ms
DAHDI_POLICY_WHEN_FULL - 106.6ms

Getting 6-7ms of additional latency for no more bit errors seems like a very worthwhile cause.

I've also updated the PR slighly.

I've built an echo/test B-channel loopback service now (using the external/playrec mechanism) and have tested the latency using the Argus. ``` DAHDI_POLICY_IMMEDIATE - 99.8ms DAHDI_POLICY_HALF_FULL - 103.2ms DAHDI_POLICY_WHEN_FULL - 106.6ms ``` Getting 6-7ms of additional latency for no more bit errors seems like a very worthwhile cause. I've also updated the PR slighly.
Manawyrm added 1 commit 2023-09-07 11:02:23 +00:00
laforge merged commit cebbaa38e1 into master 2023-09-07 11:40:14 +00:00
laforge deleted branch manawyrm-zapcard-buffer-policy 2023-09-07 11:40:14 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: retronetworking/yate#4
No description provided.
Delete Branch "Manawyrm/yate:manawyrm-zapcard-buffer-policy"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?