Outbound xfr problem on MICS 6.1/NAM w/PRI

[Phonehed]

For some reason I don't even get the option to specify "route" (instead of line or pool) when programming the mailboxes for outbound capability.

I was told I might get around the problem by telling it to use a non-existent line or pool but that didn't work.

Tried to define a specific line for outbound but that didn't work either.

Double checked user mailbox settings for outbound transfer, no trouble found there.

Checked sets & vmail prime dn for line redirect capability.

Tried with and without the PRI access code (9).

(Lines 1-23 are the only lines of any kind on the system).

Callers are getting vmail message and dialing 7 to transfer out as instructed yet the call fails everytime.

Apparently it was working as recently as a few months ago and no changes have been made since then that we know of.

Anybody else ever run into this?

Phonehed in Dallas

 

[Crowtalks]

If this is a Call Pilot, then get into it via laptop and check that the Class of Service the mailboxes are set to allows outbound transfer

 

[Crowtalks]

You can't tell it to use a particular route, the routing is built and told which line pool to use at the routing level.

You should be using PRI-A line pool.

Lines 1-23 are members of the PRI.

Somebody, somewhere has made some change, most likely but it is also likely that if they realize they screwed something up, they will never admit it.

 

[hawks]

What happens when you try it? Do you get a message saying "you have tried to enter a line or line pool however......." or do you get something else?

 

[cook1082]

There is a selection for routes/pool or line.It depends on the voice mail release.Older only get pool/line.
What kind of VM is this.

 

[cook1082]

I found this trouble shooting tip that is for message notification but the same applies for outbound trans.

Manually dial the beeper number make note of exact digits needed and how long it takes beeper company to answer.
Program a digit 9 in front of digits only if lines are centrex or PRI and destination code is 9.
Feature 915 Channel Status is useful to see if Voice Mail is seizing a line. It will also identify the line number being used.
If Off-premise Message Notification was working rebooting the voice mail may correct. This is characterized by the voice mail not seizing a line. If rebooting corrects increase the number of channels for outdialing under Feature 983 hidden code 5.
If the voice mail seizes the line but does not dial digits check restriction filter on voice mail DN

 

[Phonehed]

Thanks all...I haven't been back out there in a few days now but (as indicated in the subject line) we're talking about a NAM based Mod Plus voice mail system.

On one attempt, I do recall getting a "not available" indication on a Norstar display when attempting to call out and back in, then dialing 7 for ob xfr. If I'm not mistaken I had defined line 12 as the ob line when that happened.

On most attempts the call just fails to transfer out as far as I can tell.

When prompted for pool, I figured I needed to enter 1 (because there's only one pool in the system, PRI-A, destination code 9 or 9any?).

I'm probably going back out there tomorrow and I'm going to have a little more time to dive in deeper this time. It may just be somethin' stupid.

I don't recall checking the restriction filters for the prime vm dn.

I'm using service class 1 on the mailboxes in question and that may be part of the problem too.

If anyone can think of anything else I might check, I'm all ears!

Phonehed in Dallas

 

[lugerlover]

what release is the software..i believe nam need to be 4.1 and make sure your ksu is on the last version of 6.1

 

[Phonehed]

I upgraded this system myself last year so I'm sure it's not a software mismatch issue.

I finally got it working temporarily today by forcing the calls to transfer out on line 12 (without using an access code in the dialing string).

Since it's a seldom used feature out there I figure that will hold them until I can figure out how to make use of the entire pool for outbound transfer.

You'd think assigning pool 1 (PRI-A) as the outbound pathway would be the answer but it comes up and says pool busy every time even though they seldom use more than a dozen of their 23 channels simultaneously.



Phonehed in Dallas

 

[jerryreeve]

I have set up one customer with a PRI and a CP100, I had to go to Pool 15 or 16 which forced the call to be looked at by the routing table vice the outgoing pool. this was allowing the calls to transfer out but occasionally I would get dropped calls and had to add some pauses in at the start to make the system recognize the call before it completed the transfer.

Good luck

----------------------------
JerryReeve
Communications Systems Int'l
com-sys.com

 

[Phonehed]

Thanks Jerry,

I'll try a higher line pool number out there next week.



Phonehed in Dallas

 

[jerryreeve]

Make sure that you do have the routing table set up for this though.

----------------------------
JerryReeve
Communications Systems Int'l
com-sys.com

 

[jerryreeve]

Scratch my last, of course you do.

----------------------------
JerryReeve
Communications Systems Int'l
com-sys.com

 

[norstarboy125]

had this problem many of times I always just ended up picking a pri-a b channel ex. 13 and it works everytime.