DND settings not making it to astmanager
DND settings aren't making it to astmanager.
Watching asterisk manager for the events, logged into fop2 via the web interface, and have the daemon running in debug foreground to see what I get.
I login as an extension number, and get the usual flash display. I can change the drop-down to DND, and in the fop2 daemon I see the error:
Connection to AMI from fop2 works fine, I can see the active session.
Snippets of the config as follows:
Can anyone spot what the perl/patten match error in fop2_server.pl is please? Nic could you advise what those lines are in the raw uncompiled code that would help where we've gone wrong here please?
Regards,
Andy
Watching asterisk manager for the events, logged into fop2 via the web interface, and have the daemon running in debug foreground to see what I get.
I login as an extension number, and get the usual flash display. I can change the drop-down to DND, and in the fop2 daemon I see the error:
Use of uninitialized value in pattern match (m//) at script/fop2_server.pl line 9302.
Use of uninitialized value in concatenation (.) or string at script/fop2_server.pl line 9360.
Connection to AMI from fop2 works fine, I can see the active session.
Snippets of the config as follows:
[general]
; AMI definitions
manager_host=localhost
manager_port=5038
manager_user=admin
manager_secret=blahblah
user=3228:1234:all
[EXTENSION/3228]
type=extension
label=3228-ACCTS-REP
context=from-internal
Can anyone spot what the perl/patten match error in fop2_server.pl is please? Nic could you advise what those lines are in the raw uncompiled code that would help where we've gone wrong here please?
Regards,
Andy
Comments
I didn't have a valid extension=3228 line in the [EXTENSION/3228] section. Therefore it didn't have a full list of buttons along the top, and since it was classed as 'not a valid extension' it wasn't writing values to the asterisk database.