Hi Juha, Thanks for illumination. How do I use sip control rather than t_write_unix?
--Ling ----- Original Message ---- From: Juha Heinanen <[email protected]> To: [email protected] Cc: [email protected] Sent: Sunday, March 8, 2009 9:46:18 PM Subject: Re: [Sems] How does conf_auth communicte with conference plug-in? [email protected] writes: > In my example I set self.conf_to = sip:[email protected] and self.conf_uri > > = sip:[email protected]. The conference is set up as below to be > connected from ser: > > if (uri =~"sip:6789@"){ > t_write_unix("/tmp/sems_sock", "conference"); > } > > It is ok to dial in to 6789 from ser and directly get into the > conference. it should work if the above script code gets executed when invite comes in. > However, if calling from conf_auth, after authentication was ok and > the conf_auth was connecting to [email protected] then it > returned "400 Request-URI is invalid". Can you please tell me what's > wrong in this example? i cannot, because you didn't show the exact logs of what happened. most likely the problem is what the error tells, i.e., you made some mistake in self.conf_uri. > Another question is whyin the debug out the Contact field in SIP > header is Contact: <sip:s...@!!>? What does that mean of a domain > "!!"? i think ser will replace !! with ip address of your proxy. by the way, you should use sip control rather than t_write_unix. -- juha _______________________________________________ Sems mailing list [email protected] http://lists.iptel.org/mailman/listinfo/sems
