Development

Development.Messagecontext History

Hide minor edits - Show changes to markup

October 03, 2008, at 11:38 PM by 82.228.184.247 -
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 01:30 PM by 81.180.102.217 -
Changed lines 2-3 from:
to:

October 03, 2008, at 01:30 PM by 81.180.102.217 -
Changed lines 1-2 from:

Development -> Sand Box -> Dynamic Routing

to:

Development -> Sand Box -> SIP_MSG context

October 03, 2008, at 01:29 PM by 81.180.102.217 -
Changed lines 1-3 from:

Step 1: \

to:

Development -> 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 01:27 PM by 81.180.102.217 -
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.


Page last modified on March 02, 2009, at 06:12 PM