The OP has clearly stated what he wants:

calls coming from outside to be transfered to certain extension but at the same time i can be able to receive internal calls.

This is is done with the command "no forward local-calls" under ephone-dn.

Dear Palao,

Thanks for your reply. I tired your command mentioned in your post but it does not work.

You can find my attached config.

I will be very grateful to you.

Regards,

Malik.

Sorry, if doesn't work, you need to contact the TAC.

p.bevilacqua wrote:
The OP has clearly stated what he wants:

See Paolo, this is why I asked for a more clear problem description earlier.  The original descritpion had awkward grammar, and it wasn't clear what they were ultimately trying to achieve.  That's why I wanted the poster to clarify before I approached an answer.  And that's why your command didn't resolve what the customer was looking to do, because the original problem description was not what you thought it was.

The suggestion you gave prevents an ephone-dn from being able to forward to another hop.  See the documentation for the command:

When the no forward local-calls
 command is used in ephone-dn configuration mode, internal calls to that
 ephone-dn are not forwarded if the ephone-dn is busy or does not 
answer. If the ephone-dn is busy, the caller hears a busy signal. If the
 ephone-dn does not answer, the caller hears a ringback signal. The call
 is not forwarded even if call forwarding is enabled for the ephone-dn. 

The OP wants to be able to restrict AA->CME calls in to a specific ephone, not control ephone call forwarding.  You wouldn't use that command to do what the OP wants.  Hence, in my opinion, that low rating is potentially warranted since your solution wasn't accurate for what the customer was doing.  There isn't a reason for *you* to 'vent' on the public forum about your low score for that, either.

Now to the original solution.  Since the calls come into the AA, the transfer is going to be from CUE towards the ephone-dn.  To restrict CUE from transferring to specific ephones, the easiest way is to configure COR lists.  You will apply an inbound COR list to the CUE dial-peer, and an outbound COR list to your ephone-DNs.  Make sure you run 'debug voip ccapi inout' so that you know what inbound peer is being matched when CUE does the transfer to the CME extension.

Something like this should work:

dial-peer cor custom

name restricted

dial-peer cor list no-cue-ephone

name from-cue

dial-peer cor list restricted

name restricted

dial-peer voice x voip

desc CUE inbound peer

corlist incoming no-cue-ephone

ephone-dn X

corlist outgoing restricted

Apply the restricted corlist to any ephone-dn that you don't want to be able to transfer to.  If the calling or called peer doesn't have a corlist, the call will succeed.  You can read more about cor lists here:

http://www.cisco.com/en/US/tech/tk652/tk90/technologies_configuration_example09186a008019d649.shtml

-Steve

Dear Steven,

As i mentioned in my earlier post that i am running CME & CUE.

There is on extension on which i dont want to receive external calls/outside calls but at same time i should be able to make a call at local extentions and outside.

Please let me know how i can accomplish this task.I have also attached the current config.

Call flow is in such a way that there is a Auto Attendent at CUE all the outside calls are picked by the Auto Attendent and then you can dial the extension.

Please let me know if you need further clarification.

Regards,

Malik.