Call Forward External

[eileenc]

I am having a problem that I am hoping somebody on here can give me some insight into.

This just started approximately 3-4 months ago, all of the sudden none of our phones are able to forward calls externally. I have had my vendor and our local carrier pointing fingers at each other for months. Our vendor says that something from our local carrier is blocking the calls from leaving the PBX - our local carrier was blaming programming in the PBX. This has been going on for months. Our vendor was able to create a workaround so that now we can forward out to our local area code - but that is it. Nothing else will work.

Now our carrier is telling us that it has something to do with "call screening" and if they disable it that 911 might not work correctly and they want us to sign a waiver saying they aren't responsible for this. I cannot figure out how forwarding a call (that we have been doing for years, by the way) - can interrupt 911? Makes no sense to me. This is the capture that we got from our carrier - if it helps at all. Any insight would be greatly appreciated.

<== 09:06:13.087 l3suId = 14
<== Q931:
CR: 0, 14, 5e
SETUP:
BC: speech
64 kbit/s
circuit mode
mu-law speech
CID: 18
Length: 3
Channel Selection Info: As Indicated in Following Octets
D-Channel Indicator: D-Channel NOT indicated
Preferred/Exclusive: Exclusive
Interface type = primary rate
Interface Identifier: IID Implicitly Identified
Channel Type: B - Channel Units (3).
Number Map: Channel is indicated by the number following.
Coding Standard: CCITT
Channel Number= 21
PI: private_network_serving_local_user
origination_address_is_non_ISDN
PI: user
CGN: e164
national_number
network_provided
presentation_allowed
7244311999
CDN: e164
national_number
17247413200
RN: e164
national_number
user_provided_not_screened
presentation_allowed
call forward unconditional
4122087301
mand information element missing or IE error

 

[trvlr1]

What are you getting when you try to forward? Does the phone actually look like it is forwarded, but when you make the call it does not go through? Or is the phone not forwarding? If it is, when you call it, what do you hear, fast busy, telco message etc?
Is there a difference between forwarding local and LD?
If you forward using the route ACOD # in place of 9 or whatever your external number is, does it then go through?

 

[eileenc]

The phone appears to forward, but when you call the number we are getting "the call cannot be complted as dialed...".

Yes, it is able to forward local, but not long distance.

I also tried with the ACOD and I still get the same results.

 

[trvlr1]

Based purely on this information, it does look like the issue is with the Telco. Do you have the same lines for local and LD, or do you have separate? Also, when using the ACOD for LD, if you used ACOD1xxx-xxx-xxxx try dialing acodxxx-xxx-xxxx as sometimes the carrier does not want to see the 1.

 

[eileenc]

It isn't working either way. Any idea what the carrier is talking about when they say we need to disable "call screening

 

[Firebird Scrambler]

If no programming has been done on the phone system with the trunks and barring etc, then it has to be a telco problem.

All the best

Firebird Scrambler
Meridian 1 / Succession and BCM / Norstar Programmer in the UK

http://www.linkedin.com/in/davidbromley

If it's working, then leave it alone!.

 

[Splic3d]

We had a customer that changed carriers and could not CFW as well, their problem was that the CLID of the incoming caller was being sent out as the CLID and the carrier would rejectt the call as it was not one of their assigned number, primary and DID. The carrier said this was for billing purposes. We set it so that all that went out was their primary or DID CLID.

http://www.i3techgroup.com

Avaya/Nortel/NEC/Asterisk/Access Control/CCTV/DSX/Acti/UCx

 

[eileenc]

Splic3d (Vendor) We had a customer that changed carriers and could not CFW as well, their problem was that the CLID of the incoming caller was being sent out as the CLID and the carrier would rejectt the call as it was not one of their assigned number, primary and DID. The carrier said this was for billing purposes. We set it so that all that went out was their primary or DID CLID

This is exactly what our vendor thinks is happening - yet the carrier is denying it. How do I get them to change this?

 

[hawks]

It is the caller id info that the carrier is seeing on the forwarded call. They see the original caller id and since it does not match any of your numbers that deny the call to go through. They can open it up to allow any number to pass but that's where he is telling you that the 911 may not work right. I've never had them tell me that though, but I guess if someone forwarded their phone to 911 and someone did call that phone then the 911 operator would see the person calling.

 

[eileenc]

Right - because people are always going to forward their phone to 911??? That is just crazy.

Thanks for your replies!

 

[Splic3d]

OCLI in the net_data did the trick for me. We set it to EXT. It should send the CLID that is assigned to the DN, ie.... DID, or primary CLID.

http://www.i3techgroup.com

Avaya/Nortel/NEC/Asterisk/Access Control/CCTV/DSX/Acti/UCx