[Home]

Summary:ASTERISK-28596: 34/5000 Problem with the sip in asterisk 16
Reporter:David (Davids410)Labels:
Date Opened:2019-10-23 04:24:44Date Closed:2019-10-23 05:28:08
Priority:MajorRegression?
Status:Closed/CompleteComponents:. I did not set the category correctly.
Versions:16.6.0 Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:I have a problem, I am trying to use the sip in asterisk 16, and when I call it hangs up after 6 seconds.
I enclose what I get when I analyze the results:

[2019-10-23 11:08:49] WARNING[8752]: chan_sip.c:4119 retrans_pkt: Retransmission timeout reached on transmission nwzyJiDzSxozgsxxJF9tVw.. for seqno 2 (Critical Response) -- See https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions
Packet timed out after 6400ms with no response
[2019-10-23 11:08:49] WARNING[8752]: chan_sip.c:4143 retrans_pkt: Hanging up call nwzyJiDzSxozgsxxJF9tVw.. - no reply to our critical packet (see https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions).
   -- Channel SIP/116-david-00000035 left 'native_rtp' basic-bridge <498ba006-0972-4736-b07d-f4545b05fc15>
 == Spawn extension (davidcontext, 117, 1) exited non-zero on 'SIP/116-david-00000035'
   -- Channel SIP/117-david-00000036 left 'native_rtp' basic-bridge <498ba006-0972-4736-b07d-f4545b05fc15>
 == Extension Changed 116[hints-david] new state Idle for Notify User 115-david
 == Extension Changed 117[hints-david] new state Idle for Notify User 115-david
 == Extension Changed 117[hints-david] new state Idle for Notify User 115-david
[2019-10-23 11:08:50] WARNING[29528]: res_pjsip_pubsub.c:3305 pubsub_on_rx_publish_request: No registered publish handler for event presence
[2019-10-23 11:08:50] WARNING[29682]: res_pjsip_pubsub.c:776 subscription_get_handler_from_rdata: No registered subscribe handler for event presence.winfo
Comments:By: Asterisk Team (asteriskteam) 2019-10-23 04:24:46.047-0500

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.
By: Joshua C. Colp (jcolp) 2019-10-23 05:27:56.561-0500

We appreciate the difficulties you are facing, however this does not appear to be a bug report and your request or comments would be better served in a different forum.

The Asterisk community provides support over IRC, mailing lists, and forums as described at http://asterisk.org/community. The Asterisk issue tracker is used specifically to track issues concerning bugs and documentation errors.

Please see the Asterisk Issue Guidelines [1] for instruction on the intended use of the Asterisk issue tracker.

Thanks!

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines