Dear Team, We have further analyzed the case. It seems that Sems was crashing as it was getting multiple m lines in "183 session progress". Sems stopped crashing once we blocked traffic from provider which was sending such traffic. We are still not sure if it was actual reason of issue but we are able to keeps Sems up and running :)
v=0 o=WC-UK-MSC-2 3678234567 3671234567 IN IP4 x.x.x.x s=sip call c=IN IP4 y.y.y.y t=0 0 m=audio 23648 RTP/AVP 101 0 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=rtpmap:0 PCMU/8000 a=sendrecv m=audio 23668 RTP/AVP 8 101 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 regards, Yasir From: Yasir Siddiqi Sent: Wednesday, July 27, 2016 1:20 PM To: [email protected] Subject: sems segment fault Dear team, We are facing crash on sems. Please check attached file. Sems is running as sbc and transcoding opus to g711 codec. When we start sems, it work fine for some time (2 to 5 mins) and then crashes. Work fine means it process calls, media and transcoding successfully 2 to 5 minutes before crashing. Best regards, Yasir
_______________________________________________ Sems mailing list [email protected] http://lists.iptel.org/mailman/listinfo/sems
