Open Source Sip: [OpenSIPStack] [SF] RTP fault ...

Up to Discussions in OpenSIPStack

15 Replies Last post: Aug 28, 2008 6:29 AM by Guest 1 2 Previous Next

Guest

Jun 18, 2008 9:08 AM

[OpenSIPStack] [SF] RTP fault

Guest

1. Jun 18, 2008 9:15 AM

in response to: Guest

Re: [OpenSIPStack] [SF] RTP fault

Hi, Joegen

Thanks, in the CVS 2008-06-17 this problem is resolved

joegen@opensipstack.org wrote:

Whit and H.Kropf,

A leak in OpalFlexiTranscoder proxy class maybe causing this behavior.
OpalFlexiTranscoder was first introduced by Ilian Pinzon so that
re-invites with a media channel change my allow the codec to be changed
in mid session. OpalFlexiTranscoder, however, does not have a
destructor override. This allowed the OpalTranscoder object it created
in the heap to be forever lost. I have committed a patch for this in
CVS and is ready for testing. Let me know if if does/doesn't fix this
issue. Thanks.

Joegen

Joegen E. Baclor wrote:

Ok this bug seems legitimate. I have created a ticket for this in
assembla.

http://www.assembla.com/spaces/opensbc/tickets/21 .

If there some more info you could send that might help crush this bug,
please send them in. As a backgrounder, the Voice Age G.729 codec
educational license only allows for one channel to be opened. This is
the reason why OPAL statically flag its usage. Thus, it is very
possible that this bug only became evident with G.729 but may also be
true for other codecs as well. The only diff is other codec might be
more forgiving than G.729. More information that would
confirm/disprove this case, please send them in.

Thanks

Joegen

Whit Thiele wrote:

I have also been able to replicate this issue. So far I've only seen it
happen using G.729. The first call seems to go through, but every subsequent
call attempt fails. I am going to try recompiling an older snapshot of the
CVS source I have.

H.Kropf - Have you found out anything new on this issue?

Whit

-----Original Message-----
From: opensipstack-devel-bounces@lists.sourceforge.net
opensipstack-devel-bounces@lists.sourceforge.net On Behalf Of
Joegen E. Baclor
Sent: Thursday, May 22, 2008 9:14 PM
To: H.Kropf
Cc: opensipstack-devel@lists.sourceforge.net
Subject: Re: OpenSIPStack SF RTP fault

Hi,

Thanks for the logs. They were very helpful. It is evident that the
previous call did not destroy the codec properly. I will try to
replicate this on my system. Ilian is currently on leave so it might
take a while for him to catch this thread. I have created a ticket for
this: http://www.assembla.com/spaces/opensbc/tickets/20

Joegen

H.Kropf wrote:

Hi

Log (for pwlib - level 6) - in attachments

Joegen E. Baclor wrote:

Hmmn. Strange. Seems like the codec from the previous call has not
been destroyed. Can you send me a maximum level log of two
consecutive calls right after fresh startup of your SoftPhone?

H.Kropf wrote:

can you put a break-point in OpalTranscoder::ConvertFrames() and
figure out where exactly it fails?

I can

bool OpalMediaPatch::Sink::WriteFrame(RTP_DataFrame & sourceFrame)
{
......
if (!primaryCodec->ConvertFrames(sourceFrame, intermediateFrames))
{
PTRACE(1, "Patch\tMedia conversion (primary) failed");
return false;
}
......
}

BOOL OpalTranscoder::ConvertFrames(const RTP_DataFrame & input,
RTP_DataFrameList & output)
{
.......
return Convert(input, output[0]);
}

BOOL OpalFlexiTranscoder::Convert( const RTP_DataFrame & input,
RTP_DataFrame & output)
{
return m_Transcoder->Convert( input, output );
}

BOOL OpalFramedTranscoder::Convert(const RTP_DataFrame & input,
RTP_DataFrame & output)
{
....
while (inputLength > 0)
{
......
if (!ConvertFrame(inputPtr, consumed, outputPtr, created))
return FALSE;
.......
}
.......
}

BOOL OpalFramedTranscoder::ConvertFrame(const BYTE * inputPtr,
PINDEX & /*consumed*/, BYTE * outputPtr, PINDEX & /*created*/)
{
return ConvertFrame(inputPtr, outputPtr);
}

BOOL Opal_PCM_G729::ConvertFrame(const BYTE * src, BYTE * dst)
{
if (voiceAgeEncoderInUse != this) return FALSE; //
!!!!!!!!!!!! <<<=== this place
......
}

