• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 98 subscribers
  • Views 869 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

faxlib parsing of xferpktInfo_t

huang jack
Intellectual 970 points

i'm using faxlib, the input of fiuReceiveIn is xferpktInfo_t, xferpktInfo_t.pktIn is the data of IFP packet, where can i find the definition of IFP packet, which document define it ? thanks!

  • 0
    TI__Mastermind 20755 points

    You can find the information at:

    packages\ti\mas\iface\ifpkt\docs\doxygen\IFPKT.chm

    Regards

    Yogesh

  • 0 in reply to Yogesh Siraswar
    Intellectual 970 points

    hi，Yogesh

    i read the post http://e2e.ti.com/support/embedded/multimedia_software_codecs/f/356/t/234567.aspx ， which document define theimage in the post and where to find it‘s description　？

    i print one packet of fiuReceiveIn

    pktSize[0] : 25

    pktIn[0] : 09:0a:06:c0:01:80:00:00:f4:00:02:06:c0:01:80:00:00:c8:06:c0:01:80:00:00:ff:

    according to the image, i analysis the packet, 

    sequence number : 09:0a:
    ifp size : 06:
    data message : c0:
    data field count : 01:
    data field type : 80:
    length of data field : 00:00:
    data : f4:
    data field type : 00:
    length of data field : 02:06:           the length of data field doesn't match the the length of packhet 25, why ?
    data : c0:01:80:00:00:c8:06:c0:01:80:00:00:ff

    did i analysis it correctly ?

    thanks!


  • 0 in reply to huang jack
    TI__Guru* 95265 points

    The image you refer to is NOT from the ITU-T Rec. T.38, it was created by TI. 

    For parsing the pktIn[0]: 09:0a:06:c0:01:80:00:00:f4:00:02:06:c0:01:80:00:00:c8:06:c0:01:80:00:00:ff.

    sequence number : 09:0a:
    ifp size : 06:
    data message : c0:
    data field count : 01:
    data field type : 80:
    length of data field : 00:00:
    data : f4:

    Then, the rest are redundancy packets:

    00: ?

    02: two items

    Item 0: 06:c0:01:80:00:00:c8 (structure as the primary IFP)

    Item 1: 06:c0:01:80:00:00:ff (structure as the primary IFP)

    It is good to have real packets captured by Wireshark and decoded as UDPTL to find those out for reference.

    Regards, Eric

     

  • 0 in reply to lding
    Intellectual 970 points

    hi, Eric

    i just begin to find out how to recieve fax over PSTN using omap processor, i'm running the example from faxlib, how to convert xferpktInfo_t packet to UDPTL packet ? how can i read out the fax file from the packets ?

    thanks!

  • 0 in reply to huang jack
    TI__Guru* 95265 points

    how to convert xferpktInfo_t packet to UDPTL packet

    What inside  xferpktInfo_t doesn't have header information. To convert it into UDPTL packets, you need to add MAC/IP/UDP header in front.

    How to read fax file from the packets:

     Attached is a Fax application note, it is for our voice gateway using Faxlib. But many fax analysis is still relevant, you can look at section 5.3.

    Regards, Eric

    3515.T38_fax_analysis.pdf

     

  • 0 in reply to lding
    Intellectual 970 points

    hi，Eric

    i can parse xferpktInfo_t packet now.

    thanks!

  • 0 in reply to huang jack
    Expert 1610 points
    Hi Guys, Please help me out in understanding the packet parsing for FAX. How do I link each packet with the corresponding debug messages..? Based on what fields the messageId, messageData, supportingData etc are extracted..? We want to move this debug parser function to the host which doesn't do anything else other than parsing the fax packets received from the 55x faxlib. But we are finding it difficult to parse this as it is not documented properly as to which filed in the packet correspond to what. Any help in the issue is appreciated. I have gone through the document attached in this thread and also the image file attached in the other thread. Though they helped me to some extent, I feel there is some more missing links.