Thanks a lot. It seems that the log line
> 5(391) authorize(): Invalid nonce value received, very suspicious !
is the key -- Jan will probably handle that better than myself.
Are you sure you applied the solaris/digest patch?
(See nonce validation in ISSUES on SER's website. See also
the topmost solaris-specific issue -- better take SER sources
and recompile them without DBG_QM_MALLOC in Makefile.defs)
If things don't work then, send me please captured SIP messages too.
(Use tools like "ngrep port 5060" to record them.)
Thanks,
-Jiri
Hi,
A bit offtopic perhaps, but are there any good win32 sip ua's out there?
I'm interested in both commercial and opensource software (my friends
doesn't seem to whant to buy Cisco 7960's ... wonder why :)
/ Tomas
This is probably a very simple question. I'm trying to create a very
simplistic configuration that simply forwards the call to one of two
fixed destinations. Essentially, it forwards all calls to server A and
if that fails, forwards the call to server B. Forwarding to server A is
no problem. Within route, I simply have:
if (!mf_process_maxfwd_header("10")) {
sl_send_reply("483","Too Many Hops");
break;
};
if (len_gt( max_len )) {
sl_send_reply("513", "Message too big");
break;
};
rewriteFromRoute();
if (!forward("192.168.1.1")) {
sl_reply_error();
};
This works perfectly, but only forwards to one server. I tried changing
the last bit to:
if (!forward("192.168.1.1")) {
if (!forward("192.168.0.1")) {
sl_reply_error();
};
};
However, this results in "ERROR: bad config file (5 errors)".
Any suggestions? Is something like this possible?
--
Jamin W. Collins
Dear Jiri,
I have successfully compile the acc.so with SQL support.
And I run a number of testing on it.
It seems works fine but I encounter the following error which crach the ser.
===========================================================
[root@md benny]# 0(3545) mod_init(): Database connection opened successfuly
Maxfwd module- initializing
rr - initializing
acc - initializing
stateless - initializing
mysql - initializing
0(0) INFO: udp_init: SO_RCVBUF is initially 65535
0(0) INFO: udp_init: SO_RCVBUF is finally 131070
0(0) INFO: udp_init: SO_RCVBUF is initially 65535
0(0) INFO: udp_init: SO_RCVBUF is finally 131070
9(3565) INFO: fifo process starting: 3565
9(3565) SER: open_uac_fifo: fifo server up at /tmp/ser_fifo...
10(3574) ACC: transaction answered: method=INVITE,
i-uri=sip:1000@md.com;user=ph
one, o-uri=sip:1000@192.168.10.18:5000;user=phone, call_id=
426a69eafe94e7923666
1278d86d5024(a)192.168.10.18, from=
UserAgent-1<sip:1000@192.168.10.18:5000;user=p
hone>, code=408
10(3574) use_table(): Invalid parameter value
0(3545) child process 3574 exited by a signal 11
0(3545) core was not generated
0(3545) INFO: terminating due to SIGCHLD
=========================================================================
It seems to be a crash on use_table() when code=408,
I tried to unanswer to call or call to itself, and this problem generated.
Benny
-----Original Message-----
From: Jiri Kuthan [mailto:jiri@iptel.org]
Sent: Monday, February 24, 2003 6:30 PM
To: Benny Ho
Subject: RE: [Serusers] problem in using acc.so and radius_acc.so and
auth.so
First of all, note well:
http://lists.iptel.org/pipermail/serusers/2003-February/000493.html
At 04:36 AM 2/24/2003, Benny Ho wrote:
>Could you tell me how to enable SQL_ACC def? and setting teh db_url
>parameter?
uncomment the "#DEFS+=-DSQL_ACC" line in modules/acc/Makefile
>I cannot find any doc for mysql modules.
mysql module is not used from ser scripts directly -- modules which
rely on mysql use it internally. acc w/mysql has not been released
yet, it is work in progress on CVS and it has not been documented.
-jiri
I'm currently working with SNOM to get this issue
fixed. I'll report when I know something. It might
not hurt if someone else reported it to them!
---greg
Greg Fausak
>
>At 09:34 PM 2/24/2003, Jamin W. Collins wrote:
>>On Mon, Feb 24, 2003 at 08:54:00PM +0100, Jiri Kuthan wrote:
>>> What is CIC?
>>
>>A PBX made by I3 (www.inin.com)
>>
>>> Send us network dumps please -- that will make it easier to understand
>>> for us. You can for example use "ngrep port 5060".
>>
>>Network dump from the SER server is attached.
>
>snom phone is a common suspect again.
>
>The first signaling transaction looks ok. The only unusual thing is that
>for some reason, the ININ server advertises 192.168.0.9 as media receiver
>whereas its signaling lives at 192.168.1.16. Is media decomposed?
>
>The really suspicious is the second transaction. The snom phone sitting
>at .36 advertises contacts with .34 in its replies. That makes the
>caller (ININ) to send an ACK to .34. Snom does not received it and
>keeps soliciting it by retransmitting 200s.
>
>-Jiri
>
>_______________________________________________
>Serusers mailing list
>serusers(a)lists.iptel.org
>http://lists.iptel.org/mailman/listinfo/serusers
>
Hi,
I've been looking at ser for a couple of days now and there some things I
can't find in the documentation.
.1. Logging funktionality
I'm used to being able to log more detail than what I can get out
ser. I'm problably missing something in the documentation, but
what I want is something like the following
timestamp ser[pid] Incoming packet from ip:port
[dump of packet (only the sip header/body)]
timestamp ser[pid] Invite from [] to []
timestamp ser[pid] After rewrite: from [] to []
timestamp ser[pid] Relaying packet to [pstn-gw/other sip server]
/
timestamp ser[pid] Handling request for local user []
Can you send arguments to the log() function in the configuration
file for example log(1,"Call from %s", uri:from); ??
.2. Rewrite rules
Is it possible to rewrite the from uri?
For example when I [sip:tomas@krixor.xy.org] want to call a pstn
number I must rewrite the from address to
[sip:myphonenumber@krixor.xy.org] before I send the request to
the pstn gateway
And when a incoming call comes from the pstn gateway I want to
rewrite the from address from [<sip:number@ip-of-pstn-gateway>]
to {"PSTN Luser" <sip:number@pstn-gw.mydomain.com>]
I haven't looked at the source in the CVS yet, but I aim to do so soon, I
saw in the list archive that you have lots of nice new features planned
for the next release. ENUM support is one of the better ones :)
Anyway, looking forward to trying to help with the development of this
software.
Best regards,
Thomas Björklund
Folks,
I need an advise on how to better implement one feature, which isn't
currently present in SER. We need to allow UAs behind NAT properly
register with the registrar - by "properly" I mean that host:port portion
of URI in Contact field should not be used, but host:port the request
came from should be used instead. By definition we know that those UAs
will support symmetric SIP signalling, so that this scheme will work just
fine.
In my opinion there are two ways to do it: either add new rewritecontact*
family of functions similar to rewritehost ones. or add a new flag for
the save() function. This is where I need your help - which implementation
looks better for you (or maybe you have even some better idea), since
we are really interested in inclusion of our changes into the mainline to
reduce our local hacks.
Regards,
Maxim
Folks,
Attached please find several patches for ser 0.8.10. They do the following:
1. Removes hardcoded `/usr/local' from Makefiles and replaces it with
LOCALBASE variable setable in the top Makefile.defs. This should make
life of packagers easier.
2. Allows to override PREFIX variable with something else from environment.
3. Adds support for FreeBSD doc/man directories layout.
4. Adds some missed -I's into radius modules.
5. Fixes radius modules to use the same symbolic avp names as in dictionary.
6. Adds support for recording source port in msg structure and adds it
in "Noisy feedback". This should be extremely useful for debugging various
SIP&NAT scenarios and later could be re-used to implement `rport' support
described in my previous message.
It would be nice to have those patches integrated into the next release.
Thanks!
-Maxim