dial 1888xxxxxxx goes straight to voicemail

[modulistic]

3300 upgraded last night to 9.whatever

1800xxxxxxx works fine. I set up a digits dialed entry for a specific 1888 number and it still goes to voicemail. I did a digit modification and created a whole new route just for 1888 that absorbed all 12 digits and inserted a specific 1888 number and it still goes to voicemail.

it was working fine before the upgrade last night

 

[modulistic]

The system restore to a previous backup seems to have fixed the problems. Im going to wait to switch the t1 protocol variant back from dms100 to ni2 bellcore after the system has been stable for a few days.

hopefully whatever messed up the database (if thats what it was) isnt present anymore. Ill know pretty soon.

 

[paterson]

Mitel has an FTP site for uploading files if needed. They can provide you with details for that. Glad to hear that restore worked.

 

[modulistic]

you and me both. mostly me.

Thanks for putting up with my frustration and cussing and bitching and moaning.

 

[modulistic]

changed back to NI2 and immediately couldnt make 1888 calls. now caller ID name display wont work.

does anyone know why it is doing this?

 

[modulistic]

the switchback to DMS-100 protocol seems to have corrupted the data again.

now random stations cant make local calls even though the only change we made was to the protocol.

we are going to restore to backup tonite.

 

[Lundah]

Why are you changing the ISDN protocol? That seems to be the source of your trouble, not the database.

 

[modulistic]

because when it is set for dms100, caller id number will pass through to the sets but not called name.

when it is set for ni2/bellcore caller id name and number will pass through to the sets.

 

[Lundah]

What's on the other end of the circuit? If it's a telco switch, you normally can't just change the protocol without the carrier also changing something on their end as well.

 

[modulistic]

the other end of the pri is my co. it is a dms10 switch. ive changed back and forth several times without my CO guy having to do anything. it works fine for a few days and then the database starts to corrupt.

 

[Lundah]

That sounds fishy to me, I've never run across a situation where changing the ISDN protocol, particularly between different vendor types, doesn't require a change on the carrier side as well.

Just to prove out the 3300, I'd recommend making a backup, re-loading the software manually using the "FixPartition" flag, and restoring the system. Then, if you like, try your protocol change again and see if anything changes.

 

[nytalkin]

I might suggest a backup and restore of the current cnfg. If you have corruptions this should cure it. Do you have any software log entries when this 1888 number is dialed?

NO GOOD DEED GOES UNPUNISHED!

 

[GX5Krocks]

what database is corrupt? Are you saying that you have a database alarm? that is the key to knowing your db is corrupt. or are you speculating on this? Agreed that changing protocols with no intervention on co side makes zero sense. You sure do have a patient customer to work with on this issue. Is this a nsu or emb framer for the isdn? what about your internal dialing problems, are they too related to the CO? does your smdr show you going external when you have failures?

 

[modulistic]

I dont know what to say lundah, I can freely switch back and forth between the two protocols. Im going to have to wait on the fix partition flag until I can get some scheduled downtime at the hospital.

nytalkin. whenever we start to get problems with the NI2 protocol, we switch it back to dms100 and do a database backup. the dialing problems solve themselves. the only logs and output I know how to do I have posted in this thread.

gx5krocks. Mitel suggested the database is corrupt. there is no database alarm. I guess you can say im speculating on this, because its what mitel told me. you are right I have a patient customer. its the mindset of the whole island I live on that everything takes time and if you expect things to get done ASAP, you will be very dissapointed.

this is not an nsu, its a dual embedded framer.

I have no idea about the internal dialing problems. I havent been thinking about this situation for a few days, Ive had other fires to put out.

thanks