fanyapeng / doubango Goto Github PK

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?


Please provide any additional information below.

[deleted issue]

Add support for Diameter protocol as per RFC 3588.

What steps will reproduce the problem?
1. svn checkout http://doubango.googlecode.com/svn/branches/2.0 
2. build doubango with the same procedure of trunk on linux 
3.

What is the expected output? What do you see instead?

build libtinyDAV failed on tdav.c 

traces :

(cd ../tinyDAV ; make -f droid-makefile all; cp -f libtinyDAV_armv5te.a 
/home/pverney/dev/imsdroid/doubango.V2.x/doubango/android-projects/output)
make[1]: entrant dans le répertoire « 
/home/pverney/dev/imsdroid/doubango.V2.x/doubango/tinyDAV »
arm-eabi-gcc-4.4.0 -c  -DDEBUG_LEVEL=DEBUG_LEVEL_INFO 
-DDEBUG_LEVEL=DEBUG_LEVEL_INFO 
-I/home/pverney/dev/imsdroid/android-ndk-r4/build/platforms/android-8/arch-arm/u
sr/include -msoft-float -fpic -mthumb-interwork -ffunction-sections 
-funwind-tables -fstack-protector -D__ARM_ARCH_5__ -D__ARM_ARCH_5T__ 
-D__ARM_ARCH_5E__ -D__ARM_ARCH_5TE__ -MMD -MP -fno-short-enums -DANDROID  
-march=armv5te -mtune=xscale -Os -fomit-frame-pointer -fno-strict-aliasing 
-finline-limit=64 -DANDROID -static -I../thirdparties/android/include 
-DHAVE_ILBC=0 -DHAVE_LIBGSM=1 -DHAVE_FFMPEG=1 -DHAVE_H264=1 -DHAVE_THEORA=1 
-DHAVE_LIB_SPEEX=0 -DHAVE_SPEEX_DSP=0 -DHAVE_OPENCORE_AMR=1  -DHAVE_G729=0 
-I../tinySAK/src -I../tinyNET/src -I../tinySDP/include -I../tinyRTP/include 
-I../tinyMEDIA/include -I../tinyMSRP/include -I./include -DJB_HISTORY_SIZE=500 
src/tdav.c -o src/tdav.o
In file included from src/tdav.c:86:
./include/tinydav/audio/tdav_speakup_jitterbuffer.h:34:43: error: 
tinymedia/tmedia_JitterBuffer.h: No such file or directory
make[1]: *** [src/tdav.o] Erreur 1

What version of the product are you using? On what operating system?
Doubango branches 2.x

Please provide any additional information below.

Here is the update project file for Mac OS X. It includes the changes for 
tinyDAV which were pretty important in the last revisions.

The project folder is to be placed under "<ROOT>/xcode/MacOSX".

dear Team,

i am new in IMS & want to start work for symbian application with IM using IMS.
please provide help if possible-

1.how to start work for symbian os in IMS
2.please provide the source code & document for symbian.
3.Any other help could be appreciable.

so,kind of you.

thanks in advance!

regards,
satish

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?


Please provide any additional information below.

What steps will reproduce the problem?
1. Look at the specs 9.2.2.3 SMS-STATUS-REPORT type. Note that TP-PI and 
following parameters are optional.
2. Look at the _tsms_tpdu_status_report_deserialize function in 
tsms_tpdu_status_report.c 
3. Note that TSMS_ERROR_TOO_SHORT is called if optional parameters are missing.

What is the expected output? What do you see instead?
Absence of optional parameters is not an error but it is handled as an error:
2011-02-23 08:37:25,699 ERROR [6] BogheCore.Services.Impl.SipService:0 - 
***ERROR: function: "_tsms_tpdu_status_report_deserialize()" 
file: ".\src\tpdu\tsms_tpdu_status_report.c" 
line: "132" 
MSG: SMS-STATUS-REPORT == Data too short.

