[Home]

Summary:ASTERISK-25236: Asterisk reject incoming call from FXO gateway
Reporter:Smirnov Aleksey (limpsobaka)Labels:
Date Opened:2015-07-08 10:56:49Date Closed:2020-01-14 11:14:14.000-0600
Priority:MajorRegression?
Status:Closed/CompleteComponents:
Versions:13.2.0 13.4.0 Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:We have AddPac 1100F gateway.
On FXO port is set connection plar 4400.
When I call on FXO asterisk reject incomming call with:
{noformat}
Found peer '4401' for '192.168.1.22' from 192.168.1.250:5060

<--- Reliably Transmitting (no NAT) to 192.168.1.250:5060 --->
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.1.250:5060;branch=z9hG4bKe2550f06a41;received=192.168.1.250
From: <sip:192.168.1.22>;tag=e2550f06a4
To: <sip:4400@192.168.1.22>;tag=as4e8b06bb
Call-ID: e26f9d55-8c66-0f12-8006-0002a40846f6@192.168.1.250
CSeq: 1 INVITE
Server: Asterisk PBX 13.4.0
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="221e4c36"
Content-Length: 0
{noformat}
4400 - extension on asterisk
4401 - FXS1 on AddPac, Registered on asterisk by realtime mysql
192.168.1.250 - IP Addpac
192.168.1.22 - IP Asterisk
{noformat}
sip.conf
[test]
type=peer
context=office
host=192.168.1.250
insecure=port,invite
{noformat}
What I found in debug sip is on the asterisk:

Found peer '4401' for '192.168.1.22' from 192.168.1.250:5060

Asterisk found user 4401 for call. Peer for this call is test.
If I add peer test to mysql all work fine.
In older versions (11, 1.8) all works fine with the same configs.
Comments:By: Asterisk Team (asteriskteam) 2015-07-08 10:56:50.701-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].
By: Rusty Newton (rnewton) 2015-07-08 16:18:06.331-0500

We require additional debug to continue with triage of your issue. Please follow the instructions on the wiki [1] for how to collect debugging information from Asterisk. For expediency, where possible, attach the debug with a '.txt' file extension so that the debug will be usable for further analysis.

We need the debug from your example scenario for both failing and working scenarios. That is, for both the 13 and 11.

Be sure to follow the documentation explicitly. You need to make sure the DEBUG and VERBOSE log channels appear in your log before attaching the resulting log to the issue.


Thanks!

[1] https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information


By: Asterisk Team (asteriskteam) 2015-07-23 12:00:21.621-0500

Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1].

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