[asterisk-users] 1.8.7.0 crashing : Can't send 10 type frames with SIP write

[Terry Wilson]

----- Original Message -----
> From: "sean darcy" <seandarcy2 at gmail.com>
> To: asterisk-users at lists.digium.com
> Sent: Friday, November 11, 2011 11:26:37 AM
> Subject: [asterisk-users] 1.8.7.0 crashing : Can't send 10 type frames with SIP write
> With asterisk 1.8.7.0 has been running ok for months. Now, this
> morning,
> it's crashing. I can restart it, but it crashes after 10+ minutes.
> 
> It dies like this
> -- Executing [s at macro-stdexten:2] Dial("SIP/teliax-00000019",
> "SIP/176,18,rtT") in new stack
> == Using UDPTL TOS bits 184
> == Using UDPTL CoS mark 5
> == Using SIP RTP TOS bits 184
> == Using SIP RTP CoS mark 5
> -- Called SIP/176
> -- SIP/176-0000001d is ringing
> -- SIP/176-0000001d is ringing
> [Nov 11 12:04:08] WARNING[24072]: chan_sip.c:6433 sip_write: Can't
> send
> 10 type frames with SIP write
> [Nov 11 12:04:08] WARNING[23780]: chan_sip.c:8740 process_sdp:
> Unsupported SDP media type in offer: video 0 RTP/AVP 26 31 34 98 99
> 104
> -- SIP/176-0000001d answered SIP/teliax-00000019
> [Nov 11 12:04:09] WARNING[24072]: chan_sip.c:6433 sip_write: Can't
> send
> 10 type frames with SIP write
> [Nov 11 12:04:09] WARNING[24072]: chan_sip.c:6433 sip_write: Can't
> send
> 10 type frames with SIP write
> [Nov 11 12:04:13] WARNING[24072]: chan_sip.c:6433 sip_write: Can't
> send
> 10 type frames with SIP write
> [Nov 11 12:04:13] WARNING[24072]: chan_sip.c:6433 sip_write: Can't
> send
> 10 type frames with SIP write
> [Nov 11 12:04:14] WARNING[24072]: chan_sip.c:6433 sip_write: Can't
> send
> 10 type frames with SIP write


If it is really crashing, then you need to open an issue and use the information here: https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace to submit a backtrace. The WARNINGS above seem to be about CNG frames and a Video offer with port 0 meaning (I think) that the other side is stating that they won't accept video. I would think that they would respond this way most often if you were offering video, but with out seeing sip debug output there is no way to tell. Go ahead and add sip debug output to your issue to if you open it. Neither of the WARNINGS are indicative of anything particularly bad happening, so the crash may be completely un-related.

Terry