Is anyone using any of the Ovislink PSTN gateways (eLive 400/800) with
SER?
The products specs state support for H.323 and SIP. Like many products
it means that the unit supports only H.323, and you need to download new
firmware which replaces H.323 with SIP. I'm new to SIP in general, and
haven't got a working configuration yet.
How is PSTN gateway security supposed to work? I see in the manual
there is an example using SER to protect a "simple" gateway. Ovislink
definitely fits into that category. I guess that means that I need to put
ACLs on the router to make sure that all SIP traffic to the gateway is
blocked except from the SER server. How do better gateways implement
security?
Any nice PSTN gateways around that anyone can recommend for use? I'm
looking at Cisco, which seems like a lot of people use. I've looked at
Patton and Vegastream too. Neither of these companies has a 8 port POTS
PSTN gateway though.
Tom
Hi!
I only want to set up a sip server to let people here in my city register and have a sip adress like iptel.org do , the simplest setup possible.
I have a dyn domain (sipserver.com.br) that i want to use to do that...and i have a dynamic ip. The ser machine will be behind a nat wit an ix66.
Some one can give a way on how to set up it?
I can make it with the basic ser.conf and ser web?
I need some extras?
Thanks for all
Claudio
Hi,
I have encountering this problem when I try to run voicemail.cfg coding. May
I know what is going wrong and how to know that sems is running and how to
start? I have tried /usr/local/sbin/sems -f (config file) I encountered
errors, is this the way to start the service.....please help....
Mar 24 19:04:25 sipserver2 /usr/local/sbin/ser[12876]: ERROR: voicemail:
ans_machine deamon is not running !
Mar 24 19:04:25 sipserver2 /usr/local/sbin/ser[12876]: ERROR: voicemail: No
such device or address
Mar 24 19:04:25 sipserver2 /usr/local/sbin/ser[12876]: ERROR: vm_start:
write_to_fifo failed
Mar 24 19:04:35 sipserver2 /usr/local/sbin/ser[12874]: ERROR: voicemail:
ans_machine deamon is not running !
Mar 24 19:04:35 sipserver2 /usr/local/sbin/ser[12874]: ERROR: voicemail: No
such device or address
Mar 24 19:04:35 sipserver2 /usr/local/sbin/ser[12874]: ERROR: vm_start:
write_to_fifo failed
Regards,
shirley
I installed the radiusclient 0.4.1, and ran into a slight problem.
I run ldconfig -v /usr/local/lib and the following is output:
/usr/local/lib:
libradiusclient.so.2 -> libradiusclient.so.2.0.0
Here is the directory of /usr/local/lib
-rw-r--r-- 1 root root 130780 Mar 18 12:37 libradiusclient.a
-rwxr-xr-x 1 root root 853 Mar 18 12:37 libradiusclient.la
lrwxrwxrwx 1 root root 24 Mar 18 12:37 libradiusclient.so ->
libradiusclient.so.2.0.0
lrwxrwxrwx 1 root root 24 Mar 18 12:37 libradiusclient.so.2 ->
libradiusclient.so.2.0.0
-rwxr-xr-x 1 root root 95088 Mar 18 12:37 libradiusclient.so.2.0.0
Ldconfig will not process the libradiusclient.so because it is a symbolic
link. So when I run "ser -ddddddddd start" I get the following:
0(7710) ERROR: load_module: could not open module
</usr/lib/ser/modules/auth_radius.so>: libradiusclient.so.0: cannot open
shared object file: No such file or directory
Ser can't locate the reference for libradiusclient.so.0 since ldconfig won't
process the link libradius.so.0. Any ideas of getting around this. I
checked the man pages for ldconfig, and it states it does not process
symbolic links:
"ldconfig ignores symbolic links when scanning for libraries."
Scott Morris
Enterprise Network Engineer
DOE - ORAU / ORISE
865-576-4672
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
hey guys,
Anyone had problems with the IVR module, that sems gets a signal 17, and
kills itself?
if you check line 72 .. there's only a check if a signal is received.
This only happens with the IVR module.
- Atle
1 Sems[9658]: Warning: signal 17 received
(9976) DEBUG: run (AmServer.cpp:172): version= <0.2>
(9976) DEBUG: run (AmServer.cpp:182): fct_name= <sip_request.bye>
(9976) DEBUG: execute (AmServer.cpp:240): cmd.method= <BYE>
(9976) DEBUG: execute (AmServer.cpp:241): cmd.user= <73939>
(9976) DEBUG: execute (AmServer.cpp:242): cmd.email= <>
(9976) DEBUG: execute (AmServer.cpp:243): cmd.domain= <>
(9976) DEBUG: execute (AmServer.cpp:244): cmd.dstip= <192.168.0.2>
(9976) DEBUG: execute (AmServer.cpp:245): cmd.port= <>
(9976) DEBUG: execute (AmServer.cpp:246): cmd.r_uri=
<sip:73939@192.168.0.3:5060>
(9976) DEBUG: execute (AmServer.cpp:247): cmd.from_uri=
<sip:73945@i192.168.0.4>
(9975) WARNING: sig_usr (sems.cpp:72): signal 17 received
(9975) INFO: sig_usr (sems.cpp:81): finished
Hi,
I'd like to use official phone numbers inside my voip network (the
numbers are assigned to me and are routed to my Cisco-5300 gateway in
case of an incoming call from PSTN), and I don't want to use a prefix
when calling from voip to PSTN.
Now when I want to perform a call from the voip net, how can I decide
wether it's an internal voip call or should be routed to the PSTN gateway?
Would it be a proper solution to just lookup in the aliases- and
location-table, and, if not found there, just forward it to the PSTN
gateway? The PSTN gateway should then route it back to my SER if it's a
number assigned to me, and I'd get a loop, which should be detected by
the mf_process_maxfwd_header() function.
Sounds like a ugly hack, and I'm really not shure if this would work, so
how would be the standard solution for such a task? (beside using a PSTN
prefix)
Regards,
Andy
Hey guys. Anybody had a problem with that sems is reading a wavefile to
quick when you use the announcement module?
It's not chopping anything, it just echo\s the sound REALLY quick out to
the caller who hit the announcement
- Atle
Hi,
I understand what you are saying, but I have had two specific events with
all of the bindings expiring at once, and ser doesn't seem to be processing
new register requests from 20 different devices. Then the phones become
useless. This has only happened two times but it has not happened in the
past week.
Mar 16 12:30:41 jiffypop /usr/local/sbin/ser[5255]: Binding
'bshamah','sip:bshamah@10.10.10.118:5060;transport=udp' has expired
Mar 16 12:30:42 jiffypop /usr/local/sbin/ser[5255]: Binding
'nmistry','sip:nmistry@10.10.10.95:5060;transport=udp' has expired
Mar 16 12:30:43 jiffypop /usr/local/sbin/ser[5255]: Binding
'gnoah','sip:gnoah@10.10.10.95:5060;transport=udp' has expired
Mar 16 12:30:44 jiffypop /usr/local/sbin/ser[5255]: Binding
'benm','sip:Benm@10.10.10.181:11793' has expired
Mar 16 12:30:44 jiffypop /usr/local/sbin/ser[5255]: Binding
'conference1','sip:conference1@10.10.10.199:5060;transport=udp' has expired
Mar 16 12:30:45 jiffypop /usr/local/sbin/ser[5255]: Binding
'conference2','sip:conference2@10.10.10.199:5060;transport=udp' has expired
Mar 16 12:30:45 jiffypop /usr/local/sbin/ser[5255]: Binding
'jwagner','sip:jwagner@10.10.10.118:5060;transport=udp' has expired
Mar 16 12:31:48 jiffypop /usr/local/sbin/ser[5255]: Binding
'mdeguzman','sip:mdeguzman@10.10.10.183:5060;transport=udp' has expired
Mar 16 12:31:49 jiffypop /usr/local/sbin/ser[5255]: Binding
'erollins','sip:erollins@10.10.10.130:5060;transport=udp' has expired
Mar 16 12:31:49 jiffypop /usr/local/sbin/ser[5255]: Binding
'sgaudio','sip:sgaudio@10.10.10.130:5060;transport=udp' has expired
Mar 16 12:31:50 jiffypop /usr/local/sbin/ser[5255]: Binding
'benm','sip:benm@10.10.10.183:5060;transport=udp' has expired
Mar 16 12:31:51 jiffypop /usr/local/sbin/ser[5255]: Binding
'rhollowell','sip:rhollowell@10.10.10.176:5060' has expired
Mar 16 12:32:54 jiffypop /usr/local/sbin/ser[5255]: Binding
'rsandler','sip:rsandler@10.10.10.182:5060' has expired
Mar 16 12:32:55 jiffypop /usr/local/sbin/ser[5255]: Binding
'ewest','sip:ewest@10.10.10.154:5060' has expired
Mar 16 12:33:58 jiffypop /usr/local/sbin/ser[5255]: Binding
'fax1','sip:fax1@10.10.10.108:5060;transport=udp' has expired
Mar 16 12:33:58 jiffypop /usr/local/sbin/ser[5255]: Binding
'fax2','sip:fax2@10.10.10.108:5060;transport=udp' has expired
Mar 16 12:33:59 jiffypop /usr/local/sbin/ser[5255]: Binding
'pkong','sip:pkong@10.10.10.184:5060' has expired
Mar 16 12:36:05 jiffypop /usr/local/sbin/ser[5255]: Binding
'm1','sip:m1@10.10.10.252:5060;transport=udp' has expired
Mar 16 12:36:05 jiffypop /usr/local/sbin/ser[5255]: Binding
'm2','sip:m2@10.10.10.252:5060;transport=udp' has expired
Mar 16 12:36:06 jiffypop /usr/local/sbin/ser[5255]: Binding
'bkern','sip:10.10.10.195:9245' has expired
Mar 16 12:37:09 jiffypop /usr/local/sbin/ser[5255]: Binding
'gnoah','sip:gnoah@10.10.10.95:5060;transport=udp' has expired
Mar 16 12:37:09 jiffypop /usr/local/sbin/ser[5255]: Binding
'jnorwood','sip:jnorwood@10.10.10.102:5060' has expired
Mar 16 12:37:10 jiffypop /usr/local/sbin/ser[5255]: Binding
'jlin','sip:jlin@223.1.1.128:5060' has expired
Mar 16 12:38:13 jiffypop /usr/local/sbin/ser[5255]: Binding
'info','sip:info@10.10.10.137:5060' has expired
Mar 16 12:38:14 jiffypop /usr/local/sbin/ser[5255]: Binding
'nmistry','sip:nmistry@10.10.10.95:5060;transport=udp' has expired
>From: Jiri Kuthan <jiri(a)iptel.org>
>To: "goddess hekate" <goddess_hekate(a)hotmail.com>, serusers(a)lists.iptel.org
>Subject: Re: [Serusers] issues with bindings
>Date: Tue, 23 Mar 2004 00:55:04 +0100
>
>At 12:47 AM 3/23/2004, goddess hekate wrote:
> >Hello,
> >
> >Two times in the past week I have had some issues with the bindings of
>the sip mapping expiring:
> >
> >Binding 'user','sip:user@x.x.x.x:5060' has expired
> >
> >Does anyone know what this is and why it happens?
>
>Because it is not refreshed. Bindings are sof-state -- if not refreshed by
>new REGISTERs they will go.
>
>-jiri
>
> > I appreciate any input you may have.
> >
> >Thanks,
> >
> >Hekate
> >
> >_________________________________________________________________
> >All the action. All the drama. Get NCAA hoops coverage at MSN Sports by
>ESPN. http://msn.espn.go.com/index.html?partnersite=espn
> >
> >_______________________________________________
> >Serusers mailing list
> >serusers(a)lists.iptel.org
> >http://lists.iptel.org/mailman/listinfo/serusers
>
>--
>Jiri Kuthan http://iptel.org/~jiri/
>
_________________________________________________________________
Get rid of annoying pop-up ads with the new MSN Toolbar FREE!
http://toolbar.msn.com/go/onm00200414ave/direct/01/
Hi,
I compiled SER ... on a RedHat 9.0
I call /usr/local/sbin/ser from my /etc/rc.local file ...
But It doesn't work at boot time ...
Could any one send me a valid /etc/init.d/ser file, please ...
I am also stoping SER with kill -9 <pid>
Is that wrong?
