[Asterisk-bugs] [Asterisk 0009921]: 1.4.4 sends Re-INVITE twice, resulting in code 491 "Request pending" and call termination by Asterisk
noreply at bugs.digium.com
noreply at bugs.digium.com
Mon Jul 2 09:49:08 CDT 2007
email_notification_title_for_action_bugnote_submitted
======================================================================
http://bugs.digium.com/view.php?id=9921
======================================================================
Reported By: fabianhoppe
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 9921
Category: Channels/chan_sip/Interoperability
Reproducibility: always
Severity: major
Priority: normal
Status: feedback
Asterisk Version: 1.4.4
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Disclaimer on File?: No
Request Review:
======================================================================
Date Submitted: 06-08-2007 04:42 CDT
Last Modified: 07-02-2007 09:49 CDT
======================================================================
Summary: 1.4.4 sends Re-INVITE twice, resulting in code 491
"Request pending" and call termination by Asterisk
Description:
Dear All,
I'm using Asterisk v1.4.4 with the lastet patch level (as of 27.04.07).
Several Polycom phones in a remote location are connected to the Asterisk
server via the Internet with IPCoP and siproxd 0.5.13 serving as outbound
proxy. All outbound traffic is routed via SIP to a local SIP provider,
running a TELES iSwitch as softswitch. My sip.conf is listed below under
"additional information". In this setup I run into the following,
reproducable problem:
When I place an outbound call, the call setup works fine and the reinvites
take place, RTP streams a setup between the Polycom and the SIP provider
directly.
Placing the call on HOLD then results in a re-invite to the SIP-provider
who answers with "100 trying".
Immediately Asterisk resends an identical re-invite (with an incremented
CSeq), resulting in a "491 Request Pending" from the SIP provider (this is
the correct answer, as the first INVITE is not yet fully processed).
This gets acknowledged by Asterisk and then Asterisk simply terminates the
call!!
You can find the SIP DEBUG output from the Asterisk server as attachment.
I can provide a wireshark capture on request. Please let me know, if more
data / logs are needed.
======================================================================
----------------------------------------------------------------------
file - 07-02-07 09:49
----------------------------------------------------------------------
Any update with this? Been a few weeks.
Issue History
Date Modified Username Field Change
======================================================================
06-08-07 04:42 fabianhoppe New Issue
06-08-07 04:42 fabianhoppe Issue Monitored: fabianhoppe
06-08-07 04:42 fabianhoppe File Added: trace failed reinvite.txt
06-08-07 04:42 fabianhoppe Asterisk Version => 1.4.4
06-08-07 04:42 fabianhoppe SVN Branch (only for SVN checkou => N/A
06-08-07 04:42 fabianhoppe Disclaimer on File? => No
06-08-07 05:13 fabianhoppe Note Added: 0064803
06-08-07 10:32 file Note Added: 0064819
06-08-07 10:32 file Status new => feedback
======================================================================
More information about the Asterisk-bugs
mailing list