Hi,

Are you a C++ developer? If so, can you put a break-point in
OpalTranscoder::ConvertFrames() and figure out where exactly it fails?

Joegen

H.Kropf wrote:

Hello

After a last update of library from CVS (2008-05-20), my softphone
(on OSS library) makes only one successful call after start. In
next calls there is no voice. In PTRACE-log there are many such
records

Media Patch:1eb9410 PWL: CID=0x0000 Patch Media conversion
(primary) failed
Media Patch:1eb9410 PWL: CID=0x0000 Patch Media conversion
(primary) failed
Media Patch:1eb9410 PWL: CID=0x0000 Patch Media conversion
(primary) failed
Media Patch:1eb9410 PWL: CID=0x0000 Patch Media conversion
(primary) failed

In the previous version (CVS 2008-05-12) this problem did not exist

This SF.net email is sponsored by: Microsoft Defy all challenges.
Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
opensipstack-devel mailing list
opensipstack-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensipstack-devel

No virus found in this incoming message.
Checked by AVG.
Version: 7.5.524 / Virus Database: 269.23.21/1458 - Release Date:

5/21/2008 7:21 AM

This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
opensipstack-devel mailing list
opensipstack-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensipstack-devel

No virus found in this incoming message.
Checked by AVG.
Version: 8.0.100 / Virus Database: 269.23.21/1458 - Release Date: 5/21/2008
7:21 AM

Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
opensipstack-devel mailing list
opensipstack-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensipstack-devel

Guest

2. Jun 19, 2008 5:55 AM

in response to: Guest

[OpenSIPStack] Unhandled exception

Hi,

I am using the ATLSIP.dll generated by the ATLSIP project to write a
softphone (in Delphi). The phone works fine, except that it throws
unhandled exceptions at seemingly random times. I don't get these problems
when running OSSPhone. I noticed that OSSPhone uses
AxInterop.ATLSIPLib.1.0.dll and not ATLSIP.dll. Is there a difference
between the dll's?

Regards,

Robert

Guest

3. Jun 19, 2008 9:25 PM

in response to: Guest

Re: [OpenSIPStack] Unhandled exception

Hi Robert,

To be honest, I created OSSPhone reference implementation in .NET C++
CLI by getting a book from the local book store. There is no way for
me to answer your question authoritatively because I might be as lost as
you are in this. My guess is AxInterop.ATLSIPLib.1.0.dll is a proxy DLL
that exposes the native COM DLL (ATLSIP) to the .NET framework. I've
got absolutely zero knowledge of Delphi so I wont even try giving my
opinion.

Joegen

Robert Vos wrote:

Hi,

Regards,

Robert

optotronic

10 posts since
Jun 16, 2008

4. Jun 20, 2008 6:05 PM

in response to: Guest

Re: [OpenSIPStack] Unhandled exception

Robert,

I am also trying to use ATLSIP.dll from Delphi. For me so far, I only seem to get exceptions during shutdown. I haven't been able to track the problem down yet.

I'm not a .NET programmer, but I've been assuming that OSSPhone is using ATLSIP.dll through AxATLSIPLib.dll, as Joegen suggests. ASTLSIP.dll is native code, but OSSPhone is .NET.

If there was a non-.NET version of OSSPhone using ATLSIP.DLL, debugging would be easier. There is an MFC version of OSSPhone, but it appears to use OpenSipStack directly.

One thing to remember is that OpenSipStack uses a lot of threads. Your code needs to be aware of this when implementing ATLSIP event handlers, since they will be executed (I believe) from a thread other than the main VCL thread. Thus accessing VCL controls directly won't work properly. You should also protect non-local variables using multithreading mechanisms (critical sections, mutexes, Windows events, etc.)

Finest regards,
Bill Root

Regards,

Robert

Guest

5. Jun 24, 2008 8:49 AM

in response to: optotronic

Re: [OpenSIPStack] Unhandled exception

Bill,

Is there any chance I could perhaps mail you my code, so you could tell me
if I am doing anything horribly wrong? It's just a form with buttons for
Initilize, Register, Call, Answer and Hangup (Plus a couple of events,
allthough I am still getting exceptions when I comment them out)

Regards,
Robert

Original Message

From: "OpenSIPStack Forum"
To:
Sent: Saturday, June 21, 2008 12:05 AM
Subject: Re: OpenSIPStack Unhandled exception

Robert,

