Bug in deleting a route
mattdarnell
Thu, 08/07/2008 - 13:27 | Bug in deleting a route
Currently, when a DID is assigned to an extension and you delete the route, the DID is still associated with the extension.
When you delete a route that is a DID going to an extension, the extension DID should change to 'none'.
-Matt
Thu, 08/07/2008 - 23:50 | Bug in deleting a route
yeah the 2 pages in TL don't interlink, I find DIDs easier to manage if you do it from inbound routes other wise you risk the call going no where and either a fast busy or a number not in service message.
George
Fri, 08/08/2008 - 01:01 | the inbound route page is
the inbound route page is the only one that really counts. The information in the extension page is good for initial creation but thats about it. I dont use the extension area to create my inbound routes directly, but they do get populated when I use the bulk generator, that utility is just too cool.
Erik Smith
CTO
BluegrassNet Voice
dCAP
Fri, 08/08/2008 - 02:27 | I agree it doesn't affect
I agree it doesn't affect functionality, but the code should clean that up, to include if the user was using their DID number for outbound caller-ID etc.
-Matt
Sat, 08/09/2008 - 20:18 | Bug in deleting a route
it should be reflected correctly in both, its not a huge bug and not one that affected the operation of the system but a bug never the less.
to avoid problems set everything in inbound routes until Alex gets around to fixing it..
George
Sat, 08/09/2008 - 20:22 | maybe an easy fix: once the
maybe an easy fix: once the field is populated, dont make it editable, instead make it a link to the inbound route configuration, so that if you want to delete it you just press the delete button.
Erik Smith
CTO
BluegrassNet Voice
dCAP