What version of the product are you using? On what operating system?
The error is seen in the code r551. The error appears in logs of Boghe-alpha 
(1.0.58.550) under Windows 7.

Please provide any additional information below.

What steps will reproduce the problem?
1.Is there any possibility of moving the current ffmpeg on doubango to the 
latest ffmpeg code?
2.
3.

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?


Please provide any additional information below.
I want to use the ffmpeg 0.7.1 for my app which is built on doubango stack. Can 
I please get the detailed instructions on how to build the ffmpeg libraries for 
android using Mingw(windows machine). 

[deleted issue]

Only on windows(please see visual studio configuration)

[deleted issue]

What steps will reproduce the problem?

1. In tsip_dialog_invite.server.c, 302 response is added for call redirection. 
Contact header is added for redirect uri. However, after 302 is sent, the 
domain name of Contact header is changed to local ip address.

What is the expected output? What do you see instead?

Expected to see Contact header containing target URI without replacing. Now the 
domain name of the target URI is replaced by local IP address.

What version of the product are you using? On what operating system?
Lastest code compiled with Imsdroid to run on Android 2.2.

Please provide any additional information below.

What steps will reproduce the problem?
1.A SIP header with multi line
2.tsip_message_parse would be fail
eg.

WWW-Authenticate: Digest realm="ims.com",(CRLF here)
 nonce="2dKTzX37hxIvBkoFXv8/PA==",algorithm=MD5,qop="auth"

"nonce" would be taken as a header then the parser runs fail

Please provide any additional information below.

If FFMpeg is not available, then the Theora codec should not be built. There is 
a missing pre-processor statement to guard the build in the 
"tdav_codec_theora.c" file. The code should be surrounded by "#if HAVE_FFMPEG" 
and "#endif"

The following patch contains:
- An amended CoreAudio consumer (a few tweaks and comments)
- A full CoreAudio producer
- Naming and comments corrections

In LTE context, it would be nice not to have to redefine the following 
constants and that Doubango provides them with #define directives:

- Strings for Event and Allow-Events headers: presence, reg, presence.winfo, 
etc.
- Strings for MIME type: application/reginfo+xml, application/watcherinfo+xml, 
etc.

Maybe, it could be merged with some constants found in XCAP.

What steps will reproduce the problem?
1. Use IMSDROID to send a REGISTER
2. 401 Authorized is back and nonce is taken in WWW-authenticate header
3. but no nonce in the second REGISTER message

What is the expected output? What do you see instead?
It is expected nonce is put in  Authorization header of REGISTER

What version of the product are you using? On what operating system?
v1.0.263

Please provide any additional information below.

What steps will reproduce the problem?
1.just call tsip_uri_parse("sip:123.com", strlen(~));
2.function return 0(null)

What is the expected output? What do you see instead?
expect output is a valid tsip_uri_t pointer with 
type:sip, host:123.com
but it return 0(null), and log invalid "Failed to parse SIP/SIPS/TEL URI."

What version of the product are you using? On what operating system?
Last version of doubango, Windows VC2008,

Please provide any additional information below.

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


Please use labels and text to provide additional information.

when imsdroid receive incoming call,and answer,then hangup.


REASON:
  when receive ACK from peer,tinysip create transaction for this dialog,then dialog object ref will increase.
  but dialog object ref will not decrease when hangup.
  so the relative object(for example dialog object) will not free.

BUG FIX:
tinySIP/src/dialogs/tsip_dialog_layer.c

tsip_dialog_layer_handle_incoming_msg.

transac = tsip_transac_layer_new(layer_transac, tsk_false, message, 
TSIP_DIALOG(dialog));
tsk_object_unref(dialog);

======>
                        if (!strcasecmp(message->CSeq->method,"ACK")) {
                                ret = dialog->callback(dialog, tsip_dialog_i_msg, message);
                                tsk_object_unref(dialog);
                                goto bail;
                        } else {
                                transac = tsip_transac_layer_new(layer_transac, tsk_false, message, TSIP_DIALOG(dialog));
                                tsk_object_unref(dialog);
                        }

