Call forward to external destination.

[sunspark]

Hi ,
can anyone help me about this case .

When i use speedcall to external destination  : it work ( for exemple speed call 2222 ---> 0044xxxxxxxx)
when i call directly 0044xxxxx : it work

when i make a call forward always to 0044xxxxxx : doesn't work
when i use 2222 in call forward always : it work

For all this tests , i use the device number 3111 (5320e)

in the Cos : call forward YES , call forward internal/external destination YES.

Any idee ?

Cheers.

[ralph]

It's not going to be a problem with your device.
I would assume the two calls are going out different routes, perhaps even different trunk groups.
It could be a COR issue with the route or it could be a carrier issue not liking the forwarded Caller ID.

Try this test.
Create a system speed dial for both calls.  Be sure to tick "Override Toll Control".
Then forward to the system speed dial.   If it works then it's a COR issue with them incoming trunks.
If not then have your carrier tell you why it's being rejected.

Ralph

[sarond]

When you dial 0044xxxxxxxx directly does it dial straight away, or wait for a timeout?

I have had issues where if your ARS is not programmed correctly it won't forward properly.

As a test put the exact number in ARS i.e. 0044xxxxxxxx

[sunspark]

Hi Sarond , it's dial strait away.

@Ralph : i'dont uderstand "Create a system speed dial for both calls"

My device 3111 have COS 6-6-6 (D,N1,N2)  but when i look at the cor menu it blank on cor6

DGT Trace started:                                                             

004xxxxxx : ARS 004 +  8, ARS 004 +  8, Route (64)                           
Route 64 :  TDM trunk group 62    / Cor Group 64
Cor group 64 : 1,2

I have only one Tdm trunk group:62

thank you                                                       

[acejavelin]

Whenever I see this I always assume the telco provider is blocking the call based on caller ID carrying through from the original caller and being rejected because they don't know that number...

Do an 'edt trace tsp l2l3 <plid>' and make a test call, verify the call is attempting to go out the PRI and look for a disconnect or reject message. Watching these logs for little bit, they are pretty easy to understand, they are actual D-channel messaging between the PBX and the telco on your PRI.