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
Hi,
I've one exten on my ser box and one exten on Broadsoft switch. From SER I'm
not able to dial my broadsoft exten, b'coz broadsoft expect known user in
>From filed but I'm calling from SER so the From filed shows my SER user not
my broadsoft. So how do I change my From header when I call my broadsoft. Im
using ser-0.9.6 version. Please help.
Thanks,
Arun
Hi all,
I have to uninstall openser from my pc. Is there a "make uninstall" ?
Regerds,
daniel
--
Daniel Grotti
________________________
e-mail : d.grotti(a)gmail.com
Dear all,
I'm testing my proxy and I'm using mediaproxy for natted client.
Everything works fine, if there is a client behind nat calling a public
user, mediaproxy works fine. This is true also if there is a public client
calling a natted user.
I have some problem when there are 2 client behind NAT.
1. I tryed to test the system with 1 client behind NAT and 1 client behind
the SAME NAT (both of client under the same subnet:192.168.10.x).
In this case Mediaproxy doesn't work. RTP in direct between clients.
2. I tryed to test the system with 1 client behind NAT and 1 client behind
the SAME NAT (with clients under different subnet:192.168.10.x and
192.168.0.x).
In this case Mediaproxy doesn't work. RTP in direct between clients.
This is Mediaproxy Debug in the last case:
**********************************************
Dec 7 10:37:36 SERVER mediaproxy[2116]: request
ZDhiMWM2NDhmNzQ1ODNjYThkZjIxZGNiMmEzZmQxMjI. 192.168.0.167:58786:audio
NAT_IP PROXY_IP remote NAT_IP remote
X-Lite=20release=201011s=20stamp=2041150 info=from:userA@PROXY_IP,
to:UserB@PROXY_IP,fromtag:c1310701,totag:
Dec 7 10:37:36 SERVER mediaproxy[2116]: session
ZDhiMWM2NDhmNzQ1ODNjYThkZjIxZGNiMmEzZmQxMjI.: started. listening on
MEDIAPROXY_IP:60014
Dec 7 10:37:36 SERVER mediaproxy[2116]: execution time: 1.56 ms
Dec 7 10:37:43 SERVER mediaproxy[2116]: lookup
ZDhiMWM2NDhmNzQ1ODNjYThkZjIxZGNiMmEzZmQxMjI. 192.168.10.224:25732:audio
NAT_IP PROXY_IP remote unknown unknown
X-Lite=20release=201011s=20stamp=2041150 info=from:UserA@PROXY_IP,
to:UserB@PROXYIP,fromtag:c1310701,totag:67246350
Dec 7 10:37:43 SERVER mediaproxy[2116]: execution time: 0.51 ms
Dec 7 10:38:00 SERVER mediaproxy[2116]: delete
ZDhiMWM2NDhmNzQ1ODNjYThkZjIxZGNiMmEzZmQxMjI. info=
Dec 7 10:38:00 SERVER mediaproxy[2116]: session
ZDhiMWM2NDhmNzQ1ODNjYThkZjIxZGNiMmEzZmQxMjI.: 0/0/0 packets, 0/0/0 bytes
(caller/called/relayed)
Dec 7 10:38:00 SERVER mediaproxy[2116]: session
ZDhiMWM2NDhmNzQ1ODNjYThkZjIxZGNiMmEzZmQxMjI.: ended.
Dec 7 10:38:00 SERVER mediaproxy[2116]: execution time: 0.61 ms
*******************************
I am sure of mediaproxy change SDP parameter even in these last cases (I
can see on openser debug that proxy send out, for example, a 200 OK with SDP
part changed. And xlogs DEBUG show me that openser enters in
"use_media_proxy" routine) .
But when I sniff the packet on client side, I see SDP part with private IP !
Any suggestion?
Regards,
daniel
--
Daniel Grotti
________________________
e-mail : d.grotti(a)gmail.com
So I'm trying to diagnose an intermittent bug we seem to be having, and I'm not sure if Mediaproxy's the cause or not...
When a call is made through our system, and then the call is ended normally, the logs show the following mediaproxy entries:
Dec 6 12:14:02 server01 mediaproxy[14777]: delete 7dfafbf931195f8b61d7bbea68f9c0f8(a)xxx.xxx.xxx.xx1 info=
Dec 6 12:14:02 server01 mediaproxy[14777]: execution time: 0.20 ms
It seems to be pretty standard stuff, really. However, if a call is not made from behind a firewall, why is mediaproxy even running? Alas, this is not my main problem...
Every once in a while, calls get dropped. It happens more frequently than is acceptable. One common thing I've noticed when this happens, is mediaproxy will log a 'request' and start a session, and then approximately 30 seconds later, the call will be terminated.
Take this one for example. A customer originated a call this morning at Dec 6 11:25:18. Half an hour later, mediaproxy terminated the call. This was the log entry:
Dec 6 11:55:37 server01 mediaproxy[14777]: request 551afd3c247e7ddc5e8506d753494a3f(a)xxx.xxx.xxx.xx1 xxx.xxx.xxx.xx2:10508:audio xxx.xxx.xxx.xx2 sip.mydomain.com remote xxx.xxx.xxx.xx1 remote Quintum/1.0.0 info=from:1925XXXXXXX@sip.mydomain.com,to:1925XXXXXXX@xxx.xxx.xxx.xx1,fromtag:45364b32-2439a9,totag:as694a235d
Dec 6 11:55:37 server01 mediaproxy[14777]: session 551afd3c247e7ddc5e8506d753494a3f(a)xxx.xxx.xxx.xx1: started. listening on xxx.xxx.xxx.xx3:60490
Dec 6 11:55:37 server01 mediaproxy[14777]: execution time: 1.12 ms
Dec 6 11:56:08 server01 mediaproxy[14777]: delete 551afd3c247e7ddc5e8506d753494a3f(a)xxx.xxx.xxx.xx1 info=
Dec 6 11:56:08 server01 mediaproxy[14777]: session 551afd3c247e7ddc5e8506d753494a3f(a)xxx.xxx.xxx.xx1: 0/0/0 packets, 0/0/0 bytes (caller/called/relayed)
Dec 6 11:56:08 server01 mediaproxy[14777]: session 551afd3c247e7ddc5e8506d753494a3f(a)xxx.xxx.xxx.xx1: ended.
Dec 6 11:56:08 server01 mediaproxy[14777]: execution time: 0.68 ms
Is there any reason why mediaproxy might be arbitrarily loading and starting a new session, when the call has already long been established? I can't seem to make heads or tails of this. I'd appreciate any comments or suggestions.
Thanks,
Brian
This question is also posted at: http://www.voipuser.org/forum_topic_11777.html
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
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
Hi Henning,
but now how can I see the classic debug, without these messages scrolling on
the screen?
Thanks again,
Regards
Daniel
--
Daniel Grotti
________________________
e-mail : d.grotti(a)gmail.com
I'm trying to setup openser-svn-3261 with presence support and gettign the
following error.
Dec 5 18:04:27 ss-za /usr/local/sbin/openser[7403]: Handle PUBLISH
Dec 5 18:04:27 ss-za /usr/local/sbin/openser[7403]:
ERROR:presence:handle_publish: Missing or unsupported event header field
value
Dec 5 18:04:27 ss-za /usr/local/sbin/openser[7403]:
ERROR:presence:handle_publish: event=[presence
I'm also having issues starting Oser with presence_xml module, its crashes
with no error in my log. Disable it and oser
start fine.
--
TC
Folks,
for any of you using (or having interest in using) prepaid authentication based on CDRTool through FreeRADIUS Authorization methods, I announce the release 1.1 available to be downloaded from SourceForge.net.
Changelog from version 1.0 to present:
!Version 1.1 - 05.12.2007 by Dan-Cristian Bogos [dan(a)itsyscom.com]
* Replaced MAXDUR setting with SESSION_MAXDUR to be more descriptive
* Introducing experimental support for multiple cdrtool engines by setting MULTIPLE_PREPAID_ENGINES=True
* Simplified way of testing memcached connection (simple test against response list).
* Fixed BUG with sending non supported methods to CDRTool (eg: REGISTER and MESSAGE).
* Automatic mark of authenticated packets by returning third sip-avp "authentic#1".
* Return USERLOCK instead of REJECT when the account is locked.
* Added authenticate() function to comply with freeradius internals - not really necessary to be used.
* Fixed BUG which was failing accounting if Acct-Type was not fix positioned inside parameter tuple coming from FreeRADIUS.
* Introduced Acct-Authentic attribute dependency in order to fix double accounting in case of Yate(Cisco CDR with two leg accounting type). OpenSER should send Acct-Authentic attribute as radius_extra param with the value 1 for RADIUS or 3 for Remote.
* Fixed BUG which was emptying destination-uri in case of empty Canonical-URI.
* Forcing timeout for the keys in memcache based on SESSION_MAXDUR, for the case when no more accounting packets will arive after authorizaiton ones.
* Introduced support for Acct-Session-Time attribute which will produce more aqurate session time then automatic generated based on timestamps ones.
* Introduced support for combined accounting to fix the problems OpenSER has when no BYE packet arrives (eg: authorization generated by openser and accounting by Yate).
* Introduced support for newer cdrtool response 'Not Prepaid' derived from old 'NotPrepaid'
* Proper detection in case of Stop packets without Start being recorded inside memcached.
* Updated README-txt file to reflect the changes necessary in the configuration of OpenSER plus simplified way of installing freeradius with "./configure --with-experimental-modules"
I am at your disposal if any question might pop-up.
Project link:
https://sourceforge.net/projects/frad-cdrtool
DanB