Development |
Development.Design-Opensips-Script-Rework HistoryHide minor edits - Show changes to markup December 13, 2018, at 05:09 PM
by
- Changed line 1 from:
to:
December 12, 2018, at 06:31 PM
by
- Changed line 32 from:
fr_timer = 4 to:
fr_timeout = 4 December 12, 2018, at 06:31 PM
by
- Changed line 44 from:
failure_route [resume] {...} to:
failure_route [call_failure] {...} Added line 46:
... December 12, 2018, at 06:30 PM
by
- Changed line 19 from:
[@ example to:
[@ opensips-3.0.cfg December 12, 2018, at 06:30 PM
by
- Changed line 21 from:
to:
Changed line 30 from:
to:
December 12, 2018, at 06:29 PM
by
- Changed line 41 from:
to:
December 12, 2018, at 06:28 PM
by
- Added line 35:
Changed lines 41-42 from:
to:
December 12, 2018, at 06:27 PM
by
- Changed line 27 from:
mpath = "/tmp/test/" to:
mpath = "/usr/lib/x86_64-linux-gnu/opensips/modules" December 12, 2018, at 06:26 PM
by
- Changed lines 24-25 from:
log_name = "opensips_proxy.log" to:
log_stderror = no log_facility = LOG_LOCAL0 December 12, 2018, at 06:25 PM
by
- Changed line 23 from:
debug = 4 to:
log_level = 4 Changed line 25 from:
listen = 1.1.1.1 to:
listen = udp:1.1.1.1 December 12, 2018, at 06:25 PM
by
- Changed lines 22-25 from:
debug = 4 log_name = "opensips_proxy.log" listen = 1.1.1.1 mpath = "/tmp/test/" to:
core { debug = 4 log_name = "opensips_proxy.log" listen = 1.1.1.1 mpath = "/tmp/test/" } December 12, 2018, at 02:06 PM
by
- Changed line 45 from:
This idea was discussed with the community beforehand, during this 2015 IRC meeting. to:
The problem and its solution have already been discussed together with the community, during this 2015 IRC meeting. December 12, 2018, at 02:05 PM
by
- Deleted line 0:
Community -> PublicMeetings -> 30th of September 2015December 12, 2018, at 02:04 PM
by
- Added lines 1-46:
Community -> PublicMeetings -> 30th of September 2015Development -> Topics? -> OpenSIPS Script ReworkProblems to be addressedThere are two types of problems with the current OpenSIPS scripting language, which relate to both its structure and functionality:
Proposed SolutionTrying to address the above issues, we suggest a new format for the configuration script: 1) a simple re-structuring to solve the problems, but trying to keep a similarity with the actual structure. The grammar will enforce three main sections in the cfg file, in a certain order:
example # script starts with the global param section debug = 4 log_name = "opensips_proxy.log" listen = 1.1.1.1 mpath = "/tmp/test/" # after global params we have the section dealing with modules loadmodule [tm] { fr_timer = 4 timer_partitions = 2 } loadmodule [avpops] { db_url = "mysql://user:passwd@host/database" use_domain = 1 } # last section is exclusively for routing routes route {...} failure_route [resume] {...} local_route {...} HistoryThis idea was discussed with the community beforehand, during this 2015 IRC meeting. |