Yes, I believe the bug is somewhere else. I just noticed that there was no
patch for this particular bug report.
Our bug is somewhere else, there must be some other variables which are being
used without being initialized. Unfortunately I do not understand too well how
things work inside sipxtapi, so I don't know where to look.
I do know that the "MediaSignals" message pool is created in the MpMediaTask
class, and it is only accessed (as far as I can see) from
MpMediaTask::signalFrameStart( ). Apparently, the messages accessed from there
are being sent to the mIncomingQ OsMsgQ instance (found in OsServerTask class),
and the receiver of that message should probably be responsible of "freeing"
the message by calling pMsg->releaseMsg(); If this is not done, then the
message pool will get flooded with un-released messages which cannot be reused.
Who is responsible for releasing these messages, and why it fails under certain
circumstances is beyond me however. The fact that this doesn't happen all the
time (only during a certain type of calls) is only to complicate matters
further.
Regards,
Daníel
> From: [EMAIL PROTECTED]> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL
> PROTECTED]> CC: [email protected]> Subject: Re: [sipxtapi-dev]
> SipConnection.cpp: Variables initialization.> Date: Fri, 29 Jun 2007 18:19:28
> +0200> > I have applied your patch, but I'm still getting the error... must
> be> something else.> >
> "2007-06-29T16:17:18.108000Z":3830:KERNEL:WARNING:klnta::00000000:sipXtapi:">
> OsMsgPool::FindFreeMsg 'MediaSignals' queue size (64) exceeds soft limit>
> (32)\n">
> "2007-06-29T16:17:18.108000Z":3831:KERNEL:CRIT:klnta::00000000:sipXtapi:"OsM>
> sgPool::FindFreeMsg 'MediaSignals' queue size (64) exceeds hard limit>
> (64)\n"> > stipus> > ----- Original Message ----- > From: "Daniel
> Sigurgeirsson" <[EMAIL PROTECTED]>> To: "Alexander Chemeris" <[EMAIL
> PROTECTED]>; "Jhorsh Muhammed"> <[EMAIL PROTECTED]>> Cc: "sipxtapi-dev"
> <[email protected]>> Sent: Friday, June 29, 2007 5:46 PM>
> Subject: Re: [sipxtapi-dev] SipConnection.cpp: Variables initialization.> > >
> > Here is a patch file for this bug report. Done using TortoiseSVN. Is there>
> perhaps another alternative which should be used?> > Regards,> Daníel> > > >
> > Date: Thu, 21 Jun 2007 14:48:05 +0400> From: [EMAIL PROTECTED]>> To: [EMAIL
> PROTECTED]> CC: [email protected]> Subject: Re:>
> [sipxtapi-dev] SipConnection.cpp: Variables initialization.> > Hello,> > >>
> On 6/21/07, Jhorsh Muhammed <[EMAIL PROTECTED]> wrote:> > I found that these>
> arrays is not initialized.> > int receiveRtpPorts[MAX_ADDRESS_CANDIDATES];>>
> > int receiveRtcpPorts[MAX_ADDRESS_CANDIDATES];> > int>
> receiveVideoRtpPorts[MAX_ADDRESS_CANDIDATES];> > int>
> receiveVideoRtcpPorts[MAX_ADDRESS_CANDIDATES];> > so in RELEASE>
> configuration it is not working properly, when ports value is> > checking>
> for > 0.> > I found abnormal video ports value in SDP content of INVITE>
> message. After I> > add initialization, everything starts to work well.> >>
> For example Astrerisk shows error massage and call will be terminated.> >>
> Are you talking about SipConnection::dial()? It's better to tell line>
> number> or, even better, provide patches in unified diff format. You could>
> get such> patches by invoking "svn diff" command from command line under>
> sipXtapi> source tree.> > Anyway, thanks for your effort. :)> > -- >>
> Regards,> Alexander Chemeris.> > SIPez LLC.> SIP VoIP, IM and Presence>
> Consulting> http://www.SIPez.com> tel: +1 (617) 273-4000>>
> _______________________________________________> sipxtapi-dev mailing list>>
> [email protected]> List Archive:>
> http://list.sipfoundry.org/archive/sipxtapi-dev/>
> _________________________________________________________________> Play free
> games, earn tickets, get cool prizes! Join Live Search Club.>
> http://club.live.com/home.aspx?icid=CLUB_wlmailtextlink>
_________________________________________________________________
Make every IM count. Download Windows Live Messenger and join the i’m
Initiative now. It’s free.
http://im.live.com/messenger/im/home/?source=TAGWL_June07
_______________________________________________
sipxtapi-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
