[asterisk-bugs] [Asterisk-GUI 0015069]: Some trunks in gui doesnt show registered in the gui, but shows in registered in CLI.

[Asterisk Bug Tracker]

The following issue has been CLOSED 
====================================================================== 
https://issues.asterisk.org/view.php?id=15069 
====================================================================== 
Reported By:                aford
Assigned To:                awk
====================================================================== 
Project:                    Asterisk-GUI
Issue ID:                   15069
Category:                   Service Providers/Trunks
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     closed
Asterisk GUI Version:       2.0.4 
Asterisk Version:           1.4.18 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!): 4776 
Disclaimer on File?:        N/A 
Request Review:              
Resolution:                 won't fix
Fixed in Version:           
====================================================================== 
Date Submitted:             2009-05-08 14:57 CDT
Last Modified:              2009-07-13 09:59 CDT
====================================================================== 
Summary:                    Some trunks in gui doesnt show registered in the
gui, but shows in registered in CLI.
Description: 
Similar to tkt = 0014568 
Asterisk/1.4.18.1
Asterisk GUI-version : SVN-branch-2.0-r4776

It seems that when the host address in the trunk has an upper case letter
the gui always shows  it as "Unrecognized Trunk" even though it does
register in the CLI


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

---------------------------------------------------------------------- 
 (0107642) awk (manager) - 2009-07-13 09:59
 https://issues.asterisk.org/view.php?id=15069#c107642 
---------------------------------------------------------------------- 
aford,
Its recommended that all trunk names be lowercase. And while this might be
advantageous to eventually move away from that, its simpler for the code
that it remain all lowercase. Not the best reason, I know, but hopefully as
the project progresses we'll adopt that methodology across the whole
project. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-07-13 09:59 awk            Note Added: 0107642                          
2009-07-13 09:59 awk            Status                   assigned => closed  
2009-07-13 09:59 awk            Resolution               open => won't fix   
======================================================================