Thanks Jose.

We actually use DH cipher encryption between our clients and Kamailio and this is production setup so I can't use any other supported types.

I can for sure double check the cpu and memory but generally this server is not heavily used.

Is there anyway for Kamailio to log in the configs memory and cpu usage?

On Wed, Sep 26, 2018 at 5:03 AM José Seabra <joseseabra4@gmail.com> wrote:
Hi Andy,

The server where kamailio is running is not CPU overloaded?  and what about memory consumption?

I would say that if you decode the sip tls packages, it would be more easy to debug the issue.

The link bellow can guide you how to decode SIP TLS packages:

Hope that the information provided can help you.

Regards
José

Andrew Chen <achen@fuze.com> escreveu no dia terça, 25/09/2018 à(s) 07:17:
Hi Kam community,

Facing an urgent issue here and not sure how to troubleshoot it further.

So our engineers been getting reports of unknown SIP timeouts and they suspect it's something on the Kamailio side.  I've logged every transaction from receiving the message to done relaying it as shown below:

Sep 24 18:38:13 sjoprodfnsg01 /usr/local/sbin/kamailio[42608]: INFO: <script>: [1589Fz-ses1-41d9a88aR70125425@xxx.xxx.xxx.xxx][4534123][CSeq 7] NG-FuzeMedia-Server/42ae58c/mediahub Relaying [UPDATE] from (xxx.xxx.xxx.xxx  ) to ( xxx.xxx.xxx.xxx  ) via (tls)
Sep 24 18:38:13 sjoprodfnsg01 /usr/local/sbin/kamailio[42608]: INFO: <script>: [1589Fz-ses1-41d9a88aR70125425@ xxx.xxx.xxx.xxx  ][4534123][CSeq 7] NG-FuzeMedia-Server/42ae58c/mediahub Done relay [UPDATE] from (xxx.xxx.xxx.xxx  ) to ( xxx.xxx.xxx.xxx  ) via (tls)

When I pulled the 443 SIP trace from my tcpdump session, it shows the application data left the machine at 18:44 as shown here:

image.png

Note:  This packet is encrypted and can't see the actual SIP message.

This matches what was received on the client logs:

2018-09-24T18:38:44.032Z [40927] [INF] fuze.sip SipParser.cpp:549 LogSipMessage: xxx.xxx.xxx.xxx:443 - 4292B (local time 09/24 11:38:44)
--------------------
RECEIVE:

UPDATE sips:Luke_Surazski@ xxx.xxx.xxx.xxx:50795;id=37262838;inst=52241254 SIP/2.0 
Via: SIP/2.0/TLS  xxx.xxx.xxx.xxx:443;branch=z9hG4bK15f.5052c318e1766a0a9405f10708f43188.0;i=acbb7 
Via: SIP/2.0/TCP  xxx.xxx.xxx.xxx  :38342;rport=38342;branch=z9hG4bK-55f913-t9-I214262897 

What would cause such delays?

I'm running Kamailio 4.1.5

Thanks.

--
Andy Chen
Sr. Telephony Lead Engineer
415 516 5535 (M)


*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.*_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users


--
Cumprimentos
José Seabra
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users


--
Andy Chen
Sr. Telephony Lead Engineer
415 516 5535 (M)


*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.*