| Summary: | ASTERISK-09132: error response on INFO kills call | ||
| Reporter: | Vadim Berezniker (kryptolus) | Labels: | |
| Date Opened: | 2007-03-28 12:43:39 | Date Closed: | 2007-04-09 11:50:28 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | ASTERISK => GATEWAY: INVITE ASTERISK <= GATEWAY: 100 Trying ASTERISK => GATEWAY: INFO ASTERISK <= GATEWAY: 481 Call Leg/Transaction doesn't exist (in response to info) At this point, Asterisk assumes the 481 is in response to the INVITE and ends the call (The call is still making progress on the gateway). There are two issues, it seems. Asterisk is sending out the INFO before the call is established and it cancels the call when it shouldn't. | ||
| Comments: | By: Serge Vecher (serge-v) 2007-03-28 13:13:20 As per bug guidelines, you need to attach a SIP debug trace illustrating the problem. Please do the following: 1) Prepare test environment (reduce the amount of unrelated traffic on the server); 2) Make sure your logger.conf has the following line: console => notice,warning,error,debug 3) restart Asterisk with the following command: 'asterisk -Tvvvvvdddddngc | tee /tmp/verbosedebug.txt' 4) Enable SIP transaction logging with the following CLI commands (1.4/trunk commands in parenthesis): set debug 4 (core set debug 4) set verbose 4 (core set verbose 4) sip debug (sip set debug) 5) Reproduce the problem 6) Trim startup information and attach verbosedebug.txt to the issue. By: Serge Vecher (serge-v) 2007-04-09 11:50:28 closing as duplicate, as kryptolus has a patch in 9492 that fixes this | ||