[sr-dev] [tracker] Task opened: Proto names are causing parser errors

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Nils Ohlmeier (nils) Attached to Project - sip-router Summary - Proto names are causing parser errors Task Type - Bug Report Category - Core Status - Assigned Assigned To - Andrei Pelinescu-Onciul Operating System - All Severity - Medium Priority - Normal Reported Version - Development Due in Version - Undecided Due Date - Undecided Details - When the configuration file contains a statement like this: if (proto==TCP) { this is causing a parser errors at the startup of SER like this: 0(26225) : <core> [cfg.y:3163]: parse error in config file /home/lando/sip-router/etc/sip-router-basic.cfg, line 76, column 13-15: syntax error 0(26225) : <core> [cfg.y:3163]: parse error in config file /home/lando/sip-router/etc/sip-router-basic.cfg, line 76, column 13-15: number expected 0(26225) : <core> [cfg.y:3166]: parse error in config file /home/lando/sip-router/etc/sip-router-basic.cfg, line 76, column 16: bad expression 0(26225) : <core> [cfg.y:3166]: parse error in config file /home/lando/sip-router/etc/sip-router-basic.cfg, line 76, column 16: invalid route statement Currently only statements like this are working: if (proto==2) { More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=15 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.