I am also trying to use ATLSIP.dll from Delphi. For me so far, I only
seem to get exceptions during shutdown. I haven't been able to track the
problem down yet.

I'm not a .NET programmer, but I've been assuming that OSSPhone is using
ATLSIP.dll through AxATLSIPLib.dll, as Joegen suggests. ASTLSIP.dll is
native code, but OSSPhone is .NET.

If there was a non-.NET version of OSSPhone using ATLSIP.DLL, debugging
would be easier. There is an MFC version of OSSPhone, but it appears to
use OpenSipStack directly.

One thing to remember is that OpenSipStack uses a lot of threads. Your
code needs to be aware of this when implementing ATLSIP event handlers,
since they will be executed (I believe) from a thread other than the main
VCL thread. Thus accessing VCL controls directly won't work properly.
You should also protect non-local variables using multithreading
mechanisms (critical sections, mutexes, Windows events, etc.)

Finest regards,
Bill Root

I am using the ATLSIP.dll generated by the ATLSIP project to write
a
softphone (in Delphi). The phone works fine, except that it throws
unhandled exceptions at seemingly random times. I don't get these problems
when running OSSPhone. I noticed that OSSPhone uses
AxInterop.ATLSIPLib.1.0.dll and not ATLSIP.dll. Is there a difference
between the dll's?

Regards,

Robert

optotronic

10 posts since
Jun 16, 2008

6. Jun 24, 2008 3:35 PM

in response to: Guest

Re: [OpenSIPStack] Unhandled exception

Robert,

Yes, I'll take a peek at your code. Maybe we can publish a summary if we find anything that may help other Delphi users of OpenSipStack/ATLSIP.

You could send it via private message on the OpenSourceSIP forum. I was going to private message you my email address, but you're on as Guest.

Finest regards,
Bill

joegen

87 posts since
Apr 28, 2007

7. Jun 24, 2008 10:01 PM

in response to: optotronic

Re: [OpenSIPStack] Unhandled exception

I would be happy to accept the sample application as third party contribution to ATLSIP as long as the contributors are willing to support it in the mailing list. I've been thinking along the line of C#, VB.NET and Delphi.

Joegen

optotronic wrote:
Robert,

Yes, I'll take a peek at your code. Maybe we can publish a summary if we find anything that may help other Delphi users of OpenSipStack/ATLSIP.

You could send it via private message on the OpenSourceSIP forum. I was going to private message you my email address, but you're on as Guest.

Finest regards,
Bill

optotronic

10 posts since
Jun 16, 2008

8. Jun 26, 2008 12:09 PM

in response to: joegen

Re: [OpenSIPStack] Unhandled exception

Joegen,

I have a Delphi version of OSSPhone largely implemented, but it gets an access violation on shutdown in ATLSTIP.DLL, like my test program.

I see that the debug version of OSSPhone (MFC) frequently hangs on shutdown when run from Visual Studio 2005, if it was registered with the SIP server. When I "Break All" from Visual Studio, I get the following error message:

"The process appears to be deadlocked (or is not running any user-mode code). All threads have been stopped."

This happened the last three times I tried it. I logged in (to the SIP server), and twice quit without logging out. The third time I logged out before quitting.

I'm running in a Virtual PC 2007 VM under Windows XP.
I'm using CVS source from 2008-06-25.

Do you know of any problems during shutdown with OSSPhone (MFC) or OpenSipStack?

Finest regards,
Bill

optotronic

10 posts since
Jun 16, 2008

9. Jun 26, 2008 10:00 PM

in response to: optotronic

Re: [OpenSIPStack] Unhandled exception

More information:

I patched Logger.cxx (void LoggingIncrementingFileStream::InternalOpen()) to create the log file in the executable directory for Windows, since it's hard to know where the log file goes otherwise (I couldn't find it when running from Visual Studio)
The log file shows the following occurring after SoftPhoneManager::Terminate( PThread &, INT ) exits:

