Max calls configuration differentiated between internal and external

[NatalieThomas]

Hello,

one can configure the max calls option for a phone alright but is it possible to configure different options for internal and external calls? For example, it should not be possible to place a second internal call to an engaged dn. But it should be possible to place a second call to the engaged dn when the origin is external. If so, is this a solution, which is only configurable on CUCM or does the CME provide such a possibility, too?

Thanks a lot in advance for your help.

[Rob Huffman · Accepted solution]

Hi Natalie,

Someone may correct me here, but my answer would be that this is not possible

in CUCM if one is using a single DN. This is because the "Busy Trigger" does not

differentiate between Internal & External calls. You can however leverage a second

DN/Line button on the IP Phone and use the Forward Busy Internal and External

settings on the DN config page to route External calls to the secondary line when

the first line is busy while not routing Internal calls when the first line is busy.

In CME the Forward Busy command does not distinguish between Internal & External calls.

With Dual line ephone DN's the Hunstop channel command determines where the second call

will route and Octo line DN's it's the Busy Trigger just like CUCM

Cheers!

Rob

[Jaime Valencia]

Rob is right on the spot as always +5

CUCM does not provide a different busy trigger based on whether the call is internal or external.

The CFB/CFNA do provide a different treatment depending on the origin of the call but they're activated using the same method. CFB when you're the busy trigger+1 call. And the maximum number of calls applies to any calls you get on that line.

As Rob suggest the best way to tackle this is adding a separate DN

HTH

java

If this helps, please rate

www.cisco.com/go/pdihelpdesk

[linuxchild]

just in case this help  , you may make a difference between internal and external call when using FW

you can forbiden forwarding internal call

for sure this does not solve your current proble m

Usage Guidelines

Internal, or local, calls are defined as those calls that originate from other ephone-dns in the same Cisco Unified CME system.

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.

When the no forward local-calls command is used in  ephone-hunt configuration mode, internal calls to a hunt-group pilot  number are sent only to the first member of the group. If the first  group member is busy, the caller hears a busy signal. If the first group  member does not answer, the caller hears a ringback signal. The call is  not forwarded to subsequent hunt group members.

[NatalieThomas]

Hi,

Thanks a lot at all for your very helpful answers!