A guide to SIP Normalization on CUCM and Lua Scripting

[Sreekanth Narayanan]

I have recorded this guide for SIP Normalization on call manager and also have elaborated a little bit on how we use the Lua scripting.

A SIP Normalization script could really help the customer as a workaround or a permanent solution for issues related to calling and CLID.

Disclaimer:

Cisco TAC does NOT support SIP Normalization scripts. If the customer has already applied a script, TAC does NOT troubleshoot it. It is the customer's responsiblity to make it work.

[jpino]

Good you are the best ....thanks

[mohammad saeed]

Hi,

It's very informative video and information, many thanks,
I have question if I can remove SUBSCRIBE message from SIP trunk inbound call using LUA script in cucm?

Thanks,

Mohammad Said

[Anirban Das]

Hello @Sreekanth Narayanan,

I am completely new in CUCM. I have a short question.

Scenario:

Extension in CUCM: +498900001234 (GNF format)

Voice Mail in Unity: 498900001234 (without prefix "+")

Calling +498900001234 and leaving voice mail. Unity sending the NOTIFY towards 498900001234 to activate MWI. And obviously CUCM sending "SIP/2.0 404 Not Found" to Unity.

I used normalization script to remove "+" from the diversion header (on Unity SIP trunk) to send 498900001234 towards Unity so that Unity can recognize the number and process accordingly. Till this part there is not issue. Now since Unity is sending the NOTIFY out of the existing SIP Dialogue using a separate Call-ID, I am unable to modify the URI number in NOTIFY message to add "+" so that CUCM can locate the number and MWI works. So, here MWI is not working since CUCM is not getting any match with 498900001234.

My question is, any possibility to add "+" as prefix for 498900001234 in the NOTIFY message using normalization script / any other way so that MWI works?

14:46:19.975 |MessageWaiting::sendDaReq invalid extension =498900001234 CSS =cf6b4480-8dd2-d35e-0175-1932e802c05c|2,100,57,1.59^10.18.65.86^*
14:46:19.975 |MessageWaiting - wait_SsInfoReq can't find device type for DN = 498900001234|2,100,57,1.59^10.18.65.86^*
14:46:19.975 |//SIP/SIPD(2,67,4)/ccbId=0/scbId=60/restart0_SsInfoErr: Unsolicited NOTIFY not processed - ssCause=29 mapped to respCode=404|2,100,57,1.59^10.18.65.86^*
14:46:19.975 |MessageWaitingManager - deleteEntryFromMwiTable - entries in the messageWaiting table = 0x0 |2,100,57,1.59^10.18.65.86^*

Thank you,

Regards,

Anirban Das

[Roger Kallberg]

@Anirban Das Not a direct answer to your question as such. But why do you not have the extension in Unity Connection in full +E.164 format? Having that would greatly simplify your setup as you’ll not need to use any scripts to modify any headers in the SIP dialogue.

[simon hester]

Completely new the SIP scripting and been watching the video to try and get some clues

My use case of a LUA SIP normalization script is for the transfer of a call back out to the PSTN yet keeping the original caller ID. is this possible?

Call 1 External Incoming call >> SIP Trunk >> CUBE >> CUCM User Answers

Call 2 CUCM User Transfers Call >> CUBE >> SIP Trunk >> Third Party

The scripts seem complex so to speak and wondering if I'm tryig to do something that is just not possible. 

[andreas33693]

You are a rock star my friend!!!

Kudos