Hi Lars,
it took some time, but thanks to your details debug output I was able to
trace the problem and fix the bug. As I was expecting, in was in the
to/from parser.
Please update from CVS and give it a try.
Thanks again for the help,
bogdan
Lars Sundqvist wrote:
> I wish I could, but the INVITE's are not logged and I have not been
> able to reproduce the problem on the test system :-( so i realize this
> isn't very easy to "fix" I was mainly checking if this was a known
> problem.
>
> Version is 1.0.0-tls (disable_tls=0) compiled from source.
>
> uac is called like:
> uac_replace_from("SomeText: $avp(s:display)","")
>
> The INVITE was most likely produced by a "Aastra Intelligate" SIP UA
> since the particular customer has one of these registered right now.
>
> /Lasse
>
> Bogdan-Andrei Iancu wrote:
>
>> Hi Lars,
>>
>> can you please post the complete INVITE request that produces the
>> crash and how the uac_replace_from() function is called from script?
>> and what version are you using?
>>
>> regards,
>> bogdan
>>
>> Lars Sundqvist wrote:
>>
>>> I have switched from SER to OpenSER in our production enviroment
>>> since I
>>> need a few of the "new" modules, I am however having troubles with
>>> OpenSER hanging and crashing, so much so, that I had to change back.
>>>
>>> There is no clues in the logs to why this is happening but i have a
>>> coredump from a crash:
>>>
>>> (gdb) where
>>> #0 0x0052f7a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
>>> #1 0x005707d5 in raise () from /lib/tls/libc.so.6
>>> #2 0x00572149 in abort () from /lib/tls/libc.so.6
>>> #3 0x08054863 in del_lump (msg=0x0, offset=186, len=-135181242,
>>> type=HDR_OTHER_T) at data_lump.c:288
>>> #4 0x00f8bd20 in replace_from (msg=0x8130d98, from_dsp=0xbff977a0,
>>> from_uri=0x0) at from.c:207
>>> #5 0x00f8e57b in w_replace_from2 (msg=0x8130d98, dsp=0x812f700
>>> "\030W\022\b\v", uri=0x0) at uac.c:311
>>> #6 0x08051703 in do_action (a=0x8126658, msg=0x8130d98) at
>>> action.c:677
>>> #7 0x080529e3 in do_action (a=0x8126680, msg=0x8130d98) at
>>> action.c:773
>>> #8 0x0805297b in do_action (a=0x8126a58, msg=0x8130d98) at
>>> action.c:773
>>> #9 0x0805297b in do_action (a=0x8126f80, msg=0x8130d98) at
>>> action.c:773
>>> #10 0x0805297b in do_action (a=0x8127058, msg=0x8130d98) at
>>> action.c:773
>>> #11 0x0805297b in do_action (a=0x812b6d0, msg=0x8130d98) at
>>> action.c:773
>>> #12 0x080529e3 in do_action (a=0x812b6f8, msg=0x8130d98) at
>>> action.c:773
>>> #13 0x080529e3 in do_action (a=0x812b720, msg=0x8130d98) at
>>> action.c:773
>>> #14 0x0805297b in do_action (a=0x812b7f8, msg=0x8130d98) at
>>> action.c:773
>>> #15 0x08052b42 in run_actions (a=0x8122da0, msg=0x8130d98) at
>>> action.c:773
>>> #16 0x080753e9 in receive_msg (
>>> buf=0x80eb300 "INVITE sip:987654321@xxx.xxx.xxx SIP/2.0\r\nVia:
>>> SIP/2.0/UDP
>>> 192.168.0.17:5060;rport;branch=z9hG4bK0ffd9a6274aeb347617736a6da35e918\r\nTo:
>>>
>>> 987654321<sip:987654321@xxx.xxx.xxx>\r\nFrom: 123456789<si"...,
>>> len=943,
>>> rcv_info=0xbff98b80)
>>> at receive.c:160
>>> #17 0x0808dd1c in udp_rcv_loop () at udp_server.c:464
>>> #18 0x08064e7f in main_loop () at main.c:1033
>>> #19 0x08065615 in main (argc=3, argv=0xbff98d34) at main.c:1570
>>>
>>> (Numbers and sip domain edited)
>>> Anyone who has a clue whats going wrong?
>>>
>>> Lars Sundqvist
>>>
>>> _______________________________________________
>>> Users mailing list
>>> Users(a)openser.org
>>> http://openser.org/cgi-bin/mailman/listinfo/users
>>>
>>
>
Hi,
I am running everything on machines on the same private network. My softphone is on a windows machine with the local ip address 192.168.1.183, ser is on a Linux machine with the local ip address 192.168.1.147, and my friends softphone is on a windows machine with the local ip address 192.168.1.192.
And what I am trying to do is:
1. Having my softphone use 192.168.1.147 (the ser machine) as proxy.
2. Setting ser to forward a call to cooldude(a)company.se to 192.168.1.192 (my friend with a softphone)
Robert
-----Ursprungligt meddelande-----
Från: Ladislav Andel [mailto:ladia6@centrum.cz]
Skickat: den 25 januari 2006 13:51
Till: Robert Zettinger; serusers(a)lists.iptel.org
Ämne: Re: [Serusers] Setting up ser (configuring static forwarding)
Hi,
you should better tell us where is your SER running . Inside of private
network? public internet? Is your softphone
in the same private network as your friend's softphone?
Could you draw your network endpoints eg. SIP UA---(public
internet)---- SER --- (private network) --- your friend's SIP UA
If we know the location of your network entities then it would help us a
lot to understand what you are trying to do.
Ladislav
Robert Zettinger wrote:
>
> I have problems setting up Sip Express Router (SER). I have installed
> it, and it seems to run fine, and my softphone seems to able to
> connect to it. Just to see if it works, I want to set up ser to
> connect my softphone to my friend's (his IP is 192.168.1.192).
> Therefore I change the ser.cfg file to look like this:
>
> ----------
>
> #
> # $Id: ser.cfg,v 1.25.2.1 2005/02/18 14:30:44 andrei Exp $
> #
> # simple quick-start config script
> #
>
> # ----------- global configuration parameters ------------------------
>
> #debug=3 # debug level (cmd line: -dddddddddd)
> #fork=yes
> #log_stderror=no # (cmd line: -E)
>
> /* Uncomment these lines to enter debugging mode
> fork=no
> log_stderror=yes
> */
>
> check_via=no # (cmd. line: -v)
> dns=no # (cmd. line: -r)
> rev_dns=no # (cmd. line: -R)
> #port=5060
> #children=4
> fifo="/tmp/ser_fifo"
>
> # ------------------ module loading ----------------------------------
>
> # Uncomment this if you want to use SQL database
> #loadmodule "../usr/local/lib/ser/modules/mysql.so"
>
> loadmodule "../usr/local/lib/ser/modules/sl.so"
> loadmodule "../usr/local/lib/ser/modules/tm.so"
> loadmodule "../usr/local/lib/ser/modules/rr.so"
> loadmodule "../usr/local/lib/ser/modules/maxfwd.so"
> loadmodule "../usr/local/lib/ser/modules/usrloc.so"
> loadmodule "../usr/local/lib/ser/modules/registrar.so"
> loadmodule "../usr/local/lib/ser/modules/textops.so"
>
> # Uncomment this if you want digest authentication
> # mysql.so must be loaded !
> #loadmodule "../usr/local/lib/ser/modules/auth.so"
> #loadmodule "../usr/local/lib/ser/modules/auth_db.so"
>
> # ----------------- setting module-specific parameters ---------------
>
> # -- usrloc params --
>
> modparam("usrloc", "db_mode", 0)
>
> # Uncomment this if you want to use SQL database
> # for persistent storage and comment the previous line
> #modparam("usrloc", "db_mode", 2)
>
> # -- auth params --
> # Uncomment if you are using auth module
> #
> #modparam("auth_db", "calculate_ha1", yes)
> #
> # If you set "calculate_ha1" parameter to yes (which true in this
> config),
> # uncomment also the following parameter)
> #
> #modparam("auth_db", "password_column", "password")
>
> # -- rr params --
> # add value to ;lr param to make some broken UAs happy
> modparam("rr", "enable_full_lr", 1)
>
> # ------------------------- request routing logic -------------------
>
> # main routing logic
>
> route{
>
> # initial sanity checks -- messages with
> # max_forwards==0, or excessively long requests
> if (!mf_process_maxfwd_header("10")) {
> sl_send_reply("483","Too Many Hops");
> break;
> };
> if (msg:len >= 2048 ) {
> sl_send_reply("513", "Message too big");
> break;
> };
>
>
> # we record-route all messages -- to make sure that
> # subsequent messages will go through our proxy; that's
> # particularly good if upstream and downstream entities
> # use different transport protocol
> if (!method=="REGISTER") record_route();
>
> # subsequent messages withing a dialog should take the
> # path determined by record-routing
> if (loose_route()) {
> # mark routing logic in request
> append_hf("P-hint: rr-enforced\r\n");
> route(1);
> break;
> };
>
> if (uri=="sip:cooldude@company.se") {
> forward( 192.168.1.192, 5060);
> }
>
> if (!uri==myself) {
> # mark routing logic in request
> append_hf("P-hint: outbound\r\n");
> route(1);
> break;
> };
>
> # if the request is for other domain use UsrLoc
> # (in case, it does not work, use the following command
> # with proper names and addresses in it)
> if (uri==myself) {
>
> if (method=="REGISTER") {
>
> # Uncomment this if you want to use digest authentication
> # if (!www_authorize("iptel.org", "subscriber")) {
> # www_challenge("iptel.org", "0");
> # break;
> # };
>
> save("location");
> break;
> };
>
> lookup("aliases");
> if (!uri==myself) {
> append_hf("P-hint: outbound alias\r\n");
> route(1);
> break;
> };
>
> # native SIP destinations are handled using our USRLOC DB
> if (!lookup("location")) {
> sl_send_reply("404", "Not Found");
> break;
> };
> };
> append_hf("P-hint: usrloc applied\r\n");
> route(1);
> }
>
> route[1]
> {
> # send it out now; use stateful forwarding as it works reliably
> # even for UDP2TCP
> if (!t_relay()) {
> sl_reply_error();
> };
> }
>
>
> ----------
>
> Where
>
> if (uri=="sip:cooldude@company.se") {
> forward( 192.168.1.192, 5060);
> }
>
> is the only thing I have added to the original default config file
> that comes with the distribution. I now want to enter
> "sip:cooldude@company.se" in my softphone and get forwarded to
> 192.168.1.192. But nothing happens. Ideas?
>
>
>
> I am using Linux 2.4.18-14 and ser 0.9.6.
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Serusers mailing list
> serusers(a)lists.iptel.org
> http://lists.iptel.org/mailman/listinfo/serusers
>
Hi all!!!!
My openSER does not honour the add_username parameter of the rr module
and always insert the user part in the record route headers. Maybe it
is already corrected in the CVS...
I downloaded the next snapshot openser-1.0.0-cvs-13Jan.tgz and the
output from the -V is
version: openser 1.0.0 (i386/linux)
flags: STATS: Off, USE_IPV6, USE_TCP, DISABLE_NAGLE, USE_MCAST,
DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, F_MALLOC,
FAST_LOCK-ADAPTIVE_WAIT
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16,
MAX_URI_SIZE 1024, BUF_SIZE 65535
@(#) $Id: main.c,v 1.7 2005/10/28 14:55:23 klaus_darilion Exp $
main.c compiled on 16:28:45 Jan 16 2006 with gcc 3.3
Thanks a lot,
Sam.
I have problems setting up Sip Express Router (SER). I have installed
it, and it seems to run fine, and my softphone seems to able to connect
to it. Just to see if it works, I want to set up ser to connect my
softphone to my friend's (his IP is 192.168.1.192). Therefore I change
the ser.cfg file to look like this:
----------
#
# $Id: ser.cfg,v 1.25.2.1 2005/02/18 14:30:44 andrei Exp $
#
# simple quick-start config script
#
# ----------- global configuration parameters ------------------------
#debug=3 # debug level (cmd line: -dddddddddd)
#fork=yes
#log_stderror=no # (cmd line: -E)
/* Uncomment these lines to enter debugging mode
fork=no
log_stderror=yes
*/
check_via=no # (cmd. line: -v)
dns=no # (cmd. line: -r)
rev_dns=no # (cmd. line: -R)
#port=5060
#children=4
fifo="/tmp/ser_fifo"
# ------------------ module loading ----------------------------------
# Uncomment this if you want to use SQL database
#loadmodule "../usr/local/lib/ser/modules/mysql.so"
loadmodule "../usr/local/lib/ser/modules/sl.so"
loadmodule "../usr/local/lib/ser/modules/tm.so"
loadmodule "../usr/local/lib/ser/modules/rr.so"
loadmodule "../usr/local/lib/ser/modules/maxfwd.so"
loadmodule "../usr/local/lib/ser/modules/usrloc.so"
loadmodule "../usr/local/lib/ser/modules/registrar.so"
loadmodule "../usr/local/lib/ser/modules/textops.so"
# Uncomment this if you want digest authentication
# mysql.so must be loaded !
#loadmodule "../usr/local/lib/ser/modules/auth.so"
#loadmodule "../usr/local/lib/ser/modules/auth_db.so"
# ----------------- setting module-specific parameters ---------------
# -- usrloc params --
modparam("usrloc", "db_mode", 0)
# Uncomment this if you want to use SQL database
# for persistent storage and comment the previous line
#modparam("usrloc", "db_mode", 2)
# -- auth params --
# Uncomment if you are using auth module
#
#modparam("auth_db", "calculate_ha1", yes)
#
# If you set "calculate_ha1" parameter to yes (which true in this
config),
# uncomment also the following parameter)
#
#modparam("auth_db", "password_column", "password")
# -- rr params --
# add value to ;lr param to make some broken UAs happy
modparam("rr", "enable_full_lr", 1)
# ------------------------- request routing logic -------------------
# main routing logic
route{
# initial sanity checks -- messages with
# max_forwards==0, or excessively long requests
if (!mf_process_maxfwd_header("10")) {
sl_send_reply("483","Too Many Hops");
break;
};
if (msg:len >= 2048 ) {
sl_send_reply("513", "Message too big");
break;
};
# we record-route all messages -- to make sure that
# subsequent messages will go through our proxy; that's
# particularly good if upstream and downstream entities
# use different transport protocol
if (!method=="REGISTER") record_route();
# subsequent messages withing a dialog should take the
# path determined by record-routing
if (loose_route()) {
# mark routing logic in request
append_hf("P-hint: rr-enforced\r\n");
route(1);
break;
};
if (uri=="sip:cooldude@company.se") {
forward( 192.168.1.192, 5060);
}
if (!uri==myself) {
# mark routing logic in request
append_hf("P-hint: outbound\r\n");
route(1);
break;
};
# if the request is for other domain use UsrLoc
# (in case, it does not work, use the following command
# with proper names and addresses in it)
if (uri==myself) {
if (method=="REGISTER") {
# Uncomment this if you want to use digest authentication
# if (!www_authorize("iptel.org", "subscriber")) {
# www_challenge("iptel.org", "0");
# break;
# };
save("location");
break;
};
lookup("aliases");
if (!uri==myself) {
append_hf("P-hint: outbound alias\r\n");
route(1);
break;
};
# native SIP destinations are handled using our USRLOC DB
if (!lookup("location")) {
sl_send_reply("404", "Not Found");
break;
};
};
append_hf("P-hint: usrloc applied\r\n");
route(1);
}
route[1]
{
# send it out now; use stateful forwarding as it works reliably
# even for UDP2TCP
if (!t_relay()) {
sl_reply_error();
};
}
----------
Where
if (uri=="sip:cooldude@company.se") {
forward( 192.168.1.192, 5060);
}
is the only thing I have added to the original default config file that
comes with the distribution. I now want to enter
"sip:cooldude@company.se" in my softphone and get forwarded to
192.168.1.192. But nothing happens. Ideas?
I am using Linux 2.4.18-14 and ser 0.9.6.
Hi,
I'd like to have some ideas for the solution of this
problem: In OpenSer 1.0., when I use the function
uac_replace_from("","me(a)here.com") I'm getting the
following error:
Jan 24 15:19:59 server1
/usr/local/sbin/openser[22100]: BUG: del_lump: offset
+ len exceeds message size (79 + -135152687 > 946)
Jan 24 15:20:00 server1
/usr/local/sbin/openser[22084]: child process 22100
exited by a signal 6
Jan 24 15:20:00 server1
/usr/local/sbin/openser[22084]: core was generated
Jan 24 15:20:00 server1
/usr/local/sbin/openser[22084]: INFO: terminating due
to SIGCHLD
Thanks for your help. Best regards,
Humberto
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Hi all,
I have a ser(0.9.4/Freebsd) server well working, but in some cases, I have a
strang behavior. I use rtpproxy for nat traversal,all my users can call
pstn, but when we try to call one of our users from internal or from pstn,
Ser sends many invites and callee never answer to these invite. I must
conclude that they don't receive it... All the users having that problems
are under a nated network.
Any idea ?
Olivier
Has anyone successfully been able to set the "From"-field to the
original "To"-field after changing the r-uri to the forwarded
destination?
A calls B which forwards to C
Currently A is billed because that's the callerID that goes through.
I want to bill B.
-- Bjorn
Don't think so.
append_rpid_hf() maybe, but I haven't had any luck with it...
-----Original Message-----
From: Paul Hazlett [mailto:javarockx@gmail.com]
Sent: Tuesday, January 24, 2006 11:28 PM
To: Bjorn Asmul
Cc: seruser
Subject: Re: [Serusers] Billing - Call Forward
I'm not too familiar with the UAC module, but perhaps it will do the
trick.
Cheers,
Paul
On 1/24/06, Bjorn Asmul <bjorn(a)atlasvoice.com> wrote:
>
> Has anyone successfully been able to set the "From"-field to the
> original "To"-field after changing the r-uri to the forwarded
destination?
>
> A calls B which forwards to C
>
> Currently A is billed because that's the callerID that goes through.
> I want to bill B.
>
> -- Bjorn
> _______________________________________________
> Serusers mailing list
> serusers(a)lists.iptel.org
> http://lists.iptel.org/mailman/listinfo/serusers
>
>
>
Hi Jan,
I'd like to use PA, XCAP with eyeBeam.
Are you talking about the "ser-0.10.99-dev30-tm-timers-pa-3", I've
downloaded the tar file and tried "make install".
It seems like presence works fine, XCAP is also working(except RLS)...
About the RLS, do I need to create a directory in
"<xcap-root>/rls-services/global/index" where all the XML (for RLS)
files are stored?
How can I configure the eyeBeam accordingly? By default it's configured
as "subscribe to contact list : $username$-list@$domain$".
It seems like SER does not consider it as a list, it only considers it
just another URI. Did I do something wrong? Or do I need to change
anything in SER?
Regards,
Dennis
-----Original Message-----
From: Jan Janak [mailto:jan@iptel.org]
Sent: Tuesday, January 24, 2006 11:11 PM
To: Yeung OnTai-q16645
Cc: serusers(a)lists.iptel.org
Subject: Re: [Serusers] re : presence module with ser
On 18-01-2006 09:07, Yeung OnTai-q16645 wrote:
> Hi all,
>
> I need to build SER with presence and XCAP. Does anyone know which
> version of SER contain a relatively "stable" version of "pa" and
"rls".
> I've tried 0.9.6 and the cvs stable build, but I ran into different
> problems(error in loading modules, compling errors, etc) in making the
> source code.
>
> Can anyone point me to the right direction please?
Try the version from http://ftp.iptel.org/pub/ser/presence
That one should be relatively easy to build. Note that the XCAP server
is not included.
Jan.
>
> Thank you very much!
>
> Regards,
> Dennis
> _______________________________________________
> Serusers mailing list
> serusers(a)lists.iptel.org
> http://lists.iptel.org/mailman/listinfo/serusers