HI All
not sure whether this has already been discussed but i have recently come across a situation where we had to delete an extn/user which was a member of a huntlist. what we noticed from the asterisk console that incoming call to that huntlist is still trying to ring that extn/user which is not there (as it has been deleted) so the call ends up hitting "invalid extn"
has anybody already experienced this issue, how do we fix it ?
that was not my question :) ,
that was not my question :) , "fixing it" meant fixing the extn deleting script in thirdlane.
have already deleted the extn from huntlist.
this issue was reported to us by our customer as "all phone lines are down" . our customer deleted one of their extn which was unfortunately member of a huntlist. so their main line stayed down until we we fixed it manually.
thats why you shouldnt be
thats why you shouldnt be using extension based ring groups, you should be using device based ring groups. The method for making a ring group in asterisk has always been Dial(SIP/100&SIP/101&SIP/102,30). Trying to call Local/101 gets your caller answered by things like VM and other problems such as the invalid extension recording. There is no reference link between the extension and other objects that call on it. Perhaps in the future we can place object locks, not to remove them from the huntlist but more of a "hey idiot, you cant delete this extension till you remove it from A,B,C first" kind of lock.
this still wont prevent getting that error entirely. Someone can mis-key the 'other numbers to dial' section and cause the same exact problem.
delete it from the huntlist, duh