Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
AUD328
- Thread starter CraigUK
- Start date
when that agent hung up, the lamp did not go out. might cause a problem in the future, if your using symposium.
the set looks like
the other hex codes are usually speech paths or mem allocation. if the problem happens more then once a day. i would out the phone and rebuild it on a different tn. anything that doesn't look right when your putting it back in, leave it out and ini the switch. i put one back in not to long ago and the switch asked if i wanted to marp the dn, it was an unsed dn, and the tn that the dn was marped to was in the luvu table.. corruption is not anything to ignore.. your problem is usually caused by a single pointer that is not in sync. just don't ignore it if it gets bad
john poole
bellsouth business
columbia,sc
the set looks like
Code:
>ld 32
NPR000
.conv 6414
=> 100 0 05 00the other hex codes are usually speech paths or mem allocation. if the problem happens more then once a day. i would out the phone and rebuild it on a different tn. anything that doesn't look right when your putting it back in, leave it out and ini the switch. i put one back in not to long ago and the switch asked if i wanted to marp the dn, it was an unsed dn, and the tn that the dn was marped to was in the luvu table.. corruption is not anything to ignore.. your problem is usually caused by a single pointer that is not in sync. just don't ignore it if it gets bad
john poole
bellsouth business
columbia,sc
- Thread starter
- #3
- Status