After playing around with it, I found the issue. Turns out it was the way
I was capturing the pcap file. Each of the RTP packet has encapsulation
type of "NULL". Took me a while to find out that I can't capture through a
VPN tunnel. After recreating the pcap without VPN, the error went away.
Thanks again for your response.
On Thu, Oct 6, 2016 at 11:02 PM, Šindelka Pavel <sinde...@ttc.cz> wrote:
> Hard to say without the original file and the command line you've used to
> run editcap.
>
> P.
>
> Omlouvám se za stručnost, píšu z mobilu.
>
> Pavel Šindelka
>
> Dne 6. 10. 2016 10:53 odpoledne napsal uživatel Andy Chen <ac...@fuze.com
> >:
>
> Hi,
>
> I have a SIPP platform that's setup to add members to a conference
> platform and then play a pcap file. I used Wireshark to create a pcap file
> with RTP codec type of G.722. I noticed the first time when I ran it, I
> got the error stating something about "unsupported link-type of 0". Then I
> used this tool editcap to set it to Ethernet link-type but now I got this
> error message:
>
> Unsupported ethernet type 15889.
>
> I'm currently at a loss on how to get this pcap file to work with my sipp
> configuration.
>
> Any advice would be appreciated.
>
> Thanks.
>
> --Andy
>
>
>
--
Andy Chen
Sr. Telephony Lead Engineer
415 516 5535 (M)
ac...@thinkingphones.com
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Sipp-users mailing list
Sipp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sipp-users
