call route destination not working

[flashover]

I have a PRI circut on a 3.2.53 and cannot get the incoming route destination to route call directly to ext. # without putting a period in the destination field.

 

[disturbedone]

What do you have exactly in the ICR? What digits, what destination etc?

You say it works if you have a period (.) - is that all you have or do you have the xtn followed/preceeded by a .?

 

[flashover]

i have the incoming number set as dns digit which is my ext.# line grp. is 2 and destination is period{.} if i put user info from drop down bar DID rings busy.

 

[jamie77]

Are you in the UK on a PRI?

Are you putting the digits into the 'Incomming Number' field exactly as they are presented from your line provider?? Have you confirmed this with monitor.

Can you dial the destinations you are trying to set internally?

Jamie Green

Fooball is not a matter of life and death-It is far more important!!!!

 

[flashover]

pri in fl. and yes directly from drop bar

 

[kwing112000]

I have had issues with the drop down on all 3.2 releases. If you type it in it will not work. You have to click on it and it seems to work. I have seen it on 4 or 5 systems.

 

[janni78]

That seems to be an issue with the 3.2 manager.

If you just type in the destination you'll get a warning saying "No such RAS, User......

 

[flashover]

THATS CORRECT. ANY SUGGESTION ON HOW TO FIX

 

[1043]

Leave destination blank in the msn config bar and edit it in the incoming call route field.