What steps will reproduce the problem?
1.Try to establish an MSRP session between 2 Boghe client with an ALG in 
between which modifies the MSRP URI in the a=path attribute but doesn't change 
the From-Path and To-Path headers in the MSRP packets 
2.Communication over MSRP is not possible

I understand that draft-ietf-simple-msrp-sessmatch-10.txt is not implemented 
and is in the roadmap. Can you point me to the code that matches the MSRP URI 
in the MSRP packets with the MSRP URI negotiated in the SDP? I will try and 
relax the rules for MSRP URI comparison to make sess-match work. 

I saw tdav_session_msrp.c and there is a function match_offer which just 
returns tsk_true. Is this the function used for session matching?

Thanks,
Umang 

Thanks,
Umang

What steps will reproduce the problem?
1. We intend to use imsdroid1.x with doubango2.x, at least temporarily
2. Any known gotchas that we have to be aware of?
3.

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?


Please provide any additional information below.

i'm prefer to bonge ims client under vc++ not c#, have any scheduled?
i wanna know why use vc++ 9.0 in server, c# in client?
thanks

[deleted issue]

[deleted issue]

What steps will reproduce the problem?
1. Attached is a trace when PRACK is enabled
2. A calls B and A hangs up
3.

What is the expected output? What do you see instead?

BYE should have a CSeq number higher than PRACK's CSeq
But here it is the same, which is in violation of RFC 3261

According to RFC 3261 section 12.2.1.1

   Requests within a dialog MUST contain strictly monotonically
   increasing and contiguous CSeq sequence numbers (increasing-by-one)
   in each direction (excepting ACK and CANCEL of course, whose numbers
   equal the requests being acknowledged or cancelled).  Therefore, if
   the local sequence number is not empty, the value of the local
   sequence number MUST be incremented by one, and this value MUST be
   placed into the CSeq header field.  If the local sequence number is
   empty, an initial value MUST be chosen using the guidelines of
   Section 8.1.1.5.  The method field in the CSeq header field value
   MUST match the method of the request.

BYE is re-using the same CSeq number as that used in PRACK as indicated in the 
trace below


SENDING from network to pcsf(1)
[PRACK 
sip:QbkRBthOEgsTXgkTBA0HHiUrKz1CQEFCQ0NMNgQMGAlsMTcgK2ghOyAnOCs.ITogYX9jZGV4PjUq
dFVXXlsbV1tbWERLQkwOFgcACBNGCgUGVlheWUA_@pcsf-stdn.imsgroup0-000.ims.demo.alcate
l-lucent.com:5060 SIP/2.0
Via: SIP/2.0/UDP 127.0.0.1;branch=z9hG4bK_001_3797762552-3794627768
Via: SIP/2.0/UDP 
192.168.10.145:40627;received=10.8.0.62;branch=z9hG4bK1286255543346;rport=40627
From: <sip:[email protected]>;tag=1284673043811
To: 
<sip:[email protected]>;tag=4ca4a2a9-1285859926621769-gm-
po-lucentPCSF-000019
Contact: 
<sip:[email protected]:40627;transport=udp>;+g.oma.sip-im;language="en
,fr"
Call-ID: 73aa1663-edeb-decc-faba-8dd855649505
CSeq: 1908602408 PRACK
Content-Length: 0
Max-Forwards: 69
Route: <sip:192.11.69.128:5060;lr;transport=udp>
Route: <sip:pcsf-stdn.imsgroup0-000.ims.demo.alcatel-lucent.com:5060;lr;bidx=0>
Route: 
<sip:scsf-stdn.imsgroup0-000.ims.demo.alcatel-lucent.com:5070;lr;ottag=ue_orig;b
idx=12>
P-Preferred-Service: urn:urn-7:3gpp-service.ims.icsi.mmtel
Allow: INVITE,ACK,CANCEL,BYE,MESSAGE,OPTIONS,NOTIFY,PRACK,UPDATE,REFER
Privacy: none
P-Access-Network-Info: ADSL;utran-cell-id-3gpp=00000000
User-Agent: IM-client/OMA1.0 IMSDroid/v1.0.292 (doubango r487)
RAck: 1 1908602407 INVITE

]

