6 Dec
2007
6 Dec
'07
4:12 p.m.
Hi all,
I'm using the latest trunk version of openser.
When I start the proxy I see on debug this messages repeated forever...
I'm using a config file that worked well wiht openser release 1.2.2.
Dec 6 15:55:14 [28924] DBG:core:qm_free: params(0x817ada0, 0x81caa24),
called from nathelper.c: nh_timer(2941)
Dec 6 15:55:14 [28924] DBG:core:qm_free: freeing frag. 0x81caa0c alloc'ed
from nathelper.c: nh_timer(2841)
Dec 6 15:55:15 [28924] DBG:core:qm_malloc: params (0x817ada0, 8), called
from nathelper.c: nh_timer(2841)
Dec 6 15:55:15 [28924] DBG:core:qm_malloc: params (0x817ada0, 8), returns
address 0x81caa24 frag. 0x81caa0c (size=8) on 1 -th hit
Can you help me?
what does it mean?
Regards,
daniel
--
Daniel Grotti
________________________
e-mail : d.grotti(a)gmail.com
6 Dec
6 Dec
4:27 p.m.
On Thursday 06 December 2007, Daniel wrote:
I'm using the latest trunk version of openser.
When I start the proxy I see on debug this messages repeated forever...
I'm using a config file that worked well wiht openser release 1.2.2.
Dec 6 15:55:14 [28924] DBG:core:qm_free: params(0x817ada0, 0x81caa24),
called from nathelper.c: nh_timer(2941)
Dec 6 15:55:14 [28924] DBG:core:qm_free: freeing frag. 0x81caa0c alloc'ed
from nathelper.c: nh_timer(2841)
Dec 6 15:55:15 [28924] DBG:core:qm_malloc: params (0x817ada0, 8), called
from nathelper.c: nh_timer(2841)
Dec 6 15:55:15 [28924] DBG:core:qm_malloc: params (0x817ada0, 8), returns
address 0x81caa24 frag. 0x81caa0c (size=8) on 1 -th hit
Hi Daniel,
this is the (harmless) memory debugging that was activated to catch some
errors in memory management. This will be decativated next week, when 1.3 is
released. So you can either deactivate it by yourself (look in
Makefile.defs), ignore the messages or wait one week. ;-)
Cheers,
Henning
4:32 p.m.
thanks!
daniel
Henning Westerholt wrote:
On Thursday 06 December 2007, Daniel wrote:
--
---------------------------------------------------
Daniel Grotti
DEIS - University of Bologna
Via Venezia, 52 - 47023 Cesena (FC) - ITALY
Contacts
e-mail : daniel.grotti(a)unibo.it
Skype name : Daniel Grotti
---------------------------------------------------
I'm using the latest trunk version of
openser.
When I start the proxy I see on debug this messages repeated forever...
I'm using a config file that worked well wiht openser release 1.2.2.
Dec 6 15:55:14 [28924] DBG:core:qm_free: params(0x817ada0, 0x81caa24),
called from nathelper.c: nh_timer(2941)
Dec 6 15:55:14 [28924] DBG:core:qm_free: freeing frag. 0x81caa0c alloc'ed
from nathelper.c: nh_timer(2841)
Dec 6 15:55:15 [28924] DBG:core:qm_malloc: params (0x817ada0, 8), called
from nathelper.c: nh_timer(2841)
Dec 6 15:55:15 [28924] DBG:core:qm_malloc: params (0x817ada0, 8), returns
address 0x81caa24 frag. 0x81caa0c (size=8) on 1 -th hit
Hi Daniel,
this is the (harmless) memory debugging that was activated to catch some
errors in memory management. This will be decativated next week, when 1.3 is
released. So you can either deactivate it by yourself (look in
Makefile.defs), ignore the messages or wait one week. ;-)
Cheers,
Henning
7 Dec
7 Dec
5:49 p.m.
Interestingly enough, I'm not sure why asterisk is telling SER to respond to the
public IP?? When I commented out externip, everything works as it should, but this will
obviously break external SIP clients! Does anyone else have an issue like this?
### ASTERISK CONFIG ### 1.4 SVN HEAD
[general]
matchexterniplocally=yes
canreinvite=no
externip=xxx.206.xxx.136
localnet=10.3.1.0/255.255.255.0
context=default ; Default context for incoming calls
bindport=5061 ; UDP Port to bind to (SIP standard port is 5060)
bindaddr=0.0.0.0 ; IP address to bind to (0.0.0.0 binds to all)
sipdebug=yes ; Turn on SIP debugging by default, from
nat=no
[openser]
type=friend
context=default
insecure=very
externalnotify=yes
allow=all
host=10.3.1.31
Sip Client = 10.3.1.115
OpenSer = 10.3.1.31:5060
Asterisk = 10.3.1.31:5061
Outside IP (NAT) = xxx.206.xxx.136
|Time | 10.3.1.115 | 10.3.1.31 | xxx.206.xxx.136 |
|6.791 | Request: INVITE sip | |SIP/SDP: Request:
INVITE sip:500@10.3.1.31, with session description
| |(5060) ------------------> (5060) | |
|6.791 | Status: 100 Trying | |SIP: Status: 100
Trying
| |(5060) <------------------ (5060) | |
|6.791 | Status: 407 Proxy A | |SIP: Status: 407
Proxy Authentication Required
| |(5060) <------------------ (5060) | |
|6.794 | Request: ACK sip:50 | |SIP: Request: ACK
sip:500@10.3.1.31
| |(5060) ------------------> (5060) | |
|6.799 | Request: INVITE sip | |SIP/SDP: Request:
INVITE sip:500@10.3.1.31, with session description
| |(5060) ------------------> (5060) | |
|6.800 | Status: 100 Trying | |SIP: Status: 100
Trying
| |(5060) <------------------ (5060) | |
|6.803 | Status: 200 OK, wit | |SIP/SDP: Status:
200 OK, with session description
| |(5060) <------------------ (5060) | |
|6.817 | Request: ACK sip:50 | |SIP: Request: ACK
sip:500@xxx.206.xxx.136
| |(5060) ------------------> (5060) | |
|6.817 | | Request: ACK sip:50 |SIP: Request: ACK
sip:500@xxx.206.xxx.136
| | |(5060) ------------------> (5060) |
|7.804 | Status: 200 OK, wit | |SIP/SDP: Status:
200 OK, with session description
| |(5060) <------------------ (5060) | |
|7.806 | Request: ACK sip:50 | |SIP: Request: ACK
sip:500@xxx.206.xxx.136
| |(5060) ------------------> (5060) | |
|7.807 | | Request: ACK sip:50 |SIP: Request: ACK
sip:500@xxx.206.xxx.136
| | |(5060) ------------------> (5060) |
|8.803 | Status: 200 OK, wit | |SIP/SDP: Status:
200 OK, with session description
| |(5060) <------------------ (5060) | |
|8.805 | Request: ACK sip:50 | |SIP: Request: ACK
sip:500@xxx.206.xxx.136
| |(5060) ------------------> (5060) | |
|8.805 | | Request: ACK sip:50 |SIP: Request: ACK
sip:500@xxx.206.xxx.136
| | |(5060) ------------------> (5060) |
|10.803 | Status: 200 OK, wit | |SIP/SDP: Status:
200 OK, with session description
| |(5060) <------------------ (5060) | |
|10.806 | Request: ACK sip:50 | |SIP: Request: ACK
sip:500@xxx.206.xxx.136
| |(5060) ------------------> (5060) | |
|10.807 | | Request: ACK sip:50 |SIP: Request: ACK
sip:500@xxx.206.xxx.136
| | |(5060) ------------------> (5060) |
|14.803 | Status: 200 OK, wit | |SIP/SDP: Status:
200 OK, with session description
| |(5060) <------------------ (5060) | |
|14.805 | Request: ACK sip:50 | |SIP: Request: ACK
sip:500@xxx.206.xxx.136
| |(5060) ------------------> (5060) | |
|14.806 | | Request: ACK sip:50 |SIP: Request: ACK
sip:500@xxx.206.xxx.136
| | |(5060) ------------------> (5060) |
|18.803 | Status: 200 OK, wit | |SIP/SDP: Status:
200 OK, with session description
| |(5060) <------------------ (5060) | |
|18.806 | Request: ACK sip:50 | |SIP: Request: ACK
sip:500@xxx.206.xxx.136
| |(5060) ------------------> (5060) | |
|18.806 | | Request: ACK sip:50 |SIP: Request: ACK
sip:500@xxx.206.xxx.136
| | |(5060) ------------------> (5060) |
|22.802 | Status: 200 OK, wit | |SIP/SDP: Status:
200 OK, with session description
| |(5060) <------------------ (5060) | |
|22.805 | Request: ACK sip:50 | |SIP: Request: ACK
sip:500@xxx.206.xxx.136
| |(5060) ------------------> (5060) | |
|22.805 | | Request: ACK sip:50 |SIP: Request: ACK
sip:500@xxx.206.xxx.136
| | |(5060) ------------------> (5060) |
|38.046 | Request: BYE sip:50 | |SIP: Request: BYE
sip:500@xxx.206.xxx.136
| |(5060) ------------------> (5060) | |
|38.046 | | Request: BYE sip:50 |SIP: Request: BYE
sip:500@xxx.206.xxx.136
| | |(5060) ------------------> (5060) |
|38.491 | | Request: BYE sip:50 |SIP: Request: BYE
sip:500@xxx.206.xxx.136
| | |(5060) ------------------> (5060) |
|39.491 | | Request: BYE sip:50 |SIP: Request: BYE
sip:500@xxx.206.xxx.136
| | |(5060) ------------------> (5060) |
|39.548 | Request: BYE sip:50 | |SIP: Request: BYE
sip:500@xxx.206.xxx.136
| |(5060) ------------------> (5060) | |
|41.491 | | Request: BYE sip:50 |SIP: Request: BYE
sip:500@xxx.206.xxx.136
| | |(5060) ------------------> (5060) |
|42.788 | Request: BYE sip:50 | |SIP: Request: BYE
sip:500@xxx.206.xxx.136
| |(5060) ------------------> (5060) | |
|45.494 | | Request: BYE sip:50 |SIP: Request: BYE
sip:500@xxx.206.xxx.136
| | |(5060) ------------------> (5060) |
|49.495 | | Request: BYE sip:50 |SIP: Request: BYE
sip:500@xxx.206.xxx.136
| | |(5060) ------------------> (5060) |
-----Original Message-----
From: users-bounces(a)lists.openser.org on behalf of Daniel Grotti
Sent: Thu 12/6/2007 10:32 AM
To: Henning Westerholt
Cc: users(a)lists.openser.org
Subject: Re: [OpenSER-Users] starting openser trunk version
thanks!
daniel
Henning Westerholt wrote:
On Thursday 06 December 2007, Daniel wrote:
--
---------------------------------------------------
Daniel Grotti
DEIS - University of Bologna
Via Venezia, 52 - 47023 Cesena (FC) - ITALY
Contacts
e-mail : daniel.grotti(a)unibo.it
Skype name : Daniel Grotti
---------------------------------------------------
_______________________________________________
Users mailing list
Users(a)lists.openser.org
http://lists.openser.org/cgi-bin/mailman/listinfo/users
I'm using the latest trunk version of
openser.
When I start the proxy I see on debug this messages repeated forever...
I'm using a config file that worked well wiht openser release 1.2.2.
Dec 6 15:55:14 [28924] DBG:core:qm_free: params(0x817ada0, 0x81caa24),
called from nathelper.c: nh_timer(2941)
Dec 6 15:55:14 [28924] DBG:core:qm_free: freeing frag. 0x81caa0c alloc'ed
from nathelper.c: nh_timer(2841)
Dec 6 15:55:15 [28924] DBG:core:qm_malloc: params (0x817ada0, 8), called
from nathelper.c: nh_timer(2841)
Dec 6 15:55:15 [28924] DBG:core:qm_malloc: params (0x817ada0, 8), returns
address 0x81caa24 frag. 0x81caa0c (size=8) on 1 -th hit
Hi Daniel,
this is the (harmless) memory debugging that was activated to catch some
errors in memory management. This will be decativated next week, when 1.3 is
released. So you can either deactivate it by yourself (look in
Makefile.defs), ignore the messages or wait one week. ;-)
Cheers,
Henning
6202
days inactive
6203
days old
3 comments
4 participants
participants (4)
-
Daniel -
Daniel Grotti -
Henning Westerholt -
Patrick Baker