Summary: | ASTERISK-30415: Asterisk DID range numbers cant able to show up | ||
Reporter: | Prasanth P (prasanthcraysol) | Labels: | |
Date Opened: | 2023-02-02 06:44:17.000-0600 | Date Closed: | 2023-02-02 06:44:23.000-0600 |
Priority: | Critical | Regression? | |
Status: | Closed/Complete | Components: | Functions/func_callerid |
Versions: | 1.8.20.2 | Frequency of Occurrence | |
Related Issues: | |||
Environment: | Attachments: | ||
Description: | Please support us; we have setup an Asterisk PBX server for SIP outbound connections and configured the dial plan based on DID range numbers as the caller ID number. However, instead of showing DID range numbers, only the pilot number (4847XXXX00) appears at the user end.
sip.conf bindaddr=0.0.0.0 context=default canreinvite=no callcounter=yes notifyhold=yes callevents=yes language=en srvlookup=no directrtpsetup=yes directmedia=yes trustpid=yes sendrpid=yes qualify=yes callevents=yes insecure=invite pedantic=no videosupport=no t38pt_udptl=no t38pt_rtp=no t38pt_tcp=no dtmfmode=auto disallow=all allow=ulaw allow=alaw [1101] username=1101 secret=XXXX type=friend nat=yes context=CRAY1 host=dynamic qualify=1000 mailbox=1100 extensions.conf [general] static=yes writeprotect=no autofallthrough=no [globals] TRUNK=DAHDI/g4 [default] [CRAY1] exten => _9XXXXXXXXX,1,Set(CALLERID(num)=4847XXXX90); exten => _9XXXXXXXXX,2,Dial(DAHDI/g4/0${EXTEN}); exten => _9XXXXXXXXX,3,Hangup(); | ||
Comments: | By: Asterisk Team (asteriskteam) 2023-02-02 06:44:21.815-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. 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/]. By: Asterisk Team (asteriskteam) 2023-02-02 06:44:22.826-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 |