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!

Register Log in
  • Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

NAM OUTDIAL- B1 and B2 1

Status
Not open for further replies.
BagsNYC

BagsNYC

Vendor
Sep 25, 2002
411
US
I am trying to build restrictions on what my NAM is allowed to dial on Message Notification and Outbound Transfer(option 7 transfer from user mailbox). While testing the Message Notification portion on our live system, I left a voicemail message and watched the system dial out (using our pool A lines which I assigned to my set) to engage the notification. When I identified the line button that the NAM was dialing out on, I noticed a "oddball" numbered extension . Upon further review, I found that the B2 DN of the NAM's Main DN(F985) was doing the outdial for notification. When I attempted to restrict that DN, it did not come up in my programmable extension range. Any ideas on the technical reason behind this and how I can work around this??

My second part of this issue is when the "option 7" is dialed while in a mailbox message session, is the outdial considered to be running through the NAM or the set where the outdial is being initialized?

 
Sort by date Sort by votes
Norstar Voice Mail 3.0 allowed you to place set restrictions on the primary DN (f985) of the Voicemail, applying the set restrictions to all of the B1's and B2's is not necessary.
I have not found this to be the case on subsequent releases of Norstar Voice Mail but this was a documented feature in 3.0 NVM.
Option 7 is considered a conference transfer unless the hook flash transfer option is used.
It does not use an additional DN for the transfer.

David Brillert
 
Upvote 0 Downvote
aragon,

I ran a test, placing a full set restriction(tested after creation and applied to my phone set)on F985 extension, and the call was completed to my pager, which notified me as it always does.

Again, I believe there is something significant with the fact that the B2 match to my F985 extension is the one displayed when the system is dialing out.

Voicemail running on 4.0 SW with MICS 5.0 and very vanilla setup(no bells and whistles).
 
Upvote 0 Downvote
This confirms my understanding that the ability to restrict voice mail channels disappeared after 3.0.
Try applying the restrictions to all of the B1 and B2 DN's on the voicemail and post the results.

David Brillert
 
Upvote 0 Downvote
aragon,

Will do so tomorrow, but again the B2 match to the F985 B1 is not accessible in Programming mode..
 
Upvote 0 Downvote
Here are test results, on 4-channel 8-port NAM. Again, 5.0 MICS with 4.0 NAM. Don't be confused by oddball B1 DN range; they have been changed in the "Change DN" programming field..

System Port B1 DN B2 DN
----------- ----- -----
401 7014 7176
402 7016 7177
403 7028 7178
404 7051 7179

Built restriction filter and tested at working station. Applied as set restriction to all NAM B-1 DN's. Proceeded to leave message on my set, which outdialed and notified without issue..

Ideas????
 
Upvote 0 Downvote
Come on MVP's, I know someone out there has to have run into this issue..
 
Upvote 0 Downvote
Interesting thread....
Never considered the B2 channel not using the restrictions associated with B1.

Please Dave, check the CP when you have a moment
 
Upvote 0 Downvote
Yes, very interesting telemarv..

I am pulling my hair out over this one. Trying to find a way to restrict hacking outdial. Have no issues with copper, but because PRI has limitations on what can be restricted for this customer, I went on the NAM hunt.

We removed a few lines from the outbound copper pool and fully restricted lines, then allowed nessage notification and option 7 transfers from user's mailboxes by overriding the exact number to be dialed.
 
Upvote 0 Downvote
Restricting lines will work but that means you have to dedicate lines to outdial... not very cost effective.

Here's a thought... try restricting the B1 DN then do a DN swap (Change DN B1 to B2) then restrict the new B1 DN (which is actually the old B2 DN). Does it hold the restrictions when you change DN's?
 
Upvote 0 Downvote
Will give that a try telemarv..

Here's another weird test outcome;

I hooked up with a 6.1 MICS and 4.1 NAM. Set up mailbox and tested message notification for phone and pager. Each time the call went out over the B1. Good thing, right? At least a difference from the 5.0/4.0 I have been testing with.

Here's the catch; When I attempted to place a restriction on the B1 outdial, allowing override for pager/cell, teh calls started routing thru the B2..Crap....

Will try your test and re-post..

Thanks for your imput..
 
Upvote 0 Downvote
Checked with Nortel on this one.
They were absolutely useless.
Unaware of problem.
Unaware of documented feature in 3.0 NVM
They were unable to reproduce.
Closed my ticket while I was on vacation.
Pathetic tech support.

David Brillert
 
Upvote 0 Downvote
Not to be retreading over facts here but you have gone under the F983, MBOX, and set the outdial to none: right?

And you can still remotely go into the F981 mailbox admin settings and program the box to transfer a call to a phone? If under the mbox it's set to outdial: none then it is supposed to only offer the notification to an internal DN number.

MRoberts
 
Upvote 0 Downvote
Gents,

The issue here is simple:
In 3.0 NVM one only needed to apply a set restriction to the primary DN of the NVM (not to all channels).
This feature was removed in 4.0 NVM.
NVM is now discontinued.
Nortel support is useless and unlikely in this case.
Perhaps this works in CallPilot or will be addressed in the future but this is also unlikely.
I won't be testing this on CallPilot any time soon but if anyone else has the patience I am interested in the results.
I have already wasted three days with Nortel on this.

David Brillert
 
Upvote 0 Downvote
The reason I asked is that the documentation for 4.0 and 4.1 still says that restrictions for outdialing are appiled to the DN assigned to the mailbox or on the beginning DN of the vmail.

Melissa

MRoberts
 
Upvote 0 Downvote
Melissa,

Definetly proved that the restrictions do not apply to the Vmail DN B1 or B2 channel. Also proved that the results varied from software versions on both the MICS and NAM.

I am not looking to have outdial completly turned off, just to restrict any dialing opposed to allowed dialing.
 
Upvote 0 Downvote
One last retread ..... you did apply the restriction filter to the B1 DN assigned to the mailbox and then tested, yes?

If yes, then tomorrow, I will set it up on our bench with both the NAM and CallPilot.

MRoberts
 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

Michael.D
  • Locked
  • Question
Norstar and Meridian PBX spare cards/parts
Replies
5
Views
260
curlycord
curlycord
puttwill
  • Locked
  • Question
Music on Hold stopped working after storm and trunk card replacement
Replies
7
Views
289
curlycord
curlycord
wardy5
  • Locked
  • Question
Customer called and said Ext. 21 us 1
Replies
8
Views
229
curlycord
curlycord
tclubb
  • Locked
  • Question
MICS w/PRI. Karis Law and Ray Baum
Replies
2
Views
140
curlycord
curlycord
gmupilot
  • Locked
  • Question
different voice mail messages and flows for different lines
Replies
8
Views
244
phoneguy427
phoneguy427

Part and Inventory Search

Sponsor

Back
Top