Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

video struck #560

Open
prathibhacdac opened this issue Oct 10, 2024 · 11 comments
Open

video struck #560

prathibhacdac opened this issue Oct 10, 2024 · 11 comments

Comments

@prathibhacdac
Copy link

prathibhacdac commented Oct 10, 2024 •
edited
Loading

video freezing after 50 seconds but audio continues. How to resolve this?
@InnovateAsterisk
Copy link
Owner

What does the Asterisk CLI show at this point?

@prathibhacdac
Copy link
Author

ERROR[2022]: chan_sip.c:4354 __sip_reliable_xmit: Serious Network Trouble; __sip_xmit returns error for pkt data
== WebSocket connection from '10.23.0.218:55832' closed
[Oct 10 16:04:21] ERROR[2022]: chan_sip.c:4354 __sip_reliable_xmit: Serious Network Trouble; __sip_xmit returns error for pkt data
[Oct 10 16:04:35] ERROR[2022]: chan_sip.c:4354 __sip_reliable_xmit: Serious Network Trouble; __sip_xmit returns error for pkt data
[Oct 10 16:04:47] ERROR[2022]: iostream.c:552 ast_iostream_close: SSL_shutdown() failed: error:00000005:lib(0)::reason(5), Underlying BIO error: Broken pipe

@prathibhacdac
Copy link
Author

WARNING[106701][C-00000010]: channel.c:5765 set_format: Unable to find a codec translation path: (slin) -> (vp8|h264|opus)
[Oct 10 16:08:13] WARNING[106701][C-00000010]: indications.c:140 playtones_alloc: Unable to set 'SIP/9962-00000014' to signed linear format (write)
[Oct 10 16:08:13] WARNING[106701][C-00000010]: channel.c:4682 indicate_data_internal: Unable to handle indication 3 for 'SIP/9962-00000014'
-- SIP/9962-00000014 requested media update control 26, passing it to SIP/211003-00000015
> 0x7f6a540e94d0 -- Strict RTP switching to RTP target address 10.23.0.218:13685 as source
-- SIP/9962-00000014 requested media update control 26, passing it to SIP/211003-00000015
> 0x7f6a541c1750 -- Strict RTP switching to RTP target address 10.23.0.218:16756 as source
> 0x7f6a881047e0 -- Strict RTP learning after remote address set to: 10.212.134.201:60548
> 0x7f6a88036c30 -- Strict RTP learning after remote address set to: 10.212.134.201:60545
-- SIP/211003-00000015 answered SIP/9962-00000014
-- Channel SIP/211003-00000015 joined 'simple_bridge' basic-bridge
-- Channel SIP/9962-00000014 joined 'simple_bridge' basic-bridge
> 0x7f6a881047e0 -- Strict RTP learning after ICE completion
> 0x7f6a88036c30 -- Strict RTP learning after ICE completion
> 0x7f6a881047e0 -- Strict RTP learning after remote address set to: 10.212.134.201:60548
> 0x7f6a88036c30 -- Strict RTP learning after remote address set to: 10.212.134.201:60545
> 0x7f6a88036c30 -- Strict RTP switching to RTP target address 10.212.134.201:60545 as source
> 0x7f6a881047e0 -- Strict RTP switching to RTP target address 10.212.134.201:60548 as source
> 0x7f6a541c1750 -- Strict RTP learning complete - Locking on source address 10.23.0.218:16756
> 0x7f6a540e94d0 -- Strict RTP learning complete - Locking on source address 10.23.0.218:13685
> 0x7f6a88036c30 -- Strict RTP learning complete - Locking on source address 10.212.134.201:60545
> 0x7f6a881047e0 -- Strict RTP learning complete - Locking on source address 10.212.134.201:60548

@InnovateAsterisk
Copy link
Owner

At what point in the above log does the vide drop? Can you also capture the rtp? (rtp set debug on)

@prathibhacdac
Copy link
Author

