nme-cue autoattendant not passing calls to internal DNs

[andres.pasten]

Hi,

I've a NME-CUE 3.0.4 with autoattendant configured integrated with a CUCM 6.0.1.3000-7 cluster.

The problem is that when you choose option 1 (call the DN) it present a message saying the DN is wrong.

The CTI RP and Ports are registered ok, and if you choose option 0 (call operator) the call pass ok.

I've tested the DN associated with the CTI Ports on a phone, and that DNs can call internal numbers ok.

Any idea would be appreciated.

TIA

Andres Pasten

[david-lima]

Hi Andres, please check your dial-peer configuration:

dial-peer voice 1000 voip

description AA

destination-pattern 5...

session protocol sipv2

session target ipv4:X.X.X.X

dtmf-relay sip-notify

codec g711ulaw

no vad

Also, did you add the user with his associated number in CUE: System->user

Best regards

David

[andres.pasten]

David,

I've these dial-peers:

dial-peer voice 5460 voip

destination-pattern 5460

session protocol sipv2

session target ipv4:

dtmf-relay sip-notify

codec g711ulaw

no vad

dial-peer voice 5000 voip

preference 2

destination-pattern 5...

voice-class codec 1

voice-class h323 1

session target ipv4:

dtmf-relay h245-alphanumeric

no vad

dial-peer voice 5001 voip

preference 4

destination-pattern 5...

voice-class codec 1

voice-class h323 1

session target ipv4:

dtmf-relay h245-alphanumeric

no vad

!

dial-peer voice 5002 voip

preference 6

destination-pattern 5...

voice-class codec 1

voice-class h323 1

session target ipv4:

dtmf-relay h245-alphanumeric

no vad

The first one is for the AA, the last 3 ones are for the DNs on CCM cluster.

Which user should I add on CUE->System->User ? jtapi user?

Please let me know

TIA

Andres Pasten

[david-lima]

Hi Andres, no the jtapi user, a single user with his phone extension. (the user and phone extension that you cannot reach from AA)

Best regards

David

[andres.pasten]

Hi David,

I don't get it... I need to had every user on CCM to call it from CUE?

I've found another issues. I've CTI RP and ports on a ccm group that has the ccm pub as primary and ccm sub01 as secondary, and the same is configured on CUE Web, but CTI ports and RP are registered with secondary.

I've erased secondary from that CCM group, and then cti ports and rp became unregistered, only if I had again the secondary on the CCM group, they became registered again.

But JTAPI on CUE is registered with CCM primary.

So it seems a problem with jtapi user that can transfer call with devices registered on another ccm of the cluster.

Please let me know your opinion.

TIA

Andres Pasten

[andres.pasten]

Hi David,

I don't get it... I need to had every user on CCM to call it from CUE?

I've found another issues. I've CTI RP and ports on a ccm group that has the ccm pub as primary and ccm sub01 as secondary, and the same is configured on CUE Web, but CTI ports and RP are registered with secondary.

I've erased secondary from that CCM group, and then cti ports and rp became unregistered, only if I had again the secondary on the CCM group, they became registered again.

But JTAPI on CUE is registered with CCM primary.

So it seems a problem with jtapi user that can transfer call with devices registered on another ccm of the cluster.

Please let me know your opinion.

TIA

Andres Pasten