[Home]

Summary:ASTERISK-27574: Asterisk rejecting invites == 416 Unsupported URI scheme
Reporter:Anton Satskiy (satskiy.a)Labels:
Date Opened:2018-01-11 07:47:12.000-0600Date Closed:2020-01-14 11:24:13.000-0600
Priority:MajorRegression?
Status:Closed/CompleteComponents:Channels/chan_sip/General
Versions:11.25.1 Frequency of
Occurrence
Related
Issues:
Environment:Asterisk 11.25.1Attachments:
Description:2018/01/11 14:12:38.182826 93.85.255.188:5060 -> 192.168.100.249:5060
INVITE sip:+375249102711@192.168.100.249:5060 SIP/2.0
Via: SIP/2.0/UDP 93.85.255.188:5060;branch=z9hG4bKd7awnegnp7def7g4pa1e7xg11T26643
Call-ID: asbcgrvl3ip0j30gz121p80vhr30ap3lvl88@ATS.ats02.ims.beltel.by.132
From: <tel:+74951328884;cpc-rus=1>;tag=sbc0511gax208l8-CC-132
To: <sip:+375249102711@93.85.255.188:5060;transport=udp;user=phone>
CSeq: 1 INVITE
Allow: INVITE,ACK,BYE,CANCEL,UPDATE,INFO,PRACK,NOTIFY,REFER,SUBSCRIBE,OPTIONS,MESSAGE
Contact: <sip:+74951328884@93.85.255.188:5060;user=phone>
Max-Forwards: 66
Supported: 100rel,timer
Session-Expires: 600
Min-SE: 600
P-Asserted-Identity: <tel:+74951328884>
P-Called-Party-ID: <tel:+375249102711>
Content-Length: 375
Content-Type: application/sdp

v=0
o=- 38248362 38248362 IN IP4 93.85.255.185
s=SBC call
c=IN IP4 93.85.255.185
t=0 0
m=audio 25682 RTP/SAVP 8 0 18 116
a=fmtp:18 annexb=no
a=rtpmap:116 telephone-event/8000
a=ptime:20
a=sendrecv
a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:Rmg2Unc3SGUwVHQzUmEyUmQ4Q3UwQmM5VXo4VHcy
a=crypto:2 AES_CM_128_HMAC_SHA1_32 inline:Rmg2Unc3SGUwVHQzUmEyUmQ4Q3UwQmM5VXo4VHcy

2018/01/11 14:12:38.183447 192.168.100.249:5060 -> 93.85.255.188:5060
SIP/2.0 416 Unsupported URI scheme
Via: SIP/2.0/UDP 93.85.255.188:5060;branch=z9hG4bKd7awnegnp7def7g4pa1e7xg11T26643;received=93.85.255.188;rport=5060
From: <tel:+74951328884;cpc-rus=1>;tag=sbc0511gax208l8-CC-132
To: <sip:+375249102711@93.85.255.188:5060;transport=udp;user=phone>;tag=as5e85784a
Call-ID: asbcgrvl3ip0j30gz121p80vhr30ap3lvl88@ATS.ats02.ims.beltel.by.132
CSeq: 1 INVITE
Server: FPBX-13.0.192.19(11.25.1)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0


2018/01/11 14:12:38.189362 93.85.255.188:5060 -> 192.168.100.249:5060
ACK sip:+375249102711@192.168.100.249:5060 SIP/2.0
Via: SIP/2.0/UDP 93.85.255.188:5060;branch=z9hG4bKd7awnegnp7def7g4pa1e7xg11T26643;received=93.85.255.188;rport=5060
Call-ID: asbcgrvl3ip0j30gz121p80vhr30ap3lvl88@ATS.ats02.ims.beltel.by.132
From: <tel:+74951328884;cpc-rus=1>;tag=sbc0511gax208l8-CC-132
To: <sip:+375249102711@93.85.255.188:5060;transport=udp;user=phone>;tag=as5e85784a
CSeq: 1 ACK
Max-Forwards: 70
Content-Length: 0

=================

register=>+375249102711@ims.beltel.by:XXXXXXXX:+375249102711@ims.beltel.by@93.85.255.188:5060/+375249102711

[TRUNK]
username=+375249102711@ims.beltel.by
fromuser=+375249102711
secret=XXXXXXX
host=93.85.255.188
fromdomain=ims.beltel.by
type=friend
context=from-trunk
insecure=port,invite
trustrpid=yes
sendrpid=yes
directmedia=no
qualify=yes
keepalive=45
nat=yes
dtmfmode=rfc2833
disallow=all
allow=ulaw,alaw
encryption=no
Comments:By: Asterisk Team (asteriskteam) 2018-01-11 07:47:13.220-0600

Per the Asterisk versions page [1], the maintenance (bug fix) support for the Asterisk branch you are using has ended. For continued maintenance support please move to a supported branch of Asterisk. After testing with a supported branch, if you find this problem has not been resolved, please open a new issue against the latest version of that Asterisk branch.

Thanks!

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions
By: Asterisk Team (asteriskteam) 2018-01-11 07:47:14.291-0600

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].