40:48:08.425 pcss.cxx(193) PWL: CID=0x0000 PCSS Deleted PC sound system endpoint.
40:48:08.426 endpoint.cxx(214) PWL: CID=0x0000 OpalEP pc endpoint destroyed.
40:48:08.434 DTL: CID=0x0000 *** REMOVED TRANSACTION *** NICT|2dc1daef-e5fb-1810-83a3-e8072970ac0a@proxy01.sipphone.com|z9hG4bK2dc1daefe5fb1810843ff7f0e31de16f|REGISTER
40:48:08.434 DBG: CID=0x0000 GC: First Stale Object SIPTransaction
40:48:08.434 DTL: CID=0x0000 *** REMOVED TRANSACTION *** NICT|2dc1daef-e5fb-1810-83a3-e8072970ac0a@proxy01.sipphone.com|z9hG4bK4649e0efe5fb1810843ff7f0e31de16f|REGISTER
40:48:08.435 DBG: CID=0x0000 GC: First Stale Object SIPTransaction
40:48:08.435 SIPTransactionStage.cxx(86) PWL: CID=0x0000 Transaction Thread 2264 Terminated
40:48:08.436 SIPTransactionStage.cxx(122) PWL: CID=0x0000 Transaction Cleaner Thread 2272 Terminated
40:48:08.436 SIPTransactionStage.cxx(122) PWL: CID=0x0000 Transaction Cleaner Thread 2580 Terminated
40:48:08.438 SIPTimerManager.cxx(92) PWL: CID=0x0000 *** DESTROYED *** SIPTimer Manager
40:48:08.438 endpoint.cxx(214) PWL: CID=0x0000 OpalEP sip endpoint destroyed.
40:48:08.438 manager.cxx(401) PWL: CID=0x0000 OpalMan Deleted manager.
40:48:08.439 DBG: CID=0x11a8 TRANSACTION: (NICT) DESTROYED
40:48:08.439 DTL: CID=0x11a8 NICT(146884423) *** DESTROYED *** - NICT|2dc1daef-e5fb-1810-83a3-e8072970ac0a@proxy01.sipphone.com|z9hG4bK2dc1daefe5fb1810843ff7f0e31de16f|REGISTER
40:48:08.440 DBG: CID=0x11a8 TRANSACTION: (NICT) DESTROYED
40:48:08.440 DTL: CID=0x11a8 NICT(146884425) *** DESTROYED *** - NICT|2dc1daef-e5fb-1810-83a3-e8072970ac0a@proxy01.sipphone.com|z9hG4bK4649e0efe5fb1810843ff7f0e31de16f|REGISTER
40:48:08.471 INF: CID=0x0cb4 *** DESTROYED *** REGISTER Session REGISTER-17476330465@proxy01.sipphone.com
40:48:08.472 DBG: CID=0x0cb4 REGISTER: Session DESTROYED
40:48:08.484 DBG: CID=0x11a8 TRANSACTION: (NICT) DESTROYED
40:48:08.484 DTL: CID=0x11a8 NICT(146884424) *** DESTROYED *** - NICT|2dc1daef-e5fb-1810-83a3-e8072970ac0a@proxy01.sipphone.com|z9hG4bK3d17dbefe5fb1810843ff7f0e31de16f|REGISTER
40:48:08.536 ECCIAPI.cxx(429) PWL: CID=0x0000 Accept failed for HTTP: WIN32 error 10093
40:48:08.537 ECCIAPI.cxx(429) PWL: CID=0x0000 Accept failed for HTTP: WIN32 error 10093
40:48:08.539 ECCIAPI.cxx(429) PWL: CID=0x0000 Accept failed for HTTP: WIN32 error 10093
40:48:08.540 ECCIAPI.cxx(429) PWL: CID=0x0000 Accept failed for HTTP: WIN32 error 10093
40:48:08.541 ECCIAPI.cxx(429) PWL: CID=0x0000 Accept failed for HTTP: WIN32 error 10093
40:48:08.543 ECCIAPI.cxx(429) PWL: CID=0x0000 Accept failed for HTTP: WIN32 error 10093
40:48:08.545 ECCIAPI.cxx(429) PWL: CID=0x0000 Accept failed for HTTP: WIN32 error 10093
40:48:08.547 ECCIAPI.cxx(429) PWL: CID=0x0000 Accept failed for HTTP: WIN32 error 10093
40:48:08.548 ECCIAPI.cxx(429) PWL: CID=0x0000 Accept failed for HTTP: WIN32 error 10093
40:48:08.549 ECCIAPI.cxx(429) PWL: CID=0x0000 Accept failed for HTTP: WIN32 error 10093
40:48:08.551 ECCIAPI.cxx(429) PWL: CID=0x0000 Accept failed for HTTP: WIN32 error 10093
40:48:08.552 ECCIAPI.cxx(429) PWL: CID=0x0000 Accept failed for HTTP: WIN32 error 10093
40:48:08.553 ECCIAPI.cxx(429) PWL: CID=0x0000 Accept failed for HTTP: WIN32 error 10093
40:48:08.555 ECCIAPI.cxx(429) PWL: CID=0x0000 Accept failed for HTTP: WIN32 error 10093
40:48:08.556 ECCIAPI.cxx(429) PWL: CID=0x0000 Accept failed for HTTP: WIN32 error 10093
40:48:08.557 ECCIAPI.cxx(429) PWL: CID=0x0000 Accept failed for HTTP: WIN32 error 10093
40:48:08.560 ECCIAPI.cxx(429) PWL: CID=0x0000 Accept failed for HTTP: WIN32 error 10093
40:48:08.561 ECCIAPI.cxx(429) PWL: CID=0x0000 Accept failed for HTTP: WIN32 error 10093
40:48:08.562 ECCIAPI.cxx(429) PWL: CID=0x0000 Accept failed for HTTP: WIN32 error 10093
40:48:08.564 ECCIAPI.cxx(429) PWL: CID=0x0000 Accept failed for HTTP: WIN32 error 10093
40:48:08.565 ECCIAPI.cxx(429) PWL: CID=0x0000 Accept failed for HTTP: WIN32 error 10093
40:48:08.567 ECCIAPI.cxx(429) PWL: CID=0x0000 Accept failed for HTTP: WIN32 error 10093
40:48:08.568 ECCIAPI.cxx(429) PWL: CID=0x0000 Accept failed for HTTP: WIN32 error 10093
40:48:08.569 ECCIAPI.cxx(429) PWL: CID=0x0000 Accept failed for HTTP: WIN32 error 10093
40:48:08.571 ECCIAPI.cxx(429) PWL: CID=0x0000 Accept failed for HTTP: WIN32 error 10093
40:48:08.572 ECCIAPI.cxx(429) PWL: CID=0x0000 Accept failed for HTTP: WIN32 error 10093
40:48:08.574 ECCIAPI.cxx(429) PWL: CID=0x0000 Accept failed for HTTP: WIN32 error 10093
40:48:08.575 ECCIAPI.cxx(429) PWL: CID=0x0000 Accept failed for HTTP: WIN32 error 10093
40:48:08.577 ECCIAPI.cxx(429) PWL: CID=0x0000 Accept failed for HTTP: WIN32 error 10093
40:48:08.578 ECCIAPI.cxx(429) PWL: CID=0x0000 Accept failed for HTTP: WIN32 error 10093
40:48:08.579 ECCIAPI.cxx(429) PWL: CID=0x0000 Accept failed for HTTP: WIN32 error 10093
40:48:08.581 ECCIAPI.cxx(429) PWL: CID=0x0000 Accept failed for HTTP: WIN32 error 10093
40:48:08.582 ECCIAPI.cxx(429) PWL: CID=0x0000 Accept failed for HTTP: WIN32 error 10093
40:48:08.584 ECCIAPI.cxx(429) PWL: CID=0x0000 Accept failed for HTTP: WIN32 error 10093
40:48:08.585 ECCIAPI.cxx(429) PWL: CID=0x0000 Accept failed for HTTP: WIN32 error 10093
40:48:08.586 ECCIAPI.cxx(429) PWL: CID=0x0000 Accept failed for HTTP: WIN32 error 10093
40:48:08.588 ECCIAPI.cxx(429) PWL: CID=0x0000 Accept failed for HTTP: WIN32 error 10093
40:48:08.589 ECCIAPI.cxx(429) PWL: CID=0x0000 Accept failed for HTTP: WIN32 error 10093
40:48:08.591 ECCIAPI.cxx(429) PWL: CID=0x0000 Accept failed for HTTP: WIN32 error 10093
40:48:08.592 ECCIAPI.cxx(429) PWL: CID=0x0000 Accept failed for HTTP: WIN32 error 10093
40:48:08.594 ECCIAPI.cxx(429) PWL: CID=0x0000 Accept failed for HTTP: WIN32 error 10093
40:48:08.595 ECCIAPI.cxx(429) PWL: CID=0x0000 Accept failed for HTTP: WIN32 error 10093
40:48:08.596 ECCIAPI.cxx(429) PWL: CID=0x0000 Accept failed for HTTP: WIN32 error 10093
40:48:08.598 ECCIAPI.cxx(429) PWL: CID=0x0000 Accept failed for HTTP: WIN32 error 10093
40:48:08.599 ECCIAPI.cxx(429) PWL: CID=0x0000 Accept failed for HTTP: WIN32 error 10093
40:48:08.600 ECCIAPI.cxx(429) PWL: CID=0x0000 Accept failed for HTTP: WIN32 error 10093
40:48:08.602 ECCIAPI.cxx(429) PWL: CID=0x0000 Accept failed for HTTP: WIN32 error 10093

