Legend Forwarding Issues

[buthead]

I can forward a station to a "local long distance/Band C" area code, but can't to a true LD/out of state area code. All inbound and outbound trunking is done over a single ISDN PRI. I can call the LD number from the station I'm trying to forward, without any restrictions. I think the issue is with the PRI. When the extension is forwarded to a local number, and a station call is presented to the forwarded set, the terminating number is presented with the expected area code, nxx, and bogus 4 digit extension of the customer. When a trunk/DID call is presented, the terminating set gets no CLID and "Unknown Number" is displayed. Both calls do complete. When the set is fowarded out of state the caller gets reorder/fast busy. I'm going to call the vendor of the PRI and see if there is some wierd trunk to trunk block on their side based on the area code. What say ye?

 

[CarGoSki]

Print PRI and look to see what is in Number To Send. Male sure that the number is a vaild DID.

 

[buthead]

The carrier has confirmed that without a valid 10 digit number they will reject the call. My only access to the system is through the console. Can I go in that way and see/program the digits sent CarGoSki?

 

[SYQUEST]

Yes, and you might want to read the Feature Reference Guide document for the Legend. It is full of this kind of stuff for free @ support.avaya.com.

....JIM....

 

[Telecomboy]

Under your PRI settings, it is number to send. You either set it up for base number + extension (sends each DID out) or Line telephone number (in which you tell it to send the main number for all calls) for the most part.

 

[buthead]

My guess is it's either/or? We are set now to send the DID. If I change this, I'm assuming I am going start sending the main number, instead if the DID's. Correct?

 

[Telecomboy]

Yes, on the Legend it is either/or. If they need the main number to put the call through, then you need to change it system-wide.

 

[buthead]

Thank you to all who replied. If I'm sending the DID's now, I don't know why the carrier doesn't see that as valid. In my original post I mentioned a unknown number was displayed when I tested the feature locally. I will see what I can uncover. Thanks again.

 

[merlinman]

I'm not sure this is your issue or not, but here's what I have fought off and on for 2 or 3 months, 'till we finally got someone at the Service Provider to tell us why it failed.

Client was trying to FORWARD outside calls using REMOTE FORWARD of the Legend system, and they would not go through, just waved off.

Calling that forwarded extension from another one, the call would complete just fine.

I looked at the info in tracing the PRI and saw that the call set up was DIFFERENT.

Finally, some one at the Service Provider told the client that in order to do off prem forwarding, they had to set it up using their INTERNET INTERFACE that the provider gave them.

Big mystery finally solved.

http://home.comcast.net/~merlinman

 

[buthead]

Merlinman,
Thanks for the tip. I will look into that. Was that pipe fractionalized, or broken out of an ISP connection? Mine is.

 

[SYQUEST]

One thing to remember on the Legend/Magix for PRI on the BASE NUMBER + STATION, if any of the stations are NOT DID, you get a WRONG CLID sent. There is no way to fix this, except to use the main number or line number. Avaya never finished the PRIMARY ISDN software before discontinuing the product line!

....JIM....