Res_pjsip_transport_management.c: Shutting Down Transport

Home » Asterisk Users » Res_pjsip_transport_management.c: Shutting Down Transport
Asterisk Users 1 Comment

hello,

i met with this interesting situation

[Jan 24 13:48:37] NOTICE[1049] res_pjsip_transport_management.c:
Shutting down transport ‘8’ since no request was received in 32 seconds

[Jan 24 13:48:37] NOTICE[1049] res_pjsip_transport_management.c:
Shutting down transport ‘8’ since no request was received in 32 seconds
[Jan 24 13:48:41] NOTICE[1049] res_pjsip_transport_management.c:
Shutting down transport ” since no request was received in 32 seconds
[Jan 24 13:48:44] NOTICE[1049] res_pjsip_transport_management.c:
Shutting down transport
‘e=”“;expires=60
u▒l^’ since no request was received in 32 seconds
[Jan 24 13:48:44] NOTICE[1049] res_pjsip_transport_management.c:
Shutting down transport ” since no request was received in 32 seconds
[Jan 24 13:48:45] NOTICE[1049] res_pjsip_transport_management.c:
Shutting down transport ” since no request was received in 32 seconds
[Jan 24 13:48:47] NOTICE[1049] res_pjsip_transport_management.c:
Shutting down transport
‘e=”“;expires=60
‘ since no request was received in 32 seconds
[Jan 24 13:48:49] NOTICE[1049] res_pjsip_transport_management.c:
Shutting down transport ” since no request was received in 32 seconds
[Jan 24 13:48:50] NOTICE[1049] res_pjsip_transport_management.c:
Shutting down transport ‘.0
Date: Wed, 24 Jan 2018 12:48:18 GMT
Allow: INVITE, ACK, CAN’ since no request was received in 32 seconds
[Jan 24 13:48:53] NOTICE[1049] res_pjsip_transport_management.c:
Shutting down transport ” since no request was received in 32 seconds
[Jan 24 13:48:53] NOTICE[1049] res_pjsip_transport_management.c:
Shutting down transport ‘ SUBSCRIBE, INFO’ since no request was received in 32 seconds
[Jan 24 13:48:53] NOTICE[1049] res_pjsip_transport_management.c:
Shutting down transport ‘c732305e-f905-489a-a6f4-5164f0809c8a>”;expires=60
Expires: 60
@u▒^’ since no request was received in 32 seconds
[Jan 24 13:49:27] NOTICE[1049] res_pjsip_transport_management.c:
Shutting down transport
‘▒▒<%▒▒*W▒▒▒$@▒▒▒&r{▒▒▒▒▒X_DL▒▒▒1▒▒"▒`$▒zC▒l▒o▒O▒3▒▒c:133 idle_sched_cb: Shutting down transport '="“;expires=60

asterisk went crazy and had to be restarted

topology

asterisk 13.18.2 + pjsip realtime  + mariadb  (mariadb is on different network!) + jssip via wss as client

extconfig.conf

ps_endpoints => odbc,configDb ps_auths => odbc,configDb ps_aors => odbc,configDb ps_domain_aliases => odbc,configDb

sorcery.conf

[res_pjsip] ; Realtime PJSIP configuration wizard endpoint/cache=memory_cache,expire_on_reload=yes,full_backend_cache=yes endpoint=realtime,ps_endpoints auth/cache=memory_cache,expire_on_reload=yes,full_backend_cache=yes auth=realtime,ps_auths aor/cache=memory_cache,expire_on_reload=yes,full_backend_cache=yes aor=realtime,ps_aors domain_alias=realtime,ps_domain_aliases

there was net interruption on ~13:48

do you have any ideas what can be cause of
“res_pjsip_transport_management.c: Shutting down transport” ?

my idea was that Asterisk with cache doesnt need realtime connectivity with mariadb (can survive short internet interruptions)

Marek

—

One thought on - Res_pjsip_transport_management.c: Shutting Down Transport

  • That module does 2 things. First it handles the keepalives if keep_alive_interval is > 0 in the pjsip.conf/global. It also attempts to mitigate DOS attacks if an attacker floods asterisk with TCP (or TLS)
    connections but doesn’t send any actual messages within the time set in pjsip.conf/system/timer_b. When a connection is opened, a timer is started and if there is no recognizable SIP message before the timer expires, you get the “Shutting down transport” message.

    Yep, it was probably that network interruption. The incoming messages were being corrupted and not recognized as real SIP messages so the timer expired and the transports were shut down.