I don't know much about OpenSipStack, but this seems like a lot of cleanup activity going on after OpenSipStack has said it has terminated. In trying to track down the shutdown errors in OSSPhone (MFC) previously, I did get hits in ECCIAPI suggesting that a previously freed event handler was being triggered. There was also an issue with a timer triggering something. (Maybe they're related.) Is there an easy way to make sure this stuff is completed before SoftPhoneInterface:Event_Terminated() is triggered?

Finest regards,
Bill Root

optotronic

10 posts since
Jun 16, 2008

10. Jul 17, 2008 11:45 AM

in response to: optotronic

Re: [OpenSIPStack] Unhandled exception

I think I found one shutdown problem. In SIPUserAgent.cxx:

void SIPUserAgent::Terminate()
{
GetTransportManager()->Terminate();
m_SIPStack.Terminate( m_ThreadPool.GetSize() );
m_ThreadPool.RemoveAll(); // <- added this
}

I added the last line to remove the workers from the thread pool. Otherwise, they appeared to be running forever.

Does that look right, or is there somewhere else where they should be destroyed, that is apparently not working properly?

I am still frequently getting hangs on shutdown, especially on multicore systems, but this seems to be an improvement. I'm using OSSPhone (MFC) for testing, as it seems to have the closest behavior to my Delphi test app.

