I have been looking a little into SER 0.8.12/14 in the last few days for the first time, and I have a few a questions:-
- I am using SER with the MS RTC 1.2 SDK and I noticed that if I have record_route in the config, the messages between clients don't get through. Is this normal? Is it fixable? If RTC is non-compliant could a MS compliant module be created (just a thought)?
- I would like to send a MESSAGE to the server@192.168.2.2 so I can tell the server to perform particular functions, I have set-up a exec_msg to capture these messages to server@192.168.2.2 to send to a script file, however looking at the environment from the script file I cannot see the actual message content. Again, is this possible?
I'm sure I'll have more questions but that'll do for now :) Thank-you!
On 7/29/2004 12:56 AM, Andrew Mee wrote:
I have been looking a little into SER 0.8.12/14 in the last few days for the first time, and I have a few a questions:-
- I am using SER with the MS RTC 1.2 SDK and I noticed that if I have
record_route in the config, the messages between clients don't get through. Is this normal? Is it fixable? If RTC is non-compliant could a MS compliant module be created (just a thought)?
I do not know about latest M$ RTC, but old ones did not support lr parameter for loose routing in its short form (e.g., lr). You need to set enable_full_lr parameter of rr module so there will be used lr=on which proved to work with M$.
- I would like to send a MESSAGE to the server@192.168.2.2 so I can
tell the server to perform particular functions, I have set-up a exec_msg to capture these messages to server@192.168.2.2 to send to a script file, however looking at the environment from the script file I cannot see the actual message content. Again, is this possible?
Extracted from README:
1.4.2. exec_msg(command)
Executes an external command. The whole message is passed to it in input, no command-line parameters are added, output of the command is not processed.
You should be able to read the whole message from input in your script.
If you can achieve what you want with exec module, you may consider writing your own module.
Daniel
I'm sure I'll have more questions but that'll do for now :) Thank-you!
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
I do not know about latest M$ RTC, but old ones did not support lr parameter for loose routing in its short form (e.g., lr). You need to set enable_full_lr parameter of rr module so there will be used lr=on which proved to work with M$.
Ok this worked, thanks. However I will read a little more into loose routing, I would have liked all messages to go through the server.
Extracted from README: 1.4.2. exec_msg(command) Executes an external command. The whole message is passed to it in input, no command-line parameters are added, output of the command is not processed. You should be able to read the whole message from input in your script. If you can achieve what you want with exec module, you may consider writing your own module.
When I sent it to a PHP script and had a look at the environment variables, the information Message content wasn't there. I also tried reading the stdin to see if I read the message content this way, however the header comes through but not the content
-
Andrew Mee -
Daniel-Constantin Mierla