SENDING from network to pcsf(1)
[BYE 
sip:QbkRBthOEgsTXgkTBA0HHiUrKz1CQEFCQ0NMNgQMGAlsMTcgK2ghOyAnOCs.ITogYX9jZGV4PjUq
dFVXXlsbV1tbWERLQkwOFgcACBNGCgUGVlheWUA_@pcsf-stdn.imsgroup0-000.ims.demo.alcate
l-lucent.com:5060 SIP/2.0
Via: SIP/2.0/UDP 127.0.0.1;branch=z9hG4bK_001_3800387512-3797172088
Via: SIP/2.0/UDP 
192.168.10.145:40627;received=10.8.0.62;branch=z9hG4bK1284531147919;rport=40627
From: <sip:[email protected]>;tag=1284673043811
To: 
<sip:[email protected]>;tag=4ca4a2a9-1285859926621769-gm-
po-lucentPCSF-000019
Call-ID: 73aa1663-edeb-decc-faba-8dd855649505
CSeq: 1908602408 BYE
Content-Length: 0
Max-Forwards: 69
Accept-Contact: *;+g.oma.sip-im
Accept-Contact: *;language="en,fr"
P-Preferred-Service: urn:urn-7:3gpp-service.ims.icsi.mmtel
Allow: INVITE,ACK,CANCEL,BYE,MESSAGE,OPTIONS,NOTIFY,PRACK,UPDATE,REFER
Privacy: none
P-Access-Network-Info: ADSL;utran-cell-id-3gpp=00000000
User-Agent: IM-client/OMA1.0 IMSDroid/v1.0.292 (doubango r487)

]



What version of the product are you using? On what operating system?

IMSDroid  v1.0.292 doubango r487

Please provide any additional information below.

The function "tsip_timers_setc(uint32_t c)" is mispelled in "tsip_timers.c": it 
should be "tsip_timers_setC" with a capital 'C'.

Hello! I'm trying to open boghe application in vs2010 for developing in 
winphone7 platform.... and there are issues with converting! How can i fix 
this, or how else i can develop my application for winphone7 using doubango???

[deleted issue]

Hi Sir

 I am using ngn- stack source download from http://imsdroid.googlecode.com/svn/branches/2.0/  tjis link.

it is build properly and make audio call successfull.
but the problem is there when we make vedio call . we have unable to make vedio 
call. so plz sir help me.


Thanks

Saurabh Shukla

What steps will reproduce the problem?
1. Create a tinyHTTP session
2. Make a GET request to a non-existant domain name with 'thttp_action_GET'
3. Wait for connection failure

What is the expected output? What do you see instead?

The connection failure should lead to a non-zero return code. Instead, a 0 
value is returned.

What version of the product are you using? On what operating system?

I am using the SVN revision 413.

Please provide any additional information below.

In function 'thttp_dialog_send_request', the return code should be set when a 
connection failure occurs (following the connectto) or when the socket 
writability test failed.

