[asterisk-bugs] [JIRA] (ASTERISK-21955) [patch] Asterisk responds 488 to session timers re-Invite in an active T.38 dialog after exactly 5 seconds

[Joshua Colp (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-21955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joshua Colp updated ASTERISK-21955:
-----------------------------------

    Affects Version/s: 13.18.4

> [patch] Asterisk responds 488 to session timers re-Invite in an active T.38 dialog after exactly 5 seconds
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-21955
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21955
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/T.38
>    Affects Versions: 1.8.22.0, 13.18.4
>            Reporter: i2045
>         Attachments: Asterisk_1.8.22.0_T.38_488_sip-conf_relevant.txt, Asterisk_1.8.22.0_T.38_488.txt, t38_session_timer.patch
>
>
> 192.168.5.1 LAN IP address of client A
> 44.55.66.77 WAN IP address of client A
> 11.22.33.44 SIP proxy server
> 88.99.11.22 Asterisk 1.8.22.0 server
> 33.55.77.99 SIP server of client B
> 22.44.66.88 Media gateway of client B
> - A call (G.711 alaw) is initiated by client A to client B.
> - Client A re-Invites to T.38, Asterisk relays this re-Invite, client B accepts.
> - Client B re-Invites (line #502). The only difference with the 200 OK that client B sent earlier (line #404) is the Session-Expires header. Asterisk responds immediately with "100 Trying" and "488 Not acceptable here" after exactly 5 seconds.
> - The call is then re-Invited back to G.711 alaw and the fax fails.
> Seems a similar problem as reported in 2010:
> https://issues.asterisk.org/jira/browse/ASTERISK-15596?focusedCommentId=162618&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-162618
> Does someone know why the second re-Invite is answered with a 488?



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