Thanks for you comments. This is used in the context of processing 911 calls. So typically, the caller is "local" to the CUCM placing the outbound call. The reason for having the original caller's IP present somewhere in the outbound call it so the server receiving the 911 call can figure out the caller's physical location (this server processes the call before forwarding to the actual PSAP). As far as using JTAPI, this is basically what we are presently doing and it works well. But I was trying to find a "lighter" solution that would not require an external process. That is why the SIP Normalization scripts seemed promising. But I was hoping for some service to provide information on the call being processed, but it looks like all these services are SIP based. While this may partly work for cases where the caller is SIP based, I'm not sure what happens when the caller is using a legacy signaling (SCCP, H.323, etc) while the outbound leg is SIP? Would the SIP Normalization script see any information for the inbound leg since it's not SIP? Gaëtan
... View more
We have an application that usually relies on a CTI app to obtain a caller's IP address and we'd like to see if we could implement something similar using a SIP Normalization script instead. What we would like to do is add a custom sip header to the outbound SIP INVITE that includes the original caller's IP address. I haven't seen anything in the lua script documentation that would provide information on the original caller. Gaetan
... View more
