Call Forward to Mobile - "INVALID"

[RDECIT]

MCD10 latest build. Setting up call forward to a mobile is showing invalid when you try and dial the extension when on forward.

I've checked the COS to allow forward to external numbers, on both sets and trunks, and the Public Network to Public Network Allow.

I've entered the number raw with a leading 9 and as a speed call. Both show invalid when the extension is dialled. I can call both raw and speedcalls without a problem. It's driving me mad!

 

[kwbMitel]

Looks like you've covered the basics. Time to double check the facts before going on a snipe hunt.

COS of set allows:
- FWD to External
- Public to Public Connection
- Conferencing

COS of trunk allows
- FWD to External
- Public to public
- Conf

Fwd set using speed call and select the override toll control.

Set to Set call - what happens
Trunk to set call - what happens



*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[M1tel]

Ensure you trunks have a cor that can call the fwd number

 

[RDECIT]

kwbMitel All COS were as you described, Set to Set shows INVALID when you dial the extension.

I can't test Trunk to Set as we don't have any DDI's setup.

M1tel I've tried changing the COR for the trunk group to allow access to the mobile numbers. But it wasn't a problem dialling mobiles via number or speed call.

 

[kwbMitel]

COR should not be the issue for reasons already given, and the use of Speedcall overriding toll control.

Am I correct in assuming analog trunks?

If so, there might be a timing issue.

Please post the COS option for set and trunks

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[RDECIT]

No, digital trunks. ISDN 30. I'll post COS for sets and trunks when I'm in the office tomorrow.

 

[kwbMitel]

Something unexpected or something stupid will be the answer.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[RDECIT]

I've got the COS items in a CSV, but I can't paste them in a readable format here.


I'll try some other things.

 

[kwbMitel]

Post them as CODE

Check the link at the bottom for Process TGML as to how.

or Try Monospaced Text

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[kwbMitel]

Failing that post them anyway, I can cut and paste to elsewhere to read it.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[Mitelpassion]

run a ccs trace when you make the call.
see what the output is..this may point you in the right direction.

I've had similar issues before, you could try playing with the digits before outpulsing.

also are you sure you're call is being routed via the isdn? maybe some other LCR devices?

doubt if barring is an issue at all but worth a check.
maybe in the speedcall say yes to override toll control if not already done