[asterisk-bugs] [Asterisk 0011982]: Can not register 2 different SIP accounts with provider

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11982 
====================================================================== 
Reported By:                aussie_troll
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   11982
Category:                   Channels/chan_sip/Registration
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.17 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             02-12-2008 16:43 CST
Last Modified:              02-13-2008 01:03 CST
====================================================================== 
Summary:                    Can not register 2 different SIP accounts with
provider
Description: 
with two different SIP accounts with one provider, system will not register
either. By dropping one of the accounts, the other registers with no issue.
 This issue began with Asterisk V1.4.14. Is repeatable with versions 1.4.17
and 1.4.18.


====================================================================== 

---------------------------------------------------------------------- 
 aussie_troll - 02-13-08 01:03  
---------------------------------------------------------------------- 
well, all i can say on that is...

with only one sip registration everything works.  when i add the second it
breaks.  this was not an issue in v1.4.13, but became one and is still one
with v1.4.14 onwards.  I know of another person here in australia having
the exact same issue.

and it would stand to reason if one channel is registering properly then
it would not be a firewall issue (note i have double and triple checked my
port forwarding on the firewall, and have made no changes since being able
to run the v1.4.13 successfully.)