[SR-Users] siptrace not sending data to hepic

Andrew Chen achen at fuze.com
Wed Jul 1 21:48:54 CEST 2020


Hi all,

I've been assigned a task to investigate why hepic doesn't generate MOS
scores ever since we changed the kamailio interface MTU from 9001 -> 1500.

During my investigation, this is what I have found out so far:

- Putting MTU back to 9001 removes this condition where no MOS was
generated.
- I did a tcpdump of port 9063 which is the port used to send data to Hepic
capture server and saw it reports packets are fragmented:

3:48:55.895505 IP (tos 0x68, ttl 64, id 38049, offset 0, flags [+], proto
UDP (17), length 1500)
  206.81.181.40.5060 > 10.225.88.239.9063: SIP
13:48:55.896451 IP (tos 0x68, ttl 64, id 38050, offset 0, flags [+], proto
UDP (17), length 1500)
  206.81.181.40.5060 > 10.225.88.239.9063: SIP

- Hepic support also caused by using 1500 MTU on the interface.
- I tried using the following core parameters to see if they could remedy
this issue but didn't seem to work:

## MTU related core settings

udp4_raw=-1

udp4_raw_mtu=1500


I can't seem to find any parameters in the siptrace module that controls
fragmentation of the packets to Hepic.

Any suggestions on how else to troubleshoot this?

Thanks.

-- 
Andy Chen
Sr. Telephony Lead Engineer
achen@ <achen at thinkingphones.com>fuze.com

-- 
*Confidentiality Notice: The information contained in this e-mail and any

attachments may be confidential. If you are not an intended recipient, you

are hereby notified that any dissemination, distribution or copying of this

e-mail is strictly prohibited. If you have received this e-mail in error,

please notify the sender and permanently delete the e-mail and any

attachments immediately. You should not retain, copy or use this e-mail or

any attachment for any purpose, nor disclose all or any part of the

contents to any other person. Thank you.*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-users/attachments/20200701/1f4ef3e6/attachment.html>


More information about the sr-users mailing list