We're trying to push the LI point of interface onto the carrier's network since they are providing both origination and termination for this scenario. An RFC or another standardized method would be preferred, I don't know if they will cooperate with any custom headers. On Fri, Apr 12, 2019 at 10:40 AM Dovid Bender <dovid at telecurve.com> wrote:

If it's for your own internal purposes why not use a custom header?

On Fri, Apr 12, 2019 at 1:38 PM Calvin E. <calvine at gmail.com> wrote:

...

I'm faced with a Lawful Intercept scenario for SIP call forwarding which requires the forwarded call to contain the original source and destination numbers. The source number may or may not be changed on the forwarded leg. I see how the original called number can be preserved in Diversion or History-Info, but how do I preserve the original source number? Is there an RFC for this that I missed, or misunderstood?

Is it as simple as using PAI for the forwarded A-number and From for the original? I'm concerned the wrong number might appear to the called party. _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops