Hello:
I''m running SER 0.8.10 on FreeBSD 4.7. I'm trying to add an
alias for an existing user and I consistently get the error message
"400 Table 'aliases' Not Found". I was wondering what is causing
this error? Does anyone have any ideas?
Thanks,Steve
Att Sales
Due to problems with our current supplier of service the following are up for quotation, if you wish to be added to a contact list to supply service to our clients please send your details to daynaworldwide(a)aol.com
please quote for the following:
Do you have 2 day services Amsterdam - (airport) to Spain/Madrid Area,
weekly shipments for around 50 - 500 kgs, if yes please supply me with
rates.
++++++++
Sameday prices from EN11HA to G661XF -UK
+++++++++
We have imports to the USA and exports from Europe to the USA. Mostly boxed personal effects ahd household goods. Many of our sgents do not want vto handle residential pick up or deliveries and I am tired of begging them to handle it. can you quote?
A typical shipment is a pick up from Frankfurt to the warehouse at the Frankfurt Airport or something simiar in any of the European cities.
++++++++++
I need a quotation for a 20kg parcel, delivery from Exeter United
Kingdon to Powers Michigan United States.
+++++++++++
Prices needed a.s.a.p or customers will be lost
Kind Regards
Dayna
Dayna Worldwide
Maverick House
Beacon Road
Birmingham
B43 7BW UK
Tel 0044 (0)121 360 5954
Mobile 0044 (0)7817 456 399
Both Andrei and Daniel are right.
By default, mysql.so is not compiled and installed. If mysql.so is configured to loaded and mysql.so is not found in the library, a " bad config file" error will appear when ser is started. I did not see this error because I installed ser0.8.10 before and the obsolete mysql.so existed in the library.
Hello, I'm tring to compile ser-0.8.11pre29 using make all. I am running Redhat 8.0. The ser-0.8.11pre29.rpm install with no problem, but I noticed a posting that the generic install doesn't support mysql modules. So in a nutshell it make sense to compile from scratch making it easier to add patches in as the are built(ie...pre31). Below is the error message I'm gettin.
Extra objs:
gcc -Wl,-O2 -Wl,-E action.o crc.o data_lump.o data_lump_rpl.o dprint.o dset.o error.o fifo_server.o flags
.o forward.o hash_func.o ip_addr.o main.o md5.o md5utils.o modparam.o msg_translator.o pass_fd.o proxy.o rec
eive.o resolve.o route.o route_struct.o script_cb.o sr_module.o stats.o tcp_main.o tcp_read.o timer.o udp_se
rver.o mem/f_malloc.o mem/mem.o mem/memtest.o mem/q_malloc.o mem/shm_mem.o mem/vq_malloc.o parser/hf.o parse
r/msg_parser.o parser/parse_content.o parser/parse_cseq.o parser/parse_event.o parser/parse_expires.o parser
/parse_fline.o parser/parse_from.o parser/parse_hname2.o parser/parse_hostport.o parser/parse_nameaddr.o par
ser/parse_param.o parser/parser_f.o parser/parse_rr.o parser/parse_to.o parser/parse_uri.o parser/parse_via.
o parser/digest/digest.o parser/digest/digest_parser.o parser/digest/param_parser.o parser/contact/contact.o
parser/contact/parse_contact.o db/db.o lex.yy.o cfg.tab.o -lfl -ldl -lresolv -o ser
/usr/bin/ld: cannot find -lfl
collect2: ld returned 1 exit status
make: *** [ser] Error 1
Thanks Mike
Sorry, here is what I wanted to express in last letter.
Ser starts normally with the default ser.cfg. When I uncommented the line load module "/usr/local/lib/ser/modules/mysql.so" to load mysql.so, everything seems normally. But actually, ser stops abnormally.
Thanks!
Younger Wang
Hello All,
I have installed ser-0.8.11pre29-1 on RedHat 9.0. When I start ser by script
/etc/init.d/ser or directly using /usr/sbin/ser, the process SOMETIMES hangs
at the Aliases line show below. When I list the process table, I observed
there was a defunct process. Now, this does not happen ALL the time when I
starts ser. Sometime, /use/sbin/ser or init script will start fine without a
hiccup. I also notice that the defunct process is ALWAYS the second lowest
process id among all ser processes. Can this be a case of race condition for
the parent process to exit without waiting for the child?
I did not encounter this using ser-0.8.10 on RedHat 7.3. However, I do
remember encountering this behavior once when running ser-0.8.10 on RedHat
9.0, I have removed 0.8.10 and installed 0.8.11 since then for testing
0.8.11. Could this be a problem of RedHat 9.0? Is anyone experience this or
am I the only one?
[root@linux root]# /usr/sbin/ser
Listening on
192.168.1.100 [192.168.1.100]:5060
Aliases: some.where.org:5060 linux.some.where.org:5060
2071 pts/0 S 0:00 /usr/sbin/ser
2072 ? Z 0:00 [ser <defunct>]
2073 ? S 0:00 /usr/sbin/ser
2075 ? S 0:00 /usr/sbin/ser
2076 ? S 0:00 /usr/sbin/ser
2077 ? S 0:00 /usr/sbin/ser
2078 ? S 0:00 /usr/sbin/ser
2079 ? S 0:00 /usr/sbin/ser
Thanks for the great software guys.
Tsang Han Wong
Got another oddity at the same site as before. This morning, th proxy
server appears to have simply stopped processing INVITE requests. It
continued to process and log REGISTER requests. The ngrep process I
have running to log traffic shows the inbound INVITE request, but
nothing after it, no response, no additional INVITE, nothing.
Again, I have ngrep traffic logs for the period if they would help.
Although I have not yet increased the debug level on the process. Was
hoping something would come of the information I forwarded to serhelp
first. However, I'll be increasing the logging level tonight.
Other ideas?
--
Jamin W. Collins
Remember, root always has a loaded gun. Don't run around with it unless
you absolutely need it. -- Vineet Kumar
I've just committed into the cvs the autopinging feature useful to
keep NAT bindings alive. If possible, please test and let me know
then. Basically, everything you need to do is to recompile/reinstall
ser and all modules and add the following into your config:
modparam("nathelper", "natping_interval", N)
Where N is some non-zero interval in seconds (usually 15-30 should
be OK).
Thanks!
-Maxim
On Tue, Apr 29, 2003 at 09:38:44PM +0100, jaime(a)umtstrial.co.uk wrote:
> Hello Maxim,
>
> I have been trying your module on one server with a customised
> configuration, very similar to the default one in nathelper.cfg. Actually,
> I'm trying to connect through a NAT to a server running SER with the
> nathelper module. The overall configuration looks like this:
>
> UA1 --- NAT --- SER (proxy and registrar)
> UA2 |
>
> UA1 and UA2 must traverse a NAT in order to reach SER. The NAT does not
> have port forwarding whatsoever.
>
> I was trying to see what happens to REGISTER, SUBSCRIBE, MESSAGE and
> INVITE messages. The nathelper adds rport and received to the Via field,
> so any response from the server gets routed correctly to the appropriate
> destination (that is, the NAT external interface).
>
> REGISTER's Contact is stored at registration and the 200 OK reaches the
> initiating client through the NAT.
>
> However, any other SIP message involving a database lookup into "location"
> will try to relay the message to the natted client, which is not reachable
> from the SER proxy (see diagram above). I think this could work if in
> location table you stored the "received" and "rport" values instead of the
> "Contact" field received when regitering (if that does not go against
> standards...). Then, just keep alive the NAT binding somehow (I think you
> where mentioning it in a previous email).
>
> Does this sound resonable? Making this scenario work would allow people at
> home with simple NAT's to use a public proxy (like Iptel's) and its
> services (Instant Messaging and Presence mainly)...
>
> Jaime
>
>
>