Summary:ASTERISK-04420: Multiple INVITE's
Reporter:Lawrence (finejava)Labels:
Date Opened:2005-06-16 06:16:49Date Closed:2011-06-07 14:10:34
Versions:Frequency of
Environment:Attachments:( 0) nat-to-PPPoE
Description:I've made a comparison test between * and SER. I've found out that...* always sends multiple INVITES...and SER only sends 1 INVITES...

Another problem is...* always include the internal WAN IP in the Connection Information where it suppose to publish the WAN IP...thru my anaylsis...it's always the 3rd INVITE that gives ALL the correct information...

Is there anybody out there who have solves this problem...or is there anyway that we can make it 1 INVITE and Connection Information which displays the WAN IP


Attach is the ethereal traces on *
Comments:By: Michael Jerris (mikej) 2005-06-16 07:30:16

comparing asterisk to ser is not a good comparison as ser is a proxy and asterisk is not.  If you can note anything specific asterisk is doing that breaks an rfc, or does not work, please say so.

By: Kevin P. Fleming (kpfleming) 2005-06-21 19:46:43

Ditto on what MikeJ said..

Also, you would need to test against the latest CVS STABLE or CVS HEAD versions to confirm that any possible problems have not already been fixed.

Your 'multiple INVITE' situation is probably because you have 'canreinvite' enabled... When this is enabled, Asterisk will send an initial INVITE to set up the call, then one (or two) more to get the media path redirected between the peers.

If you have specific details of something that Asterisk is doing wrong, please open a bug with those details (and review the bug posting guidelines so you know how and what to test and trace before posting).