-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hello,
I'm quite unsure about openser's hangling of message processing. So can anybody answere following 2 questions please ?
1. When multiple messages come in, lets say 3 INVITEs. Will openser fork one child for each message, run the route script and terminate the child after that? Or will openser throw all 3 INVITEs at the same time into the route script?
2. If the 3 INVITEs share the same route script, are they handled sequentially? What happens to the AVPs and $var variables? Are they gonna mixed?
regards Helmut
Hi Helmut,
Helmut Kuper wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hello,
I'm quite unsure about openser's hangling of message processing. So can anybody answere following 2 questions please ?
- When multiple messages come in, lets say 3 INVITEs. Will openser fork
one child for each message, run the route script and terminate the child after that? Or will openser throw all 3 INVITEs at the same time into the route script?
no - openser has a fix number of worker processes (handling SIP traffic) - the received packages are read randomly by an idle worker and processed. There are no dynamic processes.
- If the 3 INVITEs share the same route script, are they handled
sequentially? What happens to the AVPs and $var variables? Are they gonna mixed?
Requests cannot share the script - each processes handles only one request at a time. Of course, multiple requests can be processed in the same time, but by multiple processes and with no interferences. The AVPs are per request/transaction. $var are persistent across a process.
regards, bogdan
regards Helmut
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHVRWA4tZeNddg3dwRAkQZAJ9Ruy3kr2RzODDlm55uZ4Y6yZTcPACgrl+v qmOW524gE6vgsWNgOalpfW4= =oR4D -----END PGP SIGNATURE-----
Users mailing list Users@lists.openser.org http://lists.openser.org/cgi-bin/mailman/listinfo/users
-
Bogdan-Andrei Iancu -
Helmut Kuper