ELF4ÄZP4 (p´´´äQäQäQäQäQt,ÌÌÌ‹ ‹ ²Ó  ˆ B¼ü  [ S pppp ppOp#pþÿÿoø ÿÿÿoðÿÿoX CO-52;1&/=':!(3B"7,FG* <@C)DM%0K#$49H+.8N6>IL?EAJˆ  ? B €B àQ äQðQüQRRTT`T(RÓñÿ/Óñÿˆ ! :XTñÿ& B 3XTñÿSñÿLVñÿFXTñÿ›B8 ðAi qàA)ÐA “ÀA°AÙ AA´å€A8pA@`AÛ²PA,V@A0AX A€VA"A®ð@}à@0Ð@ ŠÀ@a°@D¹ @Ã@€*€@±p@`@ÑP@ÔÊ@@ 0@! @¤»@ @Dˆð?;"Ãà?kÐ?£À?°?¼Ë ?=?Ý€?öp?,"S"|`?hP?@‘@?õ0?ê ?õ?_GLOBAL_OFFSET_TABLE__init_gp_disp_fini__cxa_finalize__deregister_frame_info__register_frame_info_Jv_RegisterClassesast_module_unregisterast_unregister_application__ast_module_user_hangup_allast_config_loadoption_verboseast_verboseast_variable_retrieveast_copy_stringatoiast_trueast_config_destroyast_register_applicationast_db_putsscanfsnprintfast_db_getast_waitforast_readast_frame_freesin__ast_lin2muast_writeast_logfdopenast_callerid_parseast_shrink_phone_numberast_localtimestrftimefprintffflushfclosememsetstrlenstrncatmkstemp__ast_module_user_addast_set_write_formatast_set_read_formatast_answer__ast_module_user_removeast_safe_sleepstrcmpast_tvnowast_tvdiff_msstrncmp_ast_callocast_safe_systemast_module_registerlibgcc_s.so.1libc.so.0_ftext_fdata_gp_edata__bss_start_fbss_endGLIBC_2.0 ii QTTRôQèQÄRÌRÐRÔRØRRRR R9' ø ¼¿à ½'<ðÄœ'!à™àÿ½'¿¯°¯¼¯€‚`TB(@4‚@€‚4™DŒ ø ¼ ø R®¼€RŽYŒôÿ C$‚@ €„™ ø àQ„$¼€‚$`TC ¿°à ½'<Äœ'!à™àÿ½'¿¯¼¯8‚ @ €„€…8™àQ„$ ø dT¥$¼€„üQ‚Œ@„€™ üQ„$¿  ½'¿à ½'<€Ãœ'!à™€„Ì€™ ÀR„$ AlarmReceiver: No config file generaleventcmdloudnessfdtimeoutsdtimeoutlogindividualeventseventspooldirtimestampformatdb-family > AlarmReceiver: Creating database entry %s and setting to 1 1%u > AlarmReceiver: New value for %s: %u > AlarmReceiver: database_increment write error > AlarmReceiver: Failed to write frame on %s app_alarmreceiver.cAlarmReceiver Failed to write frame on %s > AlarmReceiver: can't make temporary file AlarmReceiver: can't make temporary file w [metadata] PROTOCOL=%s CALLINGFROM=%s CALLERNAME=%s TIMESTAMP=%s [events] > AlarmReceiver: can't write metadata AlarmReceiver: can't write metadata > AlarmReceiver: Setting read and write formats to ULAW AlarmReceiver: Unable to set write format to Mu-law on %s AlarmReceiver: Unable to set read format to Mu-law on %s ADEMCO_CONTACT_ID > AlarmReceiver: Answering channel > AlarmReceiver: Waiting for connection to stabilize calls-received > AlarmReceiver: Waiting for first event from panel > AlarmReceiver: Sending 1400Hz 100ms burst (ACK) > AlarmReceiver: Sending 2300Hz 100ms burst (ACK) > AlarmReceiver: DTMF Digit Timeout on %s AlarmReceiver: DTMF timeout on chan %s Waitfor returned %d no-events-received == AlarmReceiver: ACK retries during this call: %d ack-retries > AlarmReceiver: App exiting... == AlarmReceiver: Incomplete string: %s, trying again... == AlarmReceiver: Received Event %s AlarmReceiver: Received event: %s == AlarmReceiver: Bad DTMF character %c, trying again checksum-errors == AlarmReceiver: Nonzero checksum AlarmReceiver: Nonzero checksum 1898format-errors == AlarmReceiver: Wrong message type AlarmReceiver: Wrong message type Alarmreceiver: executing: %s app_alarmreceiverAlarm Receiver for AsteriskThis paragraph is copyright (c) 2006 by Digium, Inc. In order for your module to load, it must return this key via a function called "key". Any code which includes this paragraph must be licensed under the GNU General Public License version 2 or later (at your option). In addition to Digium's general reservations of rights, Digium expressly reserves the right to allow other parties to license this paragraph under different terms. Any use of Digium, Inc. trademarks or logos (including "Asterisk" or "Digium") without express written permission of Digium, Inc. is prohibited. AlarmReceiverProvide support for receiving alarm reports from a burglar or fire alarm panel AlarmReceiver(): Only 1 signalling format is supported at this time: Ademco Contact ID. This application should be called whenever there is an alarm panel calling in to dump its events. The application will handshake with the alarm panel, and receive events, validate them, handshake them, and store them until the panel hangs up. Once the panel hangs up, the application will run the system command specified by the eventcmd setting in alarmreceiver.conf and pipe the events to the standard input of the application. The configuration file also contains settings for DTMF timing, and for the loudness of the acknowledgement tones. alarmreceiver_execreceive_ademco_contact_id  0123456789*#ABCreceive_dtmf_digitssend_tone_burstlog_eventswrite_metadata-DTû! @@¿@¯DÀEÏàÁÿÿÿÿ'ÿÿÿÿ€”LÀR¤LôLôQÐÈ%a %b %d, %Y @ %H:%M:%S %Z/event-XXXXXXüœJ0JLJf450f61f60e761b3aa089ebed76ca8a5€TT0',.ð. 5°2à(€6(À7 89 6ÀPp7 7=°:`:àPBðAàAÐAÀA°A AA€ApA`APA@A0A AAAð@à@Ð@À@°@ @@€@p@`@P@@@0@ @@@ð?à?Ð?À?°? ??€?p?`?P?@?0? ??TTGCC: (GNU) 3.3.2GCC: (GNU) 4.2.3GCC: (GNU) 4.2.3GCC: (GNU) 4.2.3GCC: (GNU) 4.2.3GCC: (GNU) 4.2.3GCC: (GNU) 4.2.3GCC: (GNU) 4.2.3GCC: (GNU) 4.2.3GCC: (GNU) 4.2.3GCC: (GNU) 4.2.3GCC: (GNU) 4.2.3GCC: (GNU) 4.2.3GCC: (GNU) 4.2.3GCC: (GNU) 4.2.3GCC: (GNU) 4.2.3GCC: (GNU) 4.2.3GCC: (GNU) 4.2.3GCC: (GNU) 4.2.3GCC: (GNU) 4.2.3GCC: (GNU) 4.2.3GCC: (GNU) 4.2.3GCC: (GNU) 4.2.3GCC: (GNU) 3.3.2ˆ üÿÿÿ  Büÿÿÿ €œ€üÿÿÿ ü€øÿÿÿ0l€øÿÿÿHìÿÀüÿÿÿ`h?€øÿÿÿ¨TÿÀüÿÿÿÐ'0'€üÿÿÿ8(€øÿÿÿ8à(€øÿÿÿ@`)ÿÀüÿÿÿHh-€üÿÿÿ€,.€üÿÿÿ€ð.€øÿÿÿˆ°2€üÿÿÿh 5€üÿÿÿH 6€øÿÿÿ8€6€øÿÿÿ@ 7p7À7 89`:€øÿÿÿ0°:ÿ€øÿÿÿ@=ˆ B.shstrtab.reginfo.dynamic.hash.dynsym.dynstr.gnu.version.gnu.version_r.init.text.MIPS.stubs.fini.rodata.eh_frame.ctors.dtors.jcr.data.rel.ro.data.got.sdata.bss.comment.mdebug.abi32.pdr.rel.dyn p´´ÌÌð¼¼P#   ð+üü[3ÿÿÿoX X ž@þÿÿoø ø Oˆ ˆ ˆU1[??g B BXm€B€B`uàQàQäQäQ †ðQðQ üQüQ’RRŸRR¥SSDªTTTT±`TXT°¶XT°¿VÍVàÒ   pèYÛ