Dialplan Analysis

[billdads]

Hello,

Strange one, but I'm out of ideas and looking for help.

We are adding more extension ranges to our system here. I entered in the new ranges into the dialplan analysis form ready for when they are presented. I don't know whether I'm just unlucky, but since then any calls to our main number which is a VDN to vector to LDN is not working.

I have used the 'list trace vdn ****' and the system isn't seeing any calls. When you call the number you get 'sorry, this service is no longer avaiable'. I receieved denial messages 10407/12332 when I wasn't allowed to alter the table.

I did not delete any of the dialplan and my understanding is that anything must be in the dialplan before it can be administered, so i don't think I have overwritten anything.

All other DDI's are fine, ist just the main VDN. I have double checked the analyis and everything is there as it should be.

The only other thing, is that a collegue deleted the postmaster mailbox out of MM, but i don't see how that can effect it

I have logged a call with the maintainer who has logged a call with our network provider.

Just seems very odd that a newtork issue has happenned, just as I try to change the dialplam

If anybody has any suggestions, they are most welcome.

 

[AvayaTier3]

Contact a professional for help, ASAP

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

37 years Bell, AT&T, Lucent, Avaya
Tier 3 for 27 years and counting

http://bshtele.com

 

[AvayaTier3]

If you do not know what the dialplan looked like before your changes, and you did not do a save translations, a reboot will put it back like it was.

Not sure if that's an option for you, but may be the quickest way to recover.

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

37 years Bell, AT&T, Lucent, Avaya
Tier 3 for 27 years and counting

http://bshtele.com

 

[billdads]

AvayaTier3

Thanks for replying

Our provider has come back and said it is a problem a network level with the SIP.

I was getting paranoid that I had messed something up, but as i said i didn't delete anything and went all over the system and couldn't find anything out of place with the changes I made.

The VDN works fine internally too

So hopefully its just a coincidence.

 

[AvayaTier3]

A good habit to get into:
Make copies for system changes before and after so changes can be easily backed out.

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

37 years Bell, AT&T, Lucent, Avaya
Tier 3 for 27 years and counting

http://bshtele.com