callomonitor

columbo1979

Mitglied
Mitglied seit
3 Apr 2006
Beiträge
639
Punkte für Reaktionen
1
Punkte
18
Hallo,
ich bekomme immer den fehler :

Saving listeners...done.
1: Invalid event specification
event: ^01xxxxxx
source: ^SIP3
dest: /bin/ether-wake
action: -i lan xxxxxxxxxxxxxxxx
2: Invalid event specification
event: ^xxxxxxxxxxxxxxxx
source: ^SIP3
dest: /bin/ether-wake
action: -i lan xxxxxxxxxxxxxxxx
3: Invalid event specification
event: ^
source: ^
dest: yac
action: 192.168.0.2
4: Invalid event specification
event: ^
source: ^
dest: mail_missed_call
action: -s "Oh, oh ... ($SOURCE)"
Please correct the errors.

Wo kann da der fehler liegen ? danke !
 
Habe nun jeweils ein in:request gepackt. fehler weg. aber beim testanruf kommt dies :

including /usr/lib/callmonitor/actions.d/dboxlcd.sh
including /usr/lib/callmonitor/actions.d/dial.sh
including /usr/lib/callmonitor/actions.d/dropbear.sh
including /usr/lib/callmonitor/actions.d/mail.sh
including /usr/lib/callmonitor/actions.d/messages.sh
>>> in:request ID=1 TIMESTAMP=20.06.06 14:32 SOURCE=xxxxxxx DEST=xxxxEXT=4 DURATION=16
[0] EVENT=in:request SOURCE='xxxx' DEST='xxxx' SOURCE_NAME='' DEST_NAME='' ID=1 EXT=4 DURATION=16 TIMESTAMP='20.06.06 14:32'
[0:0] processing rule 'in:request' '^xxxxx' '^SIP3' '/bin/ether-wake -i lan xxxxxxxxxxxxx'
[0:0] event 'in:request' matches pattern 'in:request'
[0:0] parameter SOURCE='xxxx' matches pattern '^xxxx'
[0:0] parameter DEST='xxxx' does NOT match pattern '^SIP3'
[0:0] FAILED
[0:1] processing rule 'in:request' '^xxxx' '^SIP3' '/bin/ether-wake -i lan xxxxxxx'
[0:1] event 'in:request' matches pattern 'in:request'
[0:1] parameter SOURCE='xxxx' does NOT match pattern '^xxxxx'
[0:1] FAILED
[0:2] processing rule 'in:request' '^' '^' 'yac 192.168.0.2'
[0:3] processing rule 'in:request' '^' '^' 'mail_missed_call -s "Oh, oh ... ($SOURCE)"'
[0:2] event 'in:request' matches pattern 'in:request'
[0:2] parameter SOURCE='xxxx' matches pattern '^'
[0:2] parameter DEST='xxxx' matches pattern '^'
[0:2] SUCCEEDED: executing 'yac 192.168.0.2'
[0:3] event 'in:request' matches pattern 'in:request'
[0:3] parameter SOURCE='xxx' matches pattern '^'
[0:3] parameter DEST='xxxx' matches pattern '^'
[0:3] SUCCEEDED: executing 'mail_missed_call -s "Oh, oh ... ($SOURCE)"'
/usr/sbin/callmonitor-test: eval: 1: mail_missed_call: not found
[0:3] listener failed with an exit status of 127
nc: connect: Connection refused
[0:2] listener failed with an exit status of 1

Wobei die Regel stimmt. Woran kann dies liegen ? Danke !
 
columbo1979 schrieb:
[0:0] parameter DEST='xxxx' does NOT match pattern '^SIP3'
[...]
[0:1] parameter SOURCE='xxxx' does NOT match pattern '^xxxxx'
[...]
/usr/sbin/callmonitor-test: eval: 1: mail_missed_call: not found
Diese drei Meldungen sollten doch eigentlich Auskunft darüber geben, was genau schief läuft...


Gruß,
Wichard
 
Kostenlos!

Neueste Beiträge

Statistik des Forums

Themen
248,901
Beiträge
2,304,562
Mitglieder
378,604
Neuestes Mitglied
Duggy