o Jawad hussain [09/10/09 14:03]:
Thanks,
So how to parse multiple parameters to SEMS like if a bind application 1
to SIP uri starting with 111 and bind application 2 with 112 with
udp_relay as udp_relay take (IP,Port) i.e. multiple application
execution controlling from SER to SEMS.
see application=... in sems.conf:
# optional parameter: application
#
# This controls which application is to be executed if there
# is no explicit application requested from the SIP stack
# (i.e. unixsockctrl and second parameter of t_write_unix).
#
# This can be one of
# $(ruri.user) - user part of ruri is taken as application,
# e.g. sip:announcem...@host
# $(ruri.param) - uri parameter "app", e.g.
# sip:[email protected];app=announcement
# $(apphdr) - the value of the P-App-Name header is used
#
# $(mapping) - regex=>application mapping is read from
# app_mapping.conf (see app_mapping.conf)
# <application name> - application name configured here, e.g.
# application=announcement
#
# examples:
# application = conference
# application = $(mapping)
# application = $(ruri.user)
# application = $(ruri.param)
application = $(apphdr)
BR
Stefan
Regards,
Jawad Hussain
On Thu, Sep 10, 2009 at 1:06 PM, Stefan Sayer <[email protected]
<mailto:[email protected]>> wrote:
Hello,
if you use a newer version of SEMS (1.1.1 or 1.0.1) you don't need
t_write_unix in SER, and you don't have socket_name/ser_socket_name
in sems.conf. Instead of t_write_unix in ser.cfg do
t_relay_to_udp("127.0.0.1","5070"), which will send the message to
SEMS over UDP.
SEMS has its own SIP stack and listens on a port, by default its
port 5070 (I think, have a look in sems.conf).
Regards
Stefan
o Jawad hussain [09/10/09 12:55]:
Thanks stefan,
So what I understand is in my SEMS config one is socket_name and
other is ser_socket_name and in my ser.cfg there is unix_socket
whose value is eval to SEMS ser socket and there is also a
function t_write_unix who is writing to sems socket. So if i set
t_relay_to_udp=127.0.0.1:5070 <http://127.0.0.1:5070>
<http://127.0.0.1:5070> in SEMS.cong then what other paramaters
chages in SER like t_write_unix = ? because ser errors saying
t_write_unix failed to write no such file or directory (however
the is a file).
Can you please elaborate little more.
Waiting for your reply.
Regards,
Jawad Hussain
Means that in my ser.cfg my
On Thu, Sep 10, 2009 at 12:33 PM, Stefan Sayer
<[email protected] <mailto:[email protected]>
<mailto:[email protected]
<mailto:[email protected]>>> wrote:
Hello Jawad,
o Jawad hussain [09/09/09 18:16]:
Hi,
I an trying to integrate SER-SEMS with OpenIMSCore but my
ser.cfg unix/fifo are giving errors so can you help are there
any special note for unix sockets. I am using ser 0.10
and SEMS
the latest one.
for the latest SEMS you don't need to use unix socket. Just
t_relay_to_udp to the host:port where SEMS is listening (see
sip_port in sems.conf).
hth
Stefan
-- Stefan Sayer
VoIP Services
[email protected] <mailto:[email protected]>
<mailto:[email protected] <mailto:[email protected]>>
www.iptego.com <http://www.iptego.com> <http://www.iptego.com>
IPTEGO GmbH
Wittenbergplatz 1
10789 Berlin
Germany
Amtsgericht Charlottenburg, HRB 101010
Geschaeftsfuehrer: Alexander Hoffmann
--
Stefan Sayer
VoIP Services
[email protected] <mailto:[email protected]>
www.iptego.com <http://www.iptego.com>
IPTEGO GmbH
Wittenbergplatz 1
10789 Berlin
Germany
Amtsgericht Charlottenburg, HRB 101010
Geschaeftsfuehrer: Alexander Hoffmann
--
Regards
Jawad Hussain
MS Internetworking
CCNA,JNCIA-ER
------------------------------------------------------------------------
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems
--
Stefan Sayer
VoIP Services
[email protected]
www.iptego.com
IPTEGO GmbH
Wittenbergplatz 1
10789 Berlin
Germany
Amtsgericht Charlottenburg, HRB 101010
Geschaeftsfuehrer: Alexander Hoffmann
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems
