That's not a useful trace. A useful trace is the raw pcap format. Thus,
do not export the packets, just "save" the capture in Wireshark.
regards
Klaus
PS: to minimize the size of the capture just apply a display filter
which shows only the relevant packets (e.g. SIP (call setup) and the
relevant RTP packets). and then "save as" -> "displayed"
regards
Klaus
Am 30.06.2010 07:24, schrieb Jose Suarez:
> Benny, I send you the rtp packets that I capture using Wireshark.
> In this attach are the rtp that I captured using the pjsip version 1.6.
> In that case I dial a dtmf but the application can't detect it.
> In the next email I'll send you the same attach but compiling with the
> pjsip version 1.3 (in this version the application can detect the
> incoming dtmf).
>
> thanks in advance,
> Jose
>
>
> ----- Original Message ----- From: "Benny Prijono" <bennylp@xxxxxxxxx>
> To: "pjsip list" <pjsip at lists.pjsip.org>
> Sent: Wednesday, June 30, 2010 12:59 AM
> Subject: [SPAM] - Re: incoming DTMF detection failed. Please
> HELP!!!! - Email found in subject
>
>
> What software are you using to send the DTMF?
>
> It would help if you also attach Wireshark capture of the RTP packets
> containing the DTMF events (and please make the pcap file is small, as
> we have 500KB attachment size limit on this list)
>
> Best regards,
> Benny
>
>
> On Tue, Jun 29, 2010 at 1:07 AM, Jose Suarez <jsuarez at padirac.com.ar>
> wrote:
>> Sorry for my emails but I'm very worried because I migrated my
>> application
>> to 1.6 version (I've used 1.3) because a problem in the registration
>> and now
>> I found that in this version I can't detect the incoming dtmf. My
>> application plays a message and waits for a dtmf input to repeat that
>> message but this dtmf is never detected. The code is the same that in the
>> pjsip1.3 version and in this version it functions ok.
>> In simple words, I set the callback in the pjsua_config structure
>> (.cb.on_dtmf_digit = &onDtmfDigit) but I don't receive any dtmf in that
>> callback (but I received them when I used the 1.3 version).
>> the onDtmfDigit is like this:
>> void onDtmfDigit (pjsua_call_id pjCallId, int iDigit)
>> {
>> std::stringstream ssLog;
>> std::string strDtmf;
>>
>> ssLog << iDigit;
>> strDtmf = ssLog.str();
>>
>> ssLog.str("");
>>
>> ssLog << "OnDtmfDigit - call id: <";
>> ssLog << pjCallId;
>> ssLog << ">- Dtmf detected: <";
>> ssLog << iDigit;
>> ssLog << ">.";
>>
>> strLog = ssLog.str();
>>
>> m_oLogger->write (strLog, CDialerLogger::iLogWarning);
>> }
>>
>> Could you help me please?? Is it a bug in the 1.6 version or I must
>> detect
>> the Dtmf digits in a different way?
>> I've worked too much in that project and I'm worried that I can't
>> solve that
>> because is very important to the application that I can detect DTMF.
>>
>> Thanks in advance!!
>> Jose
>> _______________________________________________
>> Visit our blog: http://blog.pjsip.org
>>
>> pjsip mailing list
>> pjsip at lists.pjsip.org
>> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>>
>>
>
> _______________________________________________
> Visit our blog: http://blog.pjsip.org
>
> pjsip mailing list
> pjsip at lists.pjsip.org
> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>
>
>
> _______________________________________________
> Visit our blog: http://blog.pjsip.org
>
> pjsip mailing list
> pjsip at lists.pjsip.org
> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
