[Home]

Summary:ASTERISK-28514: phoneprov and RealTime
Reporter:Oleg (olegsenin)Labels:pjsip
Date Opened:2019-08-26 03:24:48Date Closed:2019-08-27 05:00:34
Priority:TrivialRegression?
Status:Closed/CompleteComponents:Resources/res_phoneprov Resources/res_realtime
Versions:16.5.0 Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:Please tell how phoneprov run in RealTime.
I tried:
/etc/asterisk/extconfig.conf
ps_endpoints => odbc,asterisk
ps_auths => odbc,asterisk
ps_aors => odbc,asterisk
ps_domain_aliases => odbc,asterisk
ps_endpoint_id_ips => odbc,asterisk
ps_phoneprov => odbc,asterisk

/etc/asterisk/sorcery.conf
[res_pjsip_phoneprov_provider]
phoneprov = realtime, ps_phoneprov

SELECT * FROM `ps_phoneprov` WHERE 1;
+------+-----------+----------+--------------+---------+------+---------+-------------+
| id   | type      | endpoint | MAC          | PROFILE | LINE | LABEL   | SERVER      |
+------+-----------+----------+--------------+---------+------+---------+-------------+
| 2778 | phoneprov | 2778     | 805ec0830055 | yealink |    1 | yealink | 10.40.0.164 |
| 7001 | phoneprov | 7001     | 805EC0830055 | yealink |    1 | yealink | NULL        |
+------+-----------+----------+--------------+---------+------+---------+-------------+
But in Dynamic routes, the phone does not appear.
If using pjsip.conf:
[2775]
type = phoneprov
endpoint = 2775
MAC = 805EC0830055; $ {MAC}
PROFILE = yealink_t19_0053
then everything works.
Comments:By: Asterisk Team (asteriskteam) 2019-08-26 03:24:49.872-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: Asterisk Team (asteriskteam) 2019-08-26 03:24:52.184-0500

We appreciate the difficulties you are facing, however information request type issues would be better served in a different forum.

The Asterisk community provides support over IRC, mailing lists, and forums as described at http://asterisk.org/community. The Asterisk issue tracker is used specifically to track issues concerning bugs and documentation errors.

If this issue is actually a bug please use the Bug issue type instead.

Please see the Asterisk Issue Guidelines [1] for instruction on the intended use of the Asterisk issue tracker.

Thanks!

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

By: Asterisk Team (asteriskteam) 2019-08-27 01:38:46.568-0500

This issue has been reopened as a result of your commenting on it as the reporter. It will be triaged once again as applicable.