Hello! I've spent some time and implemented the YUV2RGB conversion 
library(http://wss.co.uk/pinknoise/yuv2rgb) port from the Theorarm code, it 
gives some sensible performance boost on my devices, although I lack the good 
instruments to calculate the exact value of it. Anyway, it can be switched on 
and off using the USE_ASM_YUV2RGB debug switch. Attached is the patch for 469 
revision of doubango although I doubt much has changed since that moment so I 
think it would be applicable with small to no changes to the current trunk. 
Check it out.

I use swig command to generate tinyWRAP_wrap.cxx under 
"oubango\bindings\_common".

command：swig -c++ -o tinyWRAP_wrap.cxx -package org.doubango.tinyWRAP -java 
tinyWRAP.i

But i get the new tinyWRAP_wrap.cxx file with "doubango\bindings\java\android
\tinyWRAP_wrap.cxx" have a lot of unlike, and run 
"bindings/java/android/buildAll.sh" not generate .so file


Please provide any additional information below.
I'm will very thanks. 

Below code snippet breaks the addCaps method in low-level Doubango SWIG API and 
causes OPTIONS to be missing an important 'Contact: ' header. addCaps should 
append the 'capabilities' to the 'Contact: ' header but since it's not there 
due to the code below, it creates multiple lines of 'Accept-Contact: ' 
headers...

The code section that needs to be checked is here. To fix it for OPTIONS, I 
simply commented out and took the lower default behavior to get a 'Contact: ' 
header and manually create an 'Accept-Contact: ' header.

tsip_dialog.c - Line 175 (code snippet):

    switch(request->line.request.request_type){
        case tsip_MESSAGE:
        case tsip_PUBLISH:
        case tsip_BYE:
        case tsip_OPTIONS:
            {
                if(request->line.request.request_type == tsip_PUBLISH) {
                    TSIP_MESSAGE_ADD_HEADER(request, TSIP_HEADER_EXPIRES_VA_ARGS(TSK_TIME_MS_2_S(self->expires)));
                }
                /* add caps in Accept-Contact headers */
                tsk_list_foreach(item, self->ss->caps) {
                    const tsk_param_t* param = TSK_PARAM(item->data);
                    char* value = tsk_null;
                    tsk_sprintf(&value, "*;%s%s%s", 
                        param->name,
                        param->value ? "=" : "",
                        param->value ? param->value : "");
                    if(value) {
                        TSIP_MESSAGE_ADD_HEADER(request, TSIP_HEADER_DUMMY_VA_ARGS("Accept-Contact", value));
                        TSK_FREE(value);
                    }
                }
                break;
            }

What steps will reproduce the problem?
1. If 100rel support is disabled (PRACK)
2.
3.

What is the expected output? What do you see instead?

Currently even if 100rel support is not enabled, PRACK is advertised as being 
supported. Here is a proposed patch

Index: include/tinysip/headers/tsip_header_Allow.h
===================================================================
--- include/tinysip/headers/tsip_header_Allow.h (revision previous)
+++ include/tinysip/headers/tsip_header_Allow.h (revision new)
@@ -36,6 +36,7 @@
 TSIP_BEGIN_DECLS

 #define TSIP_HEADER_ALLOW_DEFAULT      "ACK, BYE, CANCEL, INVITE, MESSAGE, NOTIFY, OPTIONS, PRACK, REFER, UPDATE"
+#define TSIP_HEADER_ALLOW_NOPRACK      "ACK, BYE, CANCEL, INVITE, MESSAGE, 
NOTIFY, OPTIONS, REFER, UPDATE"
 #define TSIP_HEADER_STR                            "Allow:"TSIP_HEADER_ALLOW_DEFAULT"\r\n"

 ///////////////////////////////////////////////////////////////////////////////
/////////////////////
Index: src/dialogs/tsip_dialog_invite.c
===================================================================
--- src/dialogs/tsip_dialog_invite.c    (revision previous)
+++ src/dialogs/tsip_dialog_invite.c    (revision new)
@@ -1135,10 +1135,17 @@
                        }

                        /* Add Allow header */
-                       tsip_message_add_headers(response,
+                       if(self->supported._100rel){
+                               tsip_message_add_headers(response,
                                                TSIP_HEADER_DUMMY_VA_ARGS("Allow", TSIP_HEADER_ALLOW_DEFAULT),
                                                tsk_null
                                        );
+                       } else {
+                               tsip_message_add_headers(response,
+                                               
TSIP_HEADER_DUMMY_VA_ARGS("Allow", TSIP_HEADER_ALLOW_NOPRACK),
+                                               tsk_null
+                                       );
+                       }
                }

                ret = tsip_dialog_response_send(TSIP_DIALOG(self), response);
What version of the product are you using? On what operating system?


Please provide any additional information below.

What steps will reproduce the problem?
1. in some case ,we want to get video I frame to display the video, this is a 
standard , that ,when we canot decode the video we should send video frame 
update request, as such ,we use INFO method in sip,

i have learn the doubango stack , the flow should be that : video session make 
a video frame update event ,
 the sip stack get the event and send a info request which sdp is a xml ,
but i donot know how to info from tdav_session_video to sip stack as there is 
no struct which hold the video session and sip stack, so , please give me some 
hint ,
 thanks :)