Got RTP packet from 10.212.134.203:54696 (type 100, seq 020883, ts 277792768, len 001116)
Got RTP packet from 10.212.134.203:54696 (type 100, seq 020884, ts 277792768, len 001117)
Got RTP packet from 10.212.134.203:54693 (type 107, seq 033259, ts 3623214476, len 000070)
Sent RTP packet to 10.23.0.218:12858 (via ICE) (type 96, seq 031699, ts 277792768, len 001116)
Sent RTP packet to 10.23.0.218:12858 (via ICE) (type 96, seq 031700, ts 277792768, len 001117)
Sent RTP packet to 10.23.0.218:16395 (via ICE) (type 111, seq 024313, ts 3623214432, len 000070)
Got RTP packet from 10.23.0.218:16395 (type 111, seq 028745, ts 592382930, len 000047)
Sent RTP packet to 10.212.134.203:54693 (via ICE) (type 107, seq 032858, ts 592382928, len 000047)
Got RTP packet from 10.23.0.218:16395 (type 111, seq 028746, ts 592383890, len 000047)
Sent RTP packet to 10.212.134.203:54693 (via ICE) (type 107, seq 032859, ts 592383888, len 000047)
Got RTP packet from 10.23.0.218:12858 (type 96, seq 033418, ts 3769200713, len 001072)
Got RTP packet from 10.23.0.218:12858 (type 96, seq 033419, ts 3769200713, len 001073)
Sent RTP packet to 10.212.134.203:54696 (via ICE) (type 100, seq 032110, ts 3769200713, len 001072)
Sent RTP packet to 10.212.134.203:54696 (via ICE) (type 100, seq 032111, ts 3769200713, len 001073)
Got RTP packet from 10.212.134.203:54693 (type 107, seq 033260, ts 3623215436, len 000082)
Sent RTP packet to 10.23.0.218:16395 (via ICE) (type 111, seq 024314, ts 3623215392, len 000082)
Got RTP packet from 10.23.0.218:16395 (type 111, seq 028747, ts 592384850, len 000048)
Sent RTP packet to 10.212.134.203:54693 (via ICE) (type 107, seq 032860, ts 592384848, len 000048)
Got RTP packet from 10.212.134.203:54696 (type 100, seq 020885, ts 277795648, len 001124)
Got RTP packet from 10.212.134.203:54696 (type 100, seq 020886, ts 277795648, len 001124)
Got RTP packet from 10.212.134.203:54696 (type 100, seq 020887, ts 277795648, len 001124)
Got RTP packet from 10.212.134.203:54696 (type 100, seq 020888, ts 277795648, len 001124)
Got RTP packet from 10.212.134.203:54696 (type 100, seq 020889, ts 277795648, len 001124)
Sent RTP packet to 10.23.0.218:12858 (via ICE) (type 96, seq 031701, ts 277795648, len 001124)
Sent RTP packet to 10.23.0.218:12858 (via ICE) (type 96, seq 031702, ts 277795648, len 001124)
Sent RTP packet to 10.23.0.218:12858 (via ICE) (type 96, seq 031703, ts 277795648, len 001124)
Sent RTP packet to 10.23.0.218:12858 (via ICE) (type 96, seq 031704, ts 277795648, len 001124)
Sent RTP packet to 10.23.0.218:12858 (via ICE) (type 96, seq 031705, ts 277795648, len 001124)
Got RTP packet from 10.212.134.203:54696 (type 100, seq 020890, ts 277795648, len 001124)
Got RTP packet from 10.212.134.203:54696 (type 100, seq 020891, ts 277795648, len 001125)
Sent RTP packet to 10.23.0.218:12858 (via ICE) (type 96, seq 031706, ts 277795648, len 001124)
Sent RTP packet to 10.23.0.218:12858 (via ICE) (type 96, seq 031707, ts 277795648, len 001125)
Got RTP packet from 10.212.134.203:54693 (type 107, seq 033261, ts 3623216396, len 000078)
Sent RTP packet to 10.23.0.218:16395 (via ICE) (type 111, seq 024315, ts 3623216352, len 000078)
Got RTP packet from 10.23.0.218:16395 (type 111, seq 028748, ts 592385810, len 000051)
Sent RTP packet to 10.212.134.203:54693 (via ICE) (type 107, seq 032861, ts 592385808, len 000051)
Got RTP packet from 10.212.134.203:54693 (type 107, seq 033262, ts 3623217356, len 000077)
Sent RTP packet to 10.23.0.218:16395 (via ICE) (type 111, seq 024316, ts 3623217312, len 000077)
Got RTP packet from 10.23.0.218:16395 (type 111, seq 028749, ts 592386770, len 000051)
Sent RTP packet to 10.212.134.203:54693 (via ICE) (type 107, seq 032862, ts 592386768, len 000051)
Got RTP packet from 10.212.134.203:54696 (type 100, seq 020892, ts 277798618, len 001141)
Got RTP packet from 10.212.134.203:54696 (type 100, seq 020893, ts 277798618, len 001141)
Got RTP packet from 10.212.134.203:54696 (type 100, seq 020894, ts 277798618, len 001141)
Sent RTP packet to 10.23.0.218:12858 (via ICE) (type 96, seq 031708, ts 277798618, len 001141)
Sent RTP packet to 10.23.0.218:12858 (via ICE) (type 96, seq 031709, ts 277798618, len 001141)
Sent RTP packet to 10.23.0.218:12858 (via ICE) (type 96, seq 031710, ts 277798618, len 001141)
Got RTP packet from 10.212.134.203:54696 (type 100, seq 020895, ts 277798618, len 001141)
Sent RTP packet to 10.23.0.218:12858 (via ICE) (type 96, seq 031711, ts 277798618, len 001141)
Got RTP packet from 10.212.134.203:54696 (type 100, seq 020896, ts 277798618, len 001141)
Got RTP packet from 10.212.134.203:54696 (type 100, seq 020897, ts 277798618, len 001141)
Sent RTP packet to 10.23.0.218:12858 (via ICE) (type 96, seq 031712, ts 277798618, len 001141)
Sent RTP packet to 10.23.0.218:12858 (via ICE) (type 96, seq 031713, ts 277798618, len 001141)
Got RTP packet from 10.212.134.203:54696 (type 100, seq 020898, ts 277798618, len 001141)
Sent RTP packet to 10.23.0.218:12858 (via ICE) (type 96, seq 031714, ts 277798618, len 001141)
Got RTP packet from 10.212.134.203:54696 (type 100, seq 020899, ts 277798618, len 001141)
Got RTP packet from 10.212.134.203:54696 (type 100, seq 020900, ts 277798618, len 001141)
Sent RTP packet to 10.23.0.218:12858 (via ICE) (type 96, seq 031715, ts 277798618, len 001141)
Got RTP packet from 10.212.134.203:54696 (type 100, seq 020901, ts 277798618, len 001141)
Sent RTP packet to 10.23.0.218:12858 (via ICE) (type 96, seq 031716, ts 277798618, len 001141)
Sent RTP packet to 10.23.0.218:12858 (via ICE) (type 96, seq 031717, ts 277798618, len 001141)
Got RTP packet from 10.212.134.203:54696 (type 100, seq 020902, ts 277798618, len 001141)

