looking for testers for app_meetme AMI patch

Report
Question

Hello, I've created a patch to correct error responses for the MeetMeList manager action. Currently MeetMeList produces an error if no conferences are active, success if any conferences are open. Requesting a conference that is not active while other conferences are active does not produce an error. https://issues.asterisk.org/view.php?id=18141 With the patch (app_meetme-r319651-meetmelist_error_reporting.diff):
If Conference is not specified then it's no longer an error if no conferences are active.
If Conference is specified that is not active it is an error. Please leave any notes on the issue tracker, if you respond to this mailing list please…

Asterisk Users 4.3 years ago 0 Answers

AstLinux 0.7.8 Release

Report
Question

The AstLinux Team would like to announce the immediate availability of
the 0.7.8 release. This release includes either Asterisk 1.4.41 or
Asterisk 1.8.4. All current users are encouraged to upgrade to this
release to take advantage of bug fixes and other updates to Asterisk. Please note that there is a bug in Asterisk 1.8.4 that will prevent
Cisco 79xx phones from registering. A full changelog is available at http://www.astlinux.org Current users can upgrade from the web interface or from the commandline. From the CLI: (Asterisk 1.4)
upgrade-run-image check http://mirror.astlinux.org/firmware

Asterisk Users 4.3 years ago 0 Answers

SIP Diversion RDNIS - how to get reason parameter?

Report
Question

Hi Olivier > Are those PBXs directly connected to each other through a SIP trunk ? Yes, and the reason is definitely transmitted in the SIP header and also
parsed by asterisk and displayed in debug output. After reading a bit more in chan_sip.c (I'm not a coder) I fear the result is
just put in a temporary variable __SIPDIVERSIONREASON but not in a variable
useable in the dialplan.

Asterisk Users 4.3 years ago 0 Answers

Hints custom:abcdef

Report
Question

Hello list, I want certain devices to monitor certain extensions/SIPaccounts and
other devices to monitor other extensions/SIPaccounts. Therefore I do the following : [from-TEST1] include => test1-blf [from-TEST2] include => test2-blf [test1-blf]
exten => 10,hint,SIP/testcorp1
exten => 20,hint,SIP/testcorp2 [test2-blf]
exten => 10,hint,SIP/testcorp110
exten => 20,hint,SIP/testcorp120
SIPaccounts with a context definition of "from-TEST1" can not monitor
the extensions of test2-blf.
SIPaccounts with a context definition of "from-TEST2" can not monitor
the extensions of test1-blf.
This works great. But now I have a problem with custom hints. When I do…

Asterisk Users 4.3 years ago 0 Answers