__________ Information provenant d'ESET NOD32 Antivirus, version de la base des signatures de virus 6272 (20110707) __________
Le message a été vérifié par ESET NOD32 Antivirus.
http://www.eset.com
__________ Information provenant d'ESET NOD32 Antivirus, version de la base des signatures de virus 6274 (20110707) __________
__________ Information provenant d'ESET NOD32 Antivirus, version de la base des signatures de virus 6274 (20110707) __________
> Le message a �t� v�rifi� par ESET NOD32 Antivirus.
>
> http://www.eset.com
>
> __________ Information provenant d'ESET NOD32 Antivirus, version de la
> base des signatures de virus 6274 (20110707) __________
>
> Le message a �t� v�rifi� par ESET NOD32 Antivirus.
>
> http://www.eset.com
>
> __________ Information provenant d'ESET NOD32 Antivirus, version de la
> base des signatures de virus 6274 (20110707) __________
>
> Le message a �t� v�rifi� par ESET NOD32 Antivirus.
>
> http://www.eset.com
__________ Information provenant d'ESET NOD32 Antivirus, version de la base
des signatures de virus 6276 (20110708) __________
Le message a �t� v�rifi� par ESET NOD32 Antivirus.
__________ Information provenant d'ESET NOD32 Antivirus, version de la base des signatures de virus 6276 (20110708) __________
Le message a �t� v�rifi� par ESET NOD32 Antivirus.
----- Original Message -----From: rakesh kumarSent: Friday, July 08, 2011 3:43 PMSubject: Re: i can't use DTMF RFC 2833
Envoyé de mon iPhone
The RTP sequence number of softphone's RFC2833 packets is wrong, please let developer check it. And Please reference the way of X-lite when sending RFC2833 packets within a RTP stream.please note that i tested the DTMF with in-band and it's working as well but with RFC2833 it's not
On 8/2/11 1:04 PM, Mamadou wrote:
Our implementation follows the standard (rfc 4733) and if there is a problem they must tell what is the problem. "Please reference the way of X-lite when sending RFC2833 packets..." is not a response. We expect something like this: "According to rfc xxxx section yyyy you must do this but your doing that". On Aug 2, 1:02 pm, Mohamed Hisham <his...@mhisham.net> wrote:
I Replaced parameter 4 from "seq_num" to "++seq_num" in line 458 & 461 but the same error with the following log file Regards ! Mohamed Hisham Development Team Leader On 8/2/11 12:16 PM, Mamadou wrote:For sure we will not do something because x-lite do the same. Try to increment the sequence number in the retransmission of the two last DTMF event packets:http://code.google.com/p/doubango/source/browse/branches/2.0/doubango/tinyDAV/src/audio/tdav_session_audio.c#458http://code.google.com/p/doubango/source/browse/branches/2.0/doubango/tinyDAV/src/audio/tdav_session_audio.c#461Replace parameter 4 from "seq_num" to "++seq_num". On Aug 2, 11:41 am, Mohamed Hisham<his...@mhisham.net>wrote:Hello Mamadou, I contact hanlong company witch made "Landline converter" and i facing the problem of DTMF I sent them the telnet log file for success DTMF from x-lite and faild DTMF from idoubs v2 and they are answer that:The RTP sequence number of softphone's RFC2833 packets is wrong, please let developer check it. And Please reference the way of X-lite when sending RFC2833 packets within a RTP stream.please note that i tested the DTMF with in-band and it's working as well but withRFC2833it's not i can give you account on my server and test it with you if you want :) Thanks Regards ! Mohamed Hisham Development Team Leader On 7/17/11 2:18 AM, Mamadou wrote:@Json Penton You are wrong. I support RFC 4733 (which obsolete RFC 2833). The wav files are only used to alert the user that the digit has been sent (to provide user experience). For more information, here is the source code:http://code.google .com/p/doubango/source/ browse/branches/2.0/doubango/tinyDAV/src/audio/tdav_session_audio.c#347@MohamedHisham I really think the problem comes from your server. We are using the same code since Doubango v1.x and successfully tested it against many IMS/SIP networks from big European Telco operators. The rtpevent packets are sent to your server as soon as you press the button and we cannot guess what will be the next digits. It's up to your server match the digits. On Jul 16, 11:29 am, Tayeb Meftah<tayeb.mef...@gmail.com>wrote:Testing it... Envoyé de mon iPhone Le 16 juil. 2011 à 10:33, Jason Penton<jason.pen...@gmail.com>a écrit : Mamadou, please correct me if I am wrong but according to the codebas, doubango does not support RFC2833 (aka out of band DTMF). IMSDroid pl ays DTMF tones from wav files within the RTP s tream. naturally, this is very unreliable, especially when using compression codecs like AMR, G729, etc cheers Jason On Sat, Jul 16, 2011 at 11:33 AM, Mohamed Hisham<his...@mhisham.net>
wrote: Hi Mamadou, Did you test to enter many DTMF in one call like extension for example: when you call number with recorded message and it's say "for english Press one" when you press 1 on the DTMF it's working because it's one digit "for sales enter 280" you cant enter this extension on DTMF Pad because u have to enter it very fast i tried it many times with different DTMF RFC and find that if i set it static on the code like this [Session setDTMF:2]; [Session setDTMF:8]; [Session setDTMF:0];it's work but when user enter it number by number it's should be very very fast Hope you got my point :) *Regards !**Mohamed Hisham**Development Team Leader*On 7/8/11 2:41 PM, Mamadou wrote: Hi, I'm using the lates t version of iDoubs v2 and cannot reproduce the issue. The DTMF digits are always sent. How did you make the conclusion? Could you please use wireshark and filter on "rtpevent"? For information, the DTMF digits are only sent when the RTP channel is open: Call established or Early media start. The only issue I can see is that the DTMF sound played by the device is very low (routed on the earpiece).On Jul 7, 9:05 pm, "Meftah Tayeb"<tayeb.mef...@gmail.co m><tayeb.mef...@gmail.com>wrote: ok, ask mamadou about that. i have one, but without codecs. thank you for your bad thinking. ----- Original Message ----- From: Mohamed Hisham To:doubango@googlegroups.c om Cc: Meftah Tayeb Sent: Thursday, July 07, 2011 8: 04 PM Subject: Re: i can't use DTMF RFC 2833 How can you test iDoubs V2 and you don't have it and asking for someone to build it for you please don't spam emails Dear Mamadou, I'm waiting your answer and Thank you :) Regards ! Mohamed Hisham Development Team Leader On 7/7/11 8:56 PM, Meftah Tayeb wrote: dear Hisham, i tried iDoubs V2 with my server without any issue at all. please could you tel me what server software are you using? thank you. ----- Original Message ----- From: Mohamed Hisham To:doub...@googlegroups.com Sent: Thursday, July 07, 2011 6:05 PM Subject: i can't use DTMF RFC 2833 Hello Sir, I Like your Good job and efforts and man y thanks for your answers too I use iDoubs v2 and have a problem with DTMF I trying to make it support RFC 2833 but with no result when i press DTMF buttons very fast it's works but i don't know why i have to touch it very fast to setDTMF Thanks in advance -- Regards ! Mohamed Hisham Development Team Leader... read more » DTMF.txt < 1KViewDownload DTMF.txt 1KViewDownload
// TODO: Add support for outbound DTMF (http://www.ietf.org/rfc/rfc2833.txt)http://code.google.com/p/doubango/source/browse/branches/2.0/doubango/tinyRTP/src/trtp_manager.c#41
----- Original Message -----
From: "Mamadou" <diopm...@doubango.org>
To: "Doubango" <doub...@googlegroups.com>
Sent: Wednesday, August 03, 2011 7:02 PM
Subject: Re: i can't use DTMF RFC 2833
> Envoy� de mon iPhone Le 16 juil. 2011 � 10:33, Jason
> Penton<jason.pen...@gmail.com>a �crit : Mamadou, please correct me if I am
__________ Information provenant d'ESET NOD32 Antivirus, version de la base
des signatures de virus 6347 (20110803) __________
Le message a �t� v�rifi� par ESET NOD32 Antivirus.
__________ Information provenant d'ESET NOD32 Antivirus, version de la base des signatures de virus 6347 (20110803) __________
Le message a �t� v�rifi� par ESET NOD32 Antivirus.
Regards !
Mohamed Hisham
Development Team Leader
GULFSIP : 121
GULFSIP Telecom Co. ( Egypt Branch )
mhi...@gulfsip.com
www.gulfsip.com
Regards !
Mohamed Hisham
Development Team Leader
GULFSIP : 121
GULFSIP Telecom Co. ( Egypt Branch )
mhi...@gulfsip.com
www.gulfsip.com
On Aug 3, 2011, at 8:02 PM, Mamadou <diopm...@doubango.org> wrote:
Regards !
Mohamed Hisham
Development Team Leader
GULFSIP : 121
GULFSIP Telecom Co. ( Egypt Branch )
mhi...@gulfsip.com
www.gulfsip.com
On Aug 3, 2011, at 8:02 PM, Mamadou <diopm...@doubango.org> wrote:
Hello Mamadou,
Why you didn't reply to me we need to catch this issue together
I'm still waiting your reply
On 8/4/11 9:39 PM, Mohamed Hisham wrote:
http://code.google.com/p/doubango/source/browse/branches/2.0/doubango/tinyDAV/src/audio/tdav_session_audio.c#451 To http://code.google.com/p/doubango/source/browse/branches/2.0/doubango/tinyDAV/src/audio/tdav_session_audio.c#463i tested it on many elastix servers and works after commented this lines i think this lines to send many digit like this
__________ Information provenant d'ESET NOD32 Antivirus, version de la base des signatures de virus 6368 (20110811) __________
FXO gateway
----- Original Message -----From: Mohamed HishamCc: Meftah Tayeb ; MamadouSent: Thursday, August 11, 2011 2:42 PMSubject: Re: i can't use DTMF RFC 2833
<Screen shot 2011-08-20 at 8.33.36 AM.png>
----- Original Message -----From: Mohamed HishamCc: Mamadou
__________ Information provenant d'ESET NOD32 Antivirus, version de la base des signatures de virus 6396 (20110820) __________
> Le message a �t� v�rifi� par ESET NOD32 Antivirus.
>
> http://www.eset.com
>
> __________ Information provenant d'ESET NOD32 Antivirus, version de la
> base des signatures de virus 6396 (20110820) __________
>
> Le message a �t� v�rifi� par ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
__________ Information provenant d'ESET NOD32 Antivirus, version de la base
des signatures de virus 6396 (20110820) __________
Le message a �t� v�rifi� par ESET NOD32 Antivirus.
__________ Information provenant d'ESET NOD32 Antivirus, version de la base des signatures de virus 6396 (20110820) __________
Le message a �t� v�rifi� par ESET NOD32 Antivirus.