@prathibhacdac
Copy link
Author

At what point in the above log does the vide drop? Can you also capture the rtp? (rtp set debug on)

It is cropping at 45 secs. But there is no log in the CLI.

@prathibhacdac
Copy link
Author

Do we need to mention the stunaddr in rtp.conf?

@InnovateAsterisk
Copy link
Owner

InnovateAsterisk commented Oct 14, 2024 •
edited
Loading

Within a few seconds i get this:

[Oct 14 09:41:22] WARNING[10171][C-00000024]: res_srtp.c:508 ast_srtp_protect: SRTP protect: replay check failed (index too old)
[Oct 14 09:41:22] WARNING[10171][C-00000024]: res_srtp.c:508 ast_srtp_protect: SRTP protect: replay check failed (index too old)
[Oct 14 09:41:22] WARNING[10171][C-00000024]: res_srtp.c:508 ast_srtp_protect: SRTP protect: replay check failed (index too old)
[Oct 14 09:41:22] WARNING[10171][C-00000024]: res_srtp.c:508 ast_srtp_protect: SRTP protect: replay check failed (index too old)
[Oct 14 09:41:23] WARNING[10171][C-00000024]: res_srtp.c:508 ast_srtp_protect: SRTP protect: replay check failed (index too old)
[Oct 14 09:41:23] WARNING[10171][C-00000024]: res_srtp.c:508 ast_srtp_protect: SRTP protect: replay check failed (index too old)

But it happens quick, not after 30/40 seconds.

@prathibhacdac
Copy link
Author

pls share the o/p of sip show settings

@InnovateAsterisk
Copy link
Owner 

CLI> pjsip show settings

Global Settings:

 ParameterName                              : ParameterValue
 ======================================================================
 allow_sending_180_after_183                : false
 contact_expiration_check_interval          : 30
 debug                                      : no
 default_from_user                          : asterisk
 default_outbound_endpoint                  : default_outbound_endpoint
 default_realm                              : siperb.com
 default_voicemail_extension                : 
 disable_multi_domain                       : false
 endpoint_identifier_order                  : ip,username,anonymous
 ignore_uri_user_options                    : false
 keep_alive_interval                        : 300
 max_forwards                               : 70
 max_initial_qualify_time                   : 0
 mwi_disable_initial_unsolicited            : false
 mwi_tps_queue_high                         : 500
 mwi_tps_queue_low                          : -1
 norefersub                                 : yes
 regcontext                                 : 
 send_contact_status_on_update_registration : no
 taskprocessor_overload_trigger             : global
 unidentified_request_count                 : 5
 unidentified_request_period                : 5
 unidentified_request_prune_interval        : 30
 use_callerid_contact                       : no
 user_agent                                 : SIPERB

System Settings:

 ParameterName               : ParameterValue
 ============================================
 accept_multiple_sdp_answers : false
 compact_headers             : false
 disable_rport               : false
 disable_tcp_switch          : true
 follow_early_media_fork     : true
 threadpool_auto_increment   : 5
 threadpool_idle_timeout     : 60
 threadpool_initial_size     : 0
 threadpool_max_size         : 50
 timer_b                     : 32000
 timer_t1                    : 500

@InnovateAsterisk
Copy link
Owner

Can you do a SpeedTest between your current location, and the location of the server. Make sure you are using the same sort of path that the packets would take. On speedtest.net you will need to change the server to the same server location. If you are hosting the server locally, and have clients connect from out-side, then you would have to find some sort of speed test that runs the same link.

I'm finding that Asterisk is not that good at recovering from missing or corrupt packets, when compared to a RTPEngine configuration, where the two parties are directly connections via peer-to-peer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@prathibhacdac @InnovateAsterisk