[asterisk-bugs] [Asterisk 0015106]: Routing Extensions between 2 asterisk servers in 2 directions fails with "482 Loop Detected"

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15106 
====================================================================== 
Reported By:                timeshell
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   15106
Category:                   General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           1.6.0.9 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-05-14 09:35 CDT
Last Modified:              2009-05-15 21:29 CDT
====================================================================== 
Summary:                    Routing Extensions between 2 asterisk servers in 2
directions fails with "482 Loop Detected"
Description: 
A* has a user created by asterisk-gui2.
B* has a trunkA created to connect to user on A*.
Calling rule for trunkA on B* allows exts connected to B* to call exts on
A*.

Now, I want exts connected to A* to be able to call exts on B*.

Scenario 1
Create SIP trunk user on B* with asterisk-gui2.  Connect trunk from A* to
user on B* and appropriate outgoing rule.
Result:  calls from one or both sides will get error in CLI reporting "482
Loop Detected"

Scenario 2
Create SIP trunk using asterisk-gui2 on A* but leave hostname, username
and secret blank.  Change registersip to = no.
Manually edit extensions.conf and change the global for the new SIP trunk
to be something like "trunk_1=SIP/A*Ext" where A*Ext is the trunk extension
for B* to connect a trunk to A*.
Create outgoing rule on A* to route B* exts to B*.
Create incoming rule on B* to accept incoming calls on trunk to A* and set
it to route to ${EXTEN}.
Result:  Calls may or may not work in one direction and the other
direction will not work reporting "482 Loop Detected"


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

---------------------------------------------------------------------- 
 (0104878) timeshell (reporter) - 2009-05-15 21:29
 https://issues.asterisk.org/view.php?id=15106#c104878 
---------------------------------------------------------------------- 
I've discovered part of the problem.

I discovered that when I first create a trunk and apply changes through
the gui, the trunk works.  When I subsequently edit and save, even if I
haven't made changes, and then apply changes, it stops working.  I further
have discovered that the change that occurs in the trunk configuration that
is preventing it from working is the "outbound proxy=" setting.

The interesting thing is however, the only way I was able to determine
this was by removing the setting "outbound proxy=" and unloading
chan_sip.so and reloading it.  Just doing a usual reload from the CLI
didn't work.  This is what hampered my previous attempts to troubleshoot as
I tried removing the settings one by one before by only reloading rather
than unloading the module.

So, in short, this may be a issue with the gui, at least in part. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-05-15 21:29 timeshell      Note Added: 0104878                          
======================================================================