Finest regards,
Bill Root

joegen

87 posts since
Apr 28, 2007

11. Jul 17, 2008 11:59 AM

in response to: optotronic

Re: [OpenSIPStack] Unhandled exception

I do not see any harm done so I added it in CVS. However, m_ThreadPool will delete all threads when SIPUserAgent gets deleted. If they seem to be running forever, then it means SIPUserAgent is staying forever too. Deleting SIPUserAgent will delete the threads.

Joegen

optotronic wrote:
I think I found one shutdown problem. In SIPUserAgent.cxx:

void SIPUserAgent::Terminate()
{
GetTransportManager()->Terminate();
m_SIPStack.Terminate( m_ThreadPool.GetSize() );
m_ThreadPool.RemoveAll(); // }

optotronic

10 posts since
Jun 16, 2008

12. Jul 23, 2008 2:05 PM

in response to: joegen

Re: [OpenSIPStack] Unhandled exception

Thank you, Joegen.

However, m_ThreadPool will delete all threads when SIPUserAgent gets deleted. If they seem to be running forever, then it means SIPUserAgent is staying forever too.

That corresponds with what I was seeing, however, now it is not happening. I don't know why.

I will send a private message in regard to the Delphi version of OSSPhone.

Finest regards,
Bill Root

Guest

13. Aug 22, 2008 12:23 PM

in response to: Guest

Re: [OpenSIPStack] [SF] Correct recognition of a called endpoint video capabilities

Hi,

SIP-phone Linksys/SPA2102-3.3.6 announce video capabilities but it don't
have they.

v=0
o=- 3748 3748 IN IP4 193.28.184.99
s=-
c=IN IP4 193.28.184.13
t=0 0
m=audio 20224 RTP/AVP 18 101
a=rtpmap:18 G729a/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20
a=sendrecv
m=video 0 RTP/AVP 31
a=nortpproxy:yes

Whether it is possible to "learn" OSS to perceive port "0" in string
"m=video 0 RTP/AVP 31" as absence of video capabilities?

This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
opensipstack-devel mailing list
opensipstack-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensipstack-devel

Guest

14. Aug 23, 2008 11:18 PM

in response to: Guest

Re: [OpenSIPStack] [SF] Correct recognition of a called endpoint video capabilities

Hi,

I have patched OpalOSSConnection

* $Log: OpalOSSConnection.cxx,v $
* Revision 1.36 2008/08/24 03:16:05 joegenbaclor
* Patched OnReceivedSDPMediaDescription not to overwrite
m_RemoteFormatList and to not
* create sessions for address or port == 0

Can you verify that this patch works?

Joegen

H.Kropf wrote:

No virus found in this incoming message.
Checked by AVG - http://www.avg.com
Version: 8.0.138 / Virus Database: 270.6.7/1628 - Release Date: 8/22/2008 6:32 PM

Go to original post 1 2 Previous Next

Go to original post

Jun 18, 2008 9:08 AM

[OpenSIPStack] [SF] RTP fault

Actions