search for: 000960

...8:9956 (type 00, seq 037721, ts 000640, len 000160) Got RTP packet from 192.168.1.102:8000 (type 00, seq 062222, ts 1373137124, len 000160) Sent RTP packet to 192.168.1.102:8000 (type 00, seq 037722, ts 000800, len 000160) Sent RTP packet to 192.168.1.102:8000 (type 00, seq 037723, ts 000960, len 000160) Is it the prolem? First it sends to the public address of the the router, then it sends to the virtual IP. Is this the problem that causing my to hear just one "beat" sound and then no audio? Problem 2: The problem is isolated from Problem 1, cuz I run the SIP client on...

...n 000160) [2020-09-19 23:42:22] VERBOSE[15153][C-00021a1f] res_rtp_asterisk.c: Sent RTP packet to 41.11.11.11:13918 (type 8, seq 020644, ts 000800, len 000160) [2020-09-19 23:42:22] VERBOSE[15153][C-00021a1f] res_rtp_asterisk.c: Sent RTP packet to 41.11.11.11:13918 (type 8, seq 020645, ts 000960, len 000160) <snip> [2020-09-19 23:42:29] VERBOSE[15153][C-00021a1f] res_rtp_asterisk.c: Sent RTP packet to 41.11.11.11:13918 (type 8, seq 020999, ts 250248, len 000160) [2020-09-19 23:42:29] VERBOSE[15153][C-00021a1f] res_rtp_asterisk.c: Sent RTP packet to 41.11.11.11:13918 (type 8...

...n 000160) [2020-09-19 23:42:22] VERBOSE[15153][C-00021a1f] res_rtp_asterisk.c: Sent RTP packet to 41.11.11.11:13918 (type 8, seq 020644, ts 000800, len 000160) [2020-09-19 23:42:22] VERBOSE[15153][C-00021a1f] res_rtp_asterisk.c: Sent RTP packet to 41.11.11.11:13918 (type 8, seq 020645, ts 000960, len 000160) Regards David Herselman -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20200925/e30dc007/attachment.html>

...n 000160) [2020-09-19 23:42:22] VERBOSE[15153][C-00021a1f] res_rtp_asterisk.c: Sent RTP packet to 41.11.11.11:13918 (type 8, seq 020644, ts 000800, len 000160) [2020-09-19 23:42:22] VERBOSE[15153][C-00021a1f] res_rtp_asterisk.c: Sent RTP packet to 41.11.11.11:13918 (type 8, seq 020645, ts 000960, len 000160) Regards David Herselman From: asterisk-users <asterisk-users-bounces at lists.digium.com<mailto:asterisk-users-bounces at lists.digium.com>> On Behalf Of David Herselman Sent: Wednesday, 23 September 2020 4:17 PM To: asterisk-users at lists.digium.com<mailto:asterisk...

Hi, We have a scenario where inbound calls from an upstream provider (chan_sip) sent downstream (chan_iax2) negotiates only g729 yet RTP media contains g711. Both the upstream and downstream trunks are limited to only offering g729 whilst the initial invite from our upstream provider offers both g711 and g729. Asterisk presumably simply forwards the media from iax2 trunk encapsulation to sip

Hi, One of my shared volumes crashed the other day on a RH-7.2, 2.4.9-31 system. These are the first errors in the log: kernel: EXT3-fs error (device ide0(3,9)): ext3_readdir: bad entry in directory #2424833: rec_len is smaller than minimal - offset=0, inode=2553887680, rec_len=0, name_len=0 kernel: EXT3-fs error (device ide0(3,9)): ext3_readdir: bad entry in directory #2424833: rec_len is