|
Development |
Development.Messagecontext HistoryHide minor edits - Show changes to output October 04, 2008, at 12:38 AM
by -
Changed lines 14-16 from:
same as above but for modules. to:
same as above but for modules. Question: what does it bring as facility to the configuration script. Could we imagine to have "contexts" a la Asterisk here routing rules could differ per class of users? October 03, 2008, at 02:30 PM
by -
Changed lines 2-3 from:
to:
---- October 03, 2008, at 02:30 PM
by -
Changed lines 1-2 from:
!! Development -> [[Development.SandBox | Sand Box]] -> Dynamic Routing to:
!! Development -> [[Development.SandBox | Sand Box]] -> SIP_MSG context October 03, 2008, at 02:29 PM
by -
Changed lines 1-3 from:
Step 1: \ to:
!! Development -> [[Development.SandBox | Sand Box]] -> Dynamic Routing Step 1: \\ Changed line 6 from:
Step 2: \ to:
Step 2: \\ Changed line 9 from:
Step 3: \ to:
Step 3: \\ Changed lines 12-13 from:
Step 4: \ same as above but for moduels. to:
Step 4: \\ same as above but for modules. October 03, 2008, at 02:27 PM
by -
Added lines 1-11:
Step 1: \ create a MSGcontext structure and move all non-sip_msg fields out of the struct sip_msg Step 2: \ move the branches (static global array) into the context Step 3: \ identify the core global variables that are related to sip_msg processing and move them into the msg context Step 4: \ same as above but for moduels. |