Hi,
Thank you very much for the support, I tried a lot of combinations but at
the end with no luck. Now I don't face the problem of calls getting 500
error response :-) but still my calls are peer-to-peer and not through the
SEMS. When I observe the INVITE message that is sent out from the SER-SEMS
running machine to the remote Xlite phone, I observed that the "a:
Connection Information:" parameter under SDP is still the Caller-Xlite and
not SEMS. So still my calls are not through SEMS. Need help in resolving
this issue.
Regards,
Ranganath B
On Thu, Apr 10, 2008 at 3:52 PM, Stefan Sayer <[EMAIL PROTECTED]>
wrote:
> Hello,
>
> Ranganath B wrote:
>
> > Hi,
> >
> > After reading through the "SEMS-mini Howto on how to configure SER and
> > SEMS to work together", I could successfully register 2 Xlite Softphones and
> > now I found that the INVITE message is being sent from SER to SEMS. After
> > receiving INVITE message from SER, SEMS gives the error message "ERROR:
> > startSessionUAS (AmSessionContainer.cpp:257): startSession: Unknown
> > Application" and responds with "500 I'm terribly sorry, server error
> > occurred (1/SL)" and "500 Unknown Application". Please help me in resolving
> > this issue, working conf files ser.cfg and sems.conf would also be of great
> > help.
> >
> > Now I am running SEMS and only one instance of SER at port 5060.
> >
> if you only want to use sems with one application, e.g. conference, you
> can use second parameter of t_write_unix:
>
> if (method=="INVITE"){
> if(!t_write_unix("/tmp/sems_sock","conference")){
> log("could not contact sems\n");
> t_reply("500","could not contact media server");
> }
>
> I have attached the modified ser-sems.cfg.
>
> Btw if you try sems trunk version, or a more recent snapshot (see eg here:
> http://ftp.iptel.org/pub/sems/testing/) you will find that this has become
> much easier now: for one, you can set application=conference in sems.conf,
> or define an application mapping regexp->application
> (see 'aplication' parameter explaoined in
> http://svn.berlios.de/wsvn/sems/trunk/core/etc/sems.conf.sample and
> example here
> http://svn.berlios.de/wsvn/sems/trunk/core/etc/app_mapping.conf), and
> second, sems has now an optional internal sip stack, so you don't need ser
> for it any more.
>
> Stefan
>
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems
