Passing the ISUP IAM in the INVITE as in RFC 3398 is a standard way to pass through the OLI. In mapping OLI to SIP itself, many vendors seem to use some form of proprietary scheme. As couple of examples, I have dealt with vendor -- using the non-standard Remote-Party-ID header in passing the OLI as header parameter, -- using OLI as SIP URI parameter in From header
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bu, Wen Fei (Leo) Sent: Wednesday, August 23, 2006 10:41 PM To: sip-implementors@cs.columbia.edu Subject: [Sip-implementors] How to handle OLI parameter when mapping ISUP toSIP? All, I just want to know whether there are any documents which define how to handle OLI (Originating Line Information) parameter when mapping ISUP message to SIP message. If anybody know, please let me know. Thanks in advance, Leo _______________________________________________ Sip-implementors mailing list Sip-implementors@cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list Sip-implementors@cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
