CUCM SIP Normalization and Transparency Scripting Example

Publisher

Technology or Die (independent blog)

URL

https://technologyordie.com/cucm-sip-normalization-and-transparency-scripting-example

Published

2019-10-29

Updated

unknown

Accessed

2026-09-25

HTTP status

200

License

author copyright; no-redistribution; short excerpts and locators only

Source notes citing this source

• Practitioners report that Unified CM, acting as a back-to-back user agent, drops non-standard SIP headers between call legs unless a transparency script passes them through. field report in context
• A common field pattern for transparency: an inbound handler reads a header and copies it to the other leg with msg:getPassThrough() and pt:addHeader(), after listing the header in M.allowHeaders; an outbound handler then rewrites or removes it. field report in context
• Practitioners read the trunk's Parameter Name and Parameter Value pairs inside a script with scriptParameters.getValue(name), so one script can be reused with different values. field report in context

Cite this source record

APA

WarmTransfer. (2019, October 29). CUCM SIP Normalization and Transparency Scripting Example. WarmTransfer. https://warmtransfer.net/knowledge/sources/technologyordie-cucm-sip-norm-transparency-example

BibTeX

@misc{warmtransfer-technologyordie-cucm-sip-norm-transparency-example,
  title  = {CUCM SIP Normalization and Transparency Scripting Example},
  author = {{WarmTransfer}},
  year   = {2019},
  url    = {https://warmtransfer.net/knowledge/sources/technologyordie-cucm-sip-norm-transparency-example},
  note   = {Technology or Die (independent blog), accessed 2026-09-25}
}