Callback a missed call from CUCM doesn't work

[alex_hc69]

Hi!

We've detected a strange behavior on an Alcatel OXE node when we try to callback a missed call from a CUCM node.
When we try to callback a missed call from a CUCM call (pressing messages button -> missed calls -> callback) on a OXE R10 directory, callback doesn't work.

Normal calls work fine on any direction OXE<->CUCM.
Sip trunk between OXE-CUCM seems to be configured correctly.

Any clue about which could be the problem?

Thanks and regards

[sadim]

Hi,

Check External callback translation tables.

Regards

[alex_hc69]

Already checked, nothing unusual...
various strings, included: basic number=DEF, delete=0, add=0

The CUCM directories are 4XXXX and the OXE directories are 6XXXX

On a SIP trace, the call CUCM->OXE seems to reach the OXE with 4XXXX number, thats why i can't see a problem with the external callback transaltion.

There's no entry on the external callback translation tables with 4...

Example of Invite message from CUCM to OXE:
INVITE sip:64599@10.15.127.12:5060 SIP/2.0
Date: Thu, 07 Apr 2016 11:46:21 GMT
Call-Info: <sip:10.18.14.202:5060>;method="NOTIFY;Event=telephone-event;Duration=500"
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
From: <sip:46889@10.18.14.202>;tag=49302ae0-addf-424e-8bcf-0ae9f524db4e-46773007
Allow-Events: presence, kpml
P-Asserted-Identity: <sip:46889@10.18.14.202>
Supported: timer,resource-priority,replaces
Supported: X-cisco-srtp-fallback
Supported: Geolocation
Min-SE: 1800
Remote-Party-ID: <sip:46889@10.18.14.202>;party=calling;screen=yes;privacy=off
Content-Length: 0
User-Agent: Cisco-CUCM7.1
To: <sip:64599@10.15.127.12>
Contact: <sip:46889@10.18.14.202:5060>
Expires: 180
Call-ID: 57a82a00-7061488d-7c36-ca0e120a@10.18.14.202
Via: SIP/2.0/UDP 10.18.14.202:5060;branch=z9hG4bK191be2e721647
CSeq: 101 INVITE
Session-Expires: 1800
Max-Forwards: 70

Any clue?

[vad]

For callback - the first point - External callback translation rules.
F.e. you have:
1) basic number=DEF, delete=0, add=0
2) not answered call from 46889

For callback PBX will try to dial 046889. If you dial 046889 (usual call) - you have no problem with call to 46889?

[alex_hc69]

No problem dialing 46889, the call works perfectly.
046889 doesn't work.

Problem is when:
64599 (OXE) has received a missed call from 46889 (CUCM)
If 64599 tries to callback 46889 (by messages button -> missed calls -> callback), doesn't work.

[vad]

When OXE record a call as missed - used Ext. callback translation rules.
If you want - after call from 46889 - dial for callback 46889 - you need to manage External callback translation rules
1) basic number=DEF, delete=0, add=nothing, or
2) basic number=DEF, delete=0, add=0 and additional string - basic number=4, delete=0, add=nothing

[alex_hc69]

Tried both options, do not work...

In addition, a curious behaviour:
When you make a call from CUCM to another node, the callback works perfectly.

CUCM has just 1 trunk to node1, the link to node 2 is across an ABC-F link between OXE nodes:

________SIP____________ABC-F_______
CUCM <--------> Node1 <---------> Node2
4XXXX_________6XXXX__________2XXXX

Node2 can make the callback, but Node1 can't.

[vad]

can you show all string from Ext. callback translation, may be you have string with basic number=B?
4XXXX - can you explain management for 4XXXX on node 1 - Speed Dial, Routing/Network number (ARS or Network routing table used)?

[alex_hc69]

Yes, string with:

basic number: B; delete=1; add=0

[alex_hc69]

SOLVED:

Change B string to:
Basic number: B; delete=1; add=none

Thanks so much for the help!