[Home]

Summary:ASTERISK-29524: The patterns "*" and "#" do not work when calling via a PJSIP trunk
Reporter:Max Arturo (maxarturo)Labels:
Date Opened:2021-07-19 12:47:32Date Closed:2021-07-19 12:52:58
Priority:MinorRegression?
Status:Closed/CompleteComponents:Resources/res_pjsip_session
Versions:16.2.1 Frequency of
Occurrence		Constant
Related
Issues:
duplicatesASTERISK-28767 chan_pjsip: Caller ID not used when checking for extension, callerid supplement executed too late
Environment:deb10u2Attachments:
Description:Two identical servers:
1) ServerA, extensions 1XX, all SIP interfaces.
2) ServerB extensions 2XX, all PJSIP interfaces.
3) Servers A and B were connected via IAX2 (and then there was no problem described below). The server connection was replaced with a PJSIP trunk.
4) Fragments of extensions.conf from both servers:
Fragment of extensions.conf ServerA:
[call-out]
exten => 777/213,1,GoTo(kommutator,s,1)
exten => _*80XXX/213,1,Answer()
same => n,MusicOnHold(native-random)
same => n,HangUp()

Fragment of extensions.conf ServerB:
[call-out]
exten => _[1-9]XX,1,Dial(PJSIP/${EXTEN}@my-trunk)
exten => _*80XXX,1,Dial(PJSIP/${EXTEN}@my-trunk)

5) I make a call from ServerB to ServerA from interface 213:
5.1) I call 777 - the call is successful;
5.2) I call *80777. In the ServerB console, I see that the call is successful. In the ServerA console I see: NOTICE [10838]: res_pjsip_session.c: 2993 new_invite: Call from '/ trunk-name /' (UDP: <IP>: <PORT>) to extension '*80777' rejected because extension not found in context 'call -out '.

6) if I replace the extensions on ServerA:
6.1) exten => _*80XXX,1, ... - the call from ServerB is successful;
6.2) exten => _80XXX/213,1,... - the call from ServerB is successful;
6.3) the problem occurs only if the pattern begins with "*" or "#" and contains an indication of the subscriber, as in the example: "/213".
Comments:By: Asterisk Team (asteriskteam) 2021-07-19 12:47:36.742-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. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed.

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.

Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/].