8 Dec
2006
8 Dec
'06
9:17 a.m.
Hello Hendrik,
I was reading your post and wondering if you have made any progress on SER
monitoring? Especially in regard to enhancing the snmpd to monitor the
number of users and transactions?
http://lists.iptel.org/pipermail/serusers/2006-January/026771.html
Hello Hendrik,
What about VRRP for failover ?
SER1 (master)
sip agents == || === Asterisk Farm==sip/pstn gateway
SER2 (slave)
Harry
--- Hendrik Scholz <hendrik.scholz at freenet-ag.de
<http://lists.iptel.org/mailman/listinfo/serusers> > a
écrit :
Peter Kuebler
Director Network Reliability
tele: 703-636-1114
ext: 112
tele: 703-734-4112(alt)
cell: 240-506-5703
SunRocket
8045 Leesburg Pike, Suite 300
Vienna, VA 22182
peter.kuebler(a)sunrocket.com
SunRocket NOC 703-637-9970
Hi!
hgaillac-sip at yahoo.fr
<http://lists.iptel.org/mailman/listinfo/serusers>
wrote:
Yes I know
about snmp module.
There is no way to monitor SER vi snmp !?
As others have noted SER does not directly support
SNMP but you can
easily enhance your snmpd to support it.
You add serctl fifo commands using the snmp exec
directive
to monitor the number of users, transactions stuff,
...
The meminfo patch (now included) is handy and you
can directly pipe
serctl fifo meminfo into SNMP and create nifty
graphs.
sipsak comes in handy, i.e. sending an OPTIONS
request and measuring
a) if a response comes back and b) the time
processing took.
Much better would be monitoring INVITE/REGISTER
response behaviour since
that usually requires a whole lot more interaction
(radius, db, ..)
on SER side.
Hendrik
11 Dec
11 Dec
11:21 a.m.
New subject: [Serusers] SIPSAK - wrong behaviour??
Hi ALL!
I am trying to run some tests under sipsak but I obtain strange result
I invoke sip stack with the following command:
sipsak -IU -vv -s sip:sipsak@scscf.ims.touk.pl -a sipsak -l 5061 -H 192.168.0.129
The registration proces runs without any problem, user registers and then sipsak sends
invite to ser.
And here comes the strange thing
1. sipsak sends invite to ser:
2. Ser sends the proxy authentication required response 407 (from ngrep)
3. sipsak receives the message andresponses with the ACK????
Ive placed the ngrep from the sipsak socket in the attached file.
Please help mewith this one!
Best Tomasz
1:12 p.m.
New subject: [Serusers] SIPSAK - wrong behaviour??
Hi Tomasz,
On Monday 11 December 2006 17:21, tzieleniewski wrote:
Hi ALL!
I am trying to run some tests under sipsak but I obtain strange result
I invoke sip stack with the following command:
sipsak -IU -vv -s sip:sipsak@scscf.ims.touk.pl -a sipsak -l 5061 -H
192.168.0.129 The registration proces runs without any problem, user
registers and then sipsak sends invite to ser. And here comes the strange
thing
1. sipsak sends invite to ser:
2. Ser sends the proxy authentication required response 407 (from ngrep)
3. sipsak receives the message andresponses with the ACK????
Ive placed the ngrep from the sipsak socket in the attached file.
that looks like a bug. I'll try to look into that later.
It would be great if you could try if the same behavior is still present in
the latest version from subversion (let me know if I should send you a
tarball of that). And the output from sipsak with -vvv would be a great help.
Just send that directly to me.
Thanks
Nils
2:59 p.m.
New subject: [Serusers] SIPSAK - wrong behaviour??
I was just curious, so I took look on the ngrep....
there is short jump in the description between points 2 and 3....
2a. sipsak sends ACK upon 407 reply, which is 100% correct
2b. sipsak resends INVITE with correct credentials
2c. ser forwards the INVITE to the sipsak @ port 5060
3. sipsak sends ACK (with the CSeq: 3, Via: headers look like
combination of original ACK and passed INVITE Vias), which you've found
inappropriate, right? Just to make sure we talk about the same ACK :-D
Michal
On Mon, 2006-12-11 at 19:12 +0100, Nils Ohlmeier wrote:
Hi Tomasz,
On Monday 11 December 2006 17:21, tzieleniewski wrote:
Hi ALL!
I am trying to run some tests under sipsak but I obtain strange result
I invoke sip stack with the following command:
sipsak -IU -vv -s sip:sipsak@scscf.ims.touk.pl -a sipsak -l 5061 -H
192.168.0.129 The registration proces runs without any problem, user
registers and then sipsak sends invite to ser. And here comes the strange
thing
1. sipsak sends invite to ser:
2. Ser sends the proxy authentication required response 407 (from ngrep)
3. sipsak receives the message andresponses with the ACK????
Ive placed the ngrep from the sipsak socket in the attached file.
that looks like a bug. I'll try to look into that later.
It would be great if you could try if the same behavior is still present in
the latest version from subversion (let me know if I should send you a
tarball of that). And the output from sipsak with -vvv would be a great help.
Just send that directly to me.
Thanks
Nils
_______________________________________________
Serusers mailing list
Serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
6412
days inactive
6415
days old
3 comments
4 participants
participants (4)
-
"tzieleniewski" -
Michal Matyska -
Nils Ohlmeier -
Peter Kuebler