2.
3.

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?


Please provide any additional information below.

Here is an update of the iOS 4.0 project files with an up-to-date source tree.

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


Please use labels and text to provide additional information.

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


Please use labels and text to provide additional information.

Here is an update of the Mac OS X 10.5 project files with an up-to-date source 
tree.

What steps will reproduce the problem?
1. I add zoom and scrool function for video call.
2. Affter that, i make video call (using H.264 codec).
3. Then trying zoom and scrool video

What is the expected output? What do you see instead?
The zoom is OK. But when i moving the video on screen it not effect. Then i 
trying to resize the image. I got problem: decode H.264

What version of the product are you using? On what operating system?
IMSdroid 2x/Android 2.2
Please provide any additional information below.

There is a potential memory in the "tsk_thread_create" function.

The first parameter is a pointer on a memory zone that will store the newly 
started thread handle. On Unix platform (with pthread), the pointed zone is 
allocated on the heap, but the deallocation only occurs if the 
"tsk_thread_join" is called.

Is it possible to add a note that specifies that the pointed zone needs to be 
freed by the caller in order to avoid memory leaks, either by calling 
"tsk_thread_join" or by freeing it ?

What steps will reproduce the problem?
1. Checked out r491 version of doubango
2. Opened tinyDEMO.sln in Visual Studio 2008
3. Missing Project dependencies and libraries caused the build to fail

What is the expected output? What do you see instead?
Compile of the solution files should have succeded in the first attempt
Certain projects that depended on tinySAK, as an example, were compiled ahead 
of tinySAK and thus failed. Attached is a revised tinyDEMO.sln
file where I have tried to resolve the inter-project dependency issues so that 
the solution compiles on the first attempt.

Also, dsound.lib and dxguid.lib that were expected by tinyDAV were missing. 
These files need to be copied into 
thirdparties\win32\lib\directshow\

After this, the project compiles clean.


What version of the product are you using? On what operating system?

Visual Studio 2008 Standard Edition on Windows Vista 32-bit

Please provide any additional information below.

[deleted issue]

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


Please use labels and text to provide additional information.

[deleted issue]

Is it possible to expose the following define in the public API ?

- TXCAP_MIME_TYPE_ELEMENT
- TXCAP_MIME_TYPE_ATTRIBUTE
- TXCAP_MIME_TYPE_NS
- TXCAP_MIME_TYPE_ERROR

They are currently defined in "txcap_action.c".

What steps will reproduce the problem?
1.make a call to a phone which is binding with other number, and it send back a 
update message. 
2.
3.

What is the expected output? What do you see instead?
ignore the update package,hand off the phone.

What version of the product are you using? On what operating system?
version:doubangoSVN578 ,os:android2.2.

Please provide any additional information below.
how to response the "UPDATE" message?
thanks,sir.

What steps will reproduce the problem?
1. Create a tinyHTTP session
2. Make a request to a domain
3. When the response include an "Etag" header, and it contains "W/"
   'thttp_header_ETag_parse' runs fail

ex:

Etag: W/"1231-3213213"