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 Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

RAD port returning Error

Status
Not open for further replies.

KurpeusLondon

Technical User
Apr 14, 2010
119
GB
Hi guys,

I've have an error with a RAD port (4117) returning "error". The system is running MCD 4.1 on 3300 CX II platform.

Locate feature Extension 4117

VM Port : 712
Circuit Location : 1 4 27 3 1
Extension : 4117
Active Features :


State 1 4 27 3 1

Location | Device | State | Owner | ID |Status
----------------------------------------------------------------------------
1 4 27 3 1| Superset 4150 | Out of Service | | |
----------------------------------------------------------------------------

A bit of history: that port was working as Voicemail port until I changed it to RAD. I changed the CoS to RAD ports. I believe it had work for few min (I was testing it by directly dialling the RAD port)

I tried reverting changes back to voicemail port. Not working. I've restarted the voicemail facility (iPVM_Stop/Start) but no joy.


I read somewhere it's best practise to put RAD ports to RAD hunt-groups even if single group member, any thought about that ?

Thanks,

 
Is this a DNIC port becuase I don't think that if you use the embedded voicemail as a RAD's that it gets assigned a set type? A voicemail port needs to be made a set but not a RAD port. It might have been best to blow the port away completely and start from scratch.

I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top