| Summary: | ASTERISK-28367: Servname not supported for ai_socktype / Could not resolve socket address | ||
| Reporter: | Raul Chiarella (Horseless) | Labels: | |
| Date Opened: | 2019-04-01 15:49:15 | Date Closed: | 2019-04-02 05:14:40 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | Channels/chan_sip/General |
| Versions: | 13.24.1 | Frequency of Occurrence | Occasional |
| Related Issues: | |||
| Environment: | Asterisk 13.24.1 CentOS 7 | Attachments: | |
| Description: | Where X.X.X.X is my IP Address,
netsock2.c:305 ast_sockaddr_resolve: getaddrinfo("X.X.X.X", "5060branch=z9hG4bK-d87543-fd7c5e7dbc5b1b52-1--d87543-", ...): Servname not supported for ai_socktype chan_sip.c:19021 check_via: Could not resolve socket address for 'X.X.X.X:5060branch=z9hG4bK-d87543-fd7c5e7dbc5b1b52-1--d87543-' Sending to X.X.X.X:5060 (NAT) This happens because the Source ( MicroSIP / XLite / EyeBeam and other softphones - Except for Zoiper 5, it did'nt happened with Zoiper 5 ) did'nt include the ; after the IP:PORT Log ( Zoiper 5 and MicroSIP / EyeBeam compared ): MicroSIP ( Error ): Via: SIP/2.0/UDP X.X.X.X:5060rport;branch=z9hG4bKPj3ee85d5343ed4f32977e90636290d564 EyeBeam ( Error ): Via: SIP/2.0/UDP X.X.X.X:5060branch=z9hG4bK-d87543-e70b013bc501015a-1--d87543-;rport Zoiper 5 ( OK ) : Via: SIP/2.0/UDP X.X.X.X:38353;branch=z9hG4bK-524287-1---0e6b7691ba41fb4a;rport Also MicroSIP on another network ( OK ): Via: SIP/2.0/UDP X.X.X.X:5060;branch=z9hG4bKPjc28765bbf301467b8048ee338272af06;rport | ||
| Comments: | By: Asterisk Team (asteriskteam) 2019-04-01 15:49:16.106-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-04-02 05:14:40.397-0500 This is not a bug in Asterisk. Something in the path appears to be corrupting the SIP signaling (potentially a SIP ALG). | ||