wxcommunicator-developers Mailing List for wxCommunicator
Status: Beta
Brought to you by:
yaro_23
Menu
▾
▴
wxcommunicator-developers — Mailing list dedicated for developers.
You can subscribe to this list here.
| 2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(4) |
Jun
|
Jul
|
Aug
(5) |
Sep
|
Oct
|
Nov
|
Dec
|
|---|
|
From: <ja...@se...> - 2007-08-19 18:36:23
|
In revision 43 of sipxtapi from http://code.google.com/p/sipxtapi/, I made changes to make notifications from sipxmedialib work. Previously it was impossible without introducing bugs. Message types are defined in MpNotificationMsgDef.h . A corresponding file CpNotificationMsgDef.h exists in sipxcalllib, to prevent tight coupling to sipxmedialib. MpAudioResource has a new method: void sendInterfaceNotificationMsg(MpNotificationMsgType type, int data); MpNotificationMsgType is defined in MpNotificationMsgDef.h . To send event to sipxcalllib, call this function with proper parameters. Data is internal event data which is specific to given event type. This method should be used to fire events for resources in flowgraph, like recorder, player, tone generator etc. For decoders, encoders, DTMF decoders, a different method should be used, because these are part of MediaConnection and there can be many mediaconnections attached to flowgraph. We need to route event to the correct call. Use new method void sendConnectionNotification(MpNotificationMsgType type, int data); in MpRtpOutputAudioConnection.h and MpRtpInputAudioConnection.h. Decoder, encoder are part of either inputaudio connection or outputaudio connection. Decoder already has access to MpRtpInputAudioConnection and so can fire media events. The first type of notification described above is called interfaceNotification, as it reports information for the whole MediaInterface. The 2nd type of notification is ConnectionNotification as it informs about state of a connection. MediaInterface normally has 1 flowgraph, and 1 connection, but can have more connections in case of conferences. InterfaceNotifications are fired for all SipConnections in CpPeerCall simultaneously, while ConnectionNotifications are fired for the correct SipConnection in CpPeerCall only. Jaro |
|
From: <ja...@se...> - 2007-08-18 17:58:08
|
In the last revision, I made some cleanup in sipxmediaadapterlib, which also propagated to sipxtapi: I added: virtual OsStatus setOutboundDTMFMode(MEDIA_OUTBOUND_DTMF_MODE mode) virtual OsStatus getOutboundDTMFMode(MEDIA_OUTBOUND_DTMF_MODE& mode) virtual OsStatus enableInboundDTMF(MEDIA_INBOUND_DTMF_MODE mode, UtlBoolean enable) virtual OsStatus isInboundDTMFEnabled(MEDIA_INBOUND_DTMF_MODE mode, UtlBoolean& enabled) Where MEDIA_OUTBOUND_DTMF_MODE can be inband, rfc2833 or disabled, and MEDIA_INBOUND_DTMF_MODE inband or rfc2833. We need separate settings for outbound and inbound DTMF. We want to be able to enable/disable specific type of inbound DTMF tone detection (like to have rfc2833 only, or none). We also want the option to send DTMF via inband or rfc2833. In sipxtapi, new functions were added: SIPXTAPI_API SIPX_RESULT sipxConfigSetOutboundDTMFMode(const SIPX_INST hInst, const SIPX_OUTBOUND_DTMF_MODE mode); SIPXTAPI_API SIPX_RESULT sipxConfigGetOutboundDTMFMode(const SIPX_INST hInst, SIPX_OUTBOUND_DTMF_MODE* mode); SIPXTAPI_API SIPX_RESULT sipxConfigEnableInboundDTMF(const SIPX_INST hInst, SIPX_INBOUND_DTMF_MODE mode, int bEnable); SIPXTAPI_API SIPX_RESULT sipxConfigIsInboundDTMFEnabled(const SIPX_INST hInst, SIPX_INBOUND_DTMF_MODE mode, int* bEnabled); Old DTMF configuration functions were removed. New functions will always return error, as currently only rfc2833 is implemented. But I expect that soon we should have inband detection as well. We have inband DTMF decoder, it just has to be integrated. Then these funtions will start working. Jaro |
|
From: stipus <st...@st...> - 2007-08-10 22:44:11
|
|
From: Jaroslav L. <ja...@se...> - 2007-08-10 21:28:24
|
Sipxtapi audio API changes - sipxAudioGetNumInputDevices, sipxAudioGetInputDevice, sipxAudioGetNumOutputDevices, sipxAudioGetOutputDevice return realtime soundcard information, not from the time when sipxtapi was initialized. I removed sipxtapi instance parameter from these functions, as they have nothing to do with sipxtapi instance. Users have to check their code, as sipxtapi now expects a buffer where it expected an empty pointer before!! Jaro |
|
From: Jaroslav L. <ja...@se...> - 2007-08-10 21:24:42
|
Sipxtapi is now available from http://code.google.com/p/sipxtapi/source Check out by running svn checkout http://sipxtapi.googlecode.com/svn/trunk/ sipxtapi wxCommunicator doesn't use sipxtapi from SIP foundry. The reason is, that wxCommunicator is a testbed application for sipxtapi that is going to be used in a commercial application. Jaro |
|
From: Jaroslav L. <ja...@se...> - 2007-05-26 22:09:31
|
laban samuel wrote: > > > */Jaroslav Libak <ja...@se...>/* wrote: > > > Hi Jaro, as you said i have compiled with HAVE_INTEL_IPP. But when > > am debugging on line 493 (SdpCodec > > aCodec(SdpCodec::SDP_CODEC_G729A,) i see that this breakpoint is > > not hit at all. All the parts of code under HAVE_INTEL_IPP is > > enabled. I am using Visual Studio for this. Any idea why this point > > is not hit at all. > > > > > > Samuel. > > If you tell me where you got the source code for sipxtapi from, I can > try to compile it and help you more. > > Also check, whether in CpPhoneMediaInterface.cpp line 269 "G729A G723.1 > " is added to the supported codecs list. From there, try to follow what > happens. It should propagate then to wxCommunicator. > > Jaro > > > > > Jaro, i have sipxtapi-r9456.tar.bz2 > <http://downloads.sourceforge.net/wxcommunicator/sipxtapi-r9456.tar.bz2?modtime=1178099617&big_mirror=0> which > has been downloaded from your project in the site sourceforge.net. And > the line in CpPhoneMediaInterface.cpp line 269 "G729A G723.1" is enabled > but has not been added to the supported codecs list. > > Samuel Hi I just compiled sipxtapi-r9456.tar.bz2, and G.729a shows up in wxCommunicator codec list. You probably didn't enable correct configuration in some projects. I use the VS8 solution file sipX-msvc8.sln. I used Debug-IPP configuration for sipXmediaAdapterLib, SipXmediaLib, sipXtckLib and sipXtapi. If you use custom configuration, you have to put HAVE_INTEL_IPP into preprocessor definitions in these projects. Jaro |
|
From: Jaroslav L. <ja...@se...> - 2007-05-24 23:47:31
|
> Hi Jaro, as you said i have compiled with HAVE_INTEL_IPP. But when > am debugging on line 493 (SdpCodec > aCodec(SdpCodec::SDP_CODEC_G729A,) i see that this breakpoint is > not hit at all. All the parts of code under HAVE_INTEL_IPP is > enabled. I am using Visual Studio for this. Any idea why this point > is not hit at all. > > > Samuel. If you tell me where you got the source code for sipxtapi from, I can try to compile it and help you more. Also check, whether in CpPhoneMediaInterface.cpp line 269 "G729A G723.1 " is added to the supported codecs list. From there, try to follow what happens. It should propagate then to wxCommunicator. Jaro |
|
From: Jaroslav L. <ja...@se...> - 2007-05-23 08:15:19
|
laban samuel wrote: > Hi, this is samuel. > I want to enable G729 codex for this soft phone. I have compiled > wxCommunicator with IPP libraries. But the problem is that it does not > appear in the codec list. I am not sure how to make it work. Can you > please tell me what could be done to make it work. > > Did you compile sipXtapi projects with switch HAVE_INTEL_IPP? If its compiled with HAVE_INTEL_IPP, then in CpPhoneMediaInterface.cpp line 269 there is "G729A G723.1 " so G729A codec should be constructed. If its constructed it should be in the codec list. To see if its constructed go to int SdpCodecFactory::buildSdpCodecFactory(int codecCount, SdpCodec::SdpCodecTypes codecTypes[]) and place a breakpoint on line 493 (SdpCodec aCodec(SdpCodec::SDP_CODEC_G729A,) where we create the codec. Let me know what happens. Right now I don't have a functional sipXtapi with Intel IPP support on my hard drive so I can't try this. I'm in the middle of rewriting sipXtapi to get rid of bugs, and just yesterday I went into changing the internals of sipxtapi event system and didn't have time to make call and media events working. However about 2 months ago when I tested it it, G729A worked fine, while G723.1 didn't (it needs more work). Jaro |
|
From: <ja...@se...> - 2007-05-17 14:01:55
|
Did anyone try the new projects for wxCommunicator? They were commited to SVN lately. Or do you use Visual Studio 2005? Jaro |
