Wireshark

  • Riverbed Technology
  • WinPcap
the world's foremost network protocol analyzer
  • Wireshark
    • About
    • Download
    • Blog
  • Get Help
    • Ask a Question
    • FAQs
    • Documentation
    • Mailing Lists
    • Online Tools
    • Wiki
    • Bug Tracker
  • Develop
    • Get Involved
    • Developer's Guide
    • Browse the Code
    • Latest Builds

Wireshark-dev: [Wireshark-dev] T.38 codec problem!!!

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next


From: "Deka Sanjeeb Kumar-KHBJ46" <KHBJ46@xxxxxxxxxxxx>
Date: Tue, 7 Apr 2009 18:59:23 +0800

Hi All,

I was trying to send FAX over IP network.

I enabled G729 and t.38 codec on both endpoints.

While checking the Wireshark trace of the session, i saw that first negotiation was done with G729 and media started flowing using this codec.

After some time re-negotiation happened with t.38 codec and FAX was properly transmitted.

But in the Wireshark trace could not see RTP packets with t.38 codec. RTP using G729 was still flowing even after the successfull negotiation with t.38. However the SSRC of the new G729 stream was changed to 0x0000(earlier it was a different value).

Moreover, i could see "Unknown RTP version 0" in the Wireshark trace after the second negotiation(negotiation with t.38).

I am not sure whether FAX was transmitted using G729 or t.38.

Could anyone help me out for the above scenario?

Regards.

Sanjeeb

  • Follow-Ups:
    • Re: [Wireshark-dev] T.38 codec problem!!!
      • From: Brian Daniel
    • Re: [Wireshark-dev] T.38 codec problem!!!
      • From: Jaap Keuter
  • Prev by Date: [Wireshark-dev] RTCP Frame length check: Wrong
  • Next by Date: [Wireshark-dev] wireshark -- atm n:1 dissector
  • Previous by thread: Re: [Wireshark-dev] RTCP Frame length check: Wrong
  • Next by thread: Re: [Wireshark-dev] T.38 codec problem!!!
  • Index(es):
    • Date
    • Thread

Wireshark and the "fin" logo are registered trademarks of the Wireshark Foundation