[asterisk-bugs] [JIRA] (ASTERISK-24548) duration of the call in error callback. Can't send 10 type frames with SIP write

[Rusty Newton (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-24548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=223945#comment-223945 ] 

Rusty Newton commented on ASTERISK-24548:
-----------------------------------------

Can you demonstrate via logs and dialplan where you get an incorrect call duration?

I'm not sure on the relation of the noted warnings to your call duration issues.

Frame type '10' corresponds to a Comfort Noise frame, likely sent by one of the SIP peers involved in the conference.

In general, comfort noise is not fully supported by Asterisk. You may want to turn off comfort noise generation on the peers and see if that alleviates this issue.

> duration of the call in error callback.  Can't send 10 type frames with SIP write
> ---------------------------------------------------------------------------------
>
>                 Key: ASTERISK-24548
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24548
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>    Affects Versions: 13.0.1
>            Reporter: danilo borges
>            Assignee: danilo borges
>         Attachments: myDebugLog, sip.conf
>
>
> We have an error callback call duration in which he did not charge the second link (551138223465) and marks the time to 0. And it floods the cli with the error: 
> {noformat}
> [Nov 25 09:16:01] WARNING[2595][C-00000001] chan_sip.c: Can't send 10 type frames with SIP write
> {noformat}
> Remembering that this link via callback is made directly to PSTN lines (not using ATA devices). The same configuration does not affect the asterisk 11 where normally use without error call duration and without error warnings. Attached hereto debug. From already thank you very much.



--
This message was sent by Atlassian JIRA
(v6.2#6252)