<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.2627" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=570113620-08062005><FONT face=Arial size=2>I have set up ser
with mediaproxy and sems according to example configs. When I start up
mediaproxy, ser and sems all phones register properly and calls can be placed
internally (have no external gate yet). I also tried calling a UA not onlie to
get sems to take the call and it works great. So I tell my beta tester to start
testing.... </FONT></SPAN></DIV>
<DIV><SPAN class=570113620-08062005><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=570113620-08062005><FONT face=Arial size=2>1 day after,
all calls are rejected because of server error. I have to restart everything and
it works again, only to fail the day after... </FONT></SPAN></DIV>
<DIV><SPAN class=570113620-08062005><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=570113620-08062005><FONT face=Arial size=2>These entries
are found in the log for every call I try to make when ser stopped
working.</FONT></SPAN></DIV>
<DIV><SPAN class=570113620-08062005><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=570113620-08062005><FONT face=Arial size=2>Jun 8 22:42:33
ns2 ser[523]: ERROR: t_newtran: transaction already in process
0x29830c58<BR>Jun 8 22:42:33 ns2 ser[523]: ERROR: sl_reply_error used: I'm
terribly sorry, server error occurred (1/SL)<BR></FONT></SPAN></DIV>
<DIV><SPAN class=570113620-08062005><FONT face=Arial size=2>Error message on
SJPhone is "number not available"</FONT></SPAN></DIV>
<DIV><SPAN class=570113620-08062005><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=570113620-08062005><FONT face=Arial size=2>The error message
about t_newtran tells me this is caused by a part of the config added for sems
to work. Also it seems that after putting the t_newtran in the config there
should be some t_release as well since I get this message
repeatedly after restarting ser. However I can not find any
documentation stating this is necessary or where this should be put in place
within ser.cfg.</FONT></SPAN></DIV>
<DIV><SPAN class=570113620-08062005><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=570113620-08062005><FONT face=Arial size=2>Jun 8 22:53:34
ns2 ser[4898]: WARNING: script writer didn't release
transaction</FONT></SPAN></DIV>
<DIV><SPAN class=570113620-08062005><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=570113620-08062005><FONT face=Arial size=2>If I comment out the
SEMS configuration lines withing ser.cfg and restart ser. It works properly
again....</FONT></SPAN></DIV>
<DIV><SPAN class=570113620-08062005><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=570113620-08062005><FONT face=Arial size=2>First, is there any
any one with a ser.cfg script that works with sems without the error/waring
messages above being logged? If so please send it to me.</FONT></SPAN></DIV>
<DIV><SPAN class=570113620-08062005><FONT face=Arial size=2>Secondly, have any
one written any official documentation about this product, including different
scenarios? Since the system is widely used I do not understand why there is no
official documentation available. Dont say onsip, no more help to find
there.</FONT></SPAN></DIV>
<DIV><SPAN class=570113620-08062005><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=570113620-08062005><FONT face=Arial size=2></FONT></SPAN><SPAN
class=570113620-08062005><FONT face=Arial
size=2> </DIV></FONT></SPAN></BODY></HTML>