Lost frame(s) from slin to alaw


Using Freepbx 15.0.29 / Asterisk 16.21.1

Checking logs into my Freepbx, I can see that there are lost frames

    -- Channel PJSIP/1009-00000001 joined 'simple_bridge' basic-bridge <9717e7e6-f720-46f1-909e-cc9f9cdef9ec>
    -- Channel Local/[email protected];2 joined 'simple_bridge' basic-bridge <9717e7e6-f720-46f1-909e-cc9f9cdef9ec>
    -- Local/[email protected];1 answered PJSIP/OVH-SIP-00000000
    -- <Local/[email protected];1> Playing 'custom/Aslog.slin' (language 'fr')
       > 0xaac666e0 -- Strict RTP switching to RTP target address as source
[2023-03-03 09:18:31] NOTICE[4496][C-00000001]: translate.c:603 ast_translate: 4640 lost frame(s) 4641/0 ([email protected])->([email protected])
    -- Stopped music on hold on PJSIP/OVH-SIP-00000000
    -- Channel Local/[email protected];1 joined 'simple_bridge' basic-bridge <4532078c-1a34-42ce-aa99-f15119fa39c4>
    -- Channel PJSIP/OVH-SIP-00000000 joined 'simple_bridge' basic-bridge <4532078c-1a34-42ce-aa99-f15119fa39c4>
       > 0xaac666e0 -- Strict RTP learning complete - Locking on source address

The line is

[2023-03-03 09:18:31] NOTICE[4496][C-00000001]: translate.c:603 ast_translate: 4640 lost frame(s) 4641/0 ([email protected])->([email protected])

If I check the stats…

raspbx4*CLI> pjsip show channelstats

                                             ...........Receive......... .........Transmit..........
 BridgeId ChannelId ........ UpTime.. Codec.   Count    Lost Pct  Jitter   Count    Lost Pct  Jitter RTT....

 4532078c OVH-SIP-00000000   00:00:21 alaw     1029       0    0   0.000   1031       0    0   0.000   0.000
 9717e7e6 1009-00000001      00:00:20 alaw      783       0    0   0.000    793       0    0   0.000   0.012

In this particular case, the phone link was good.

Why are there lost frames ?

Thanks in advance.

Furthermore, this message seems to be associated with chan_dongle, which is third party code, and, to the best of my knowledge, no longer supported.

Asterisk 16 no longer receives bug fixes.

Hum… I tested this in the past to play with 2G voice calls.

But strange that this comes here while I do not use it anymore.

Anyway, I’m building new system based on old XIVO hardware where I installed last Freepbx version.
Will not have chan_dongle anymore.

Many thanks for your help.


It is possible that it isn’t just chan_dongle, although that is the context in which others have reported it. I think it has to be RPi though, given that the message isn’t in the official code.

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.