For calls in a VPN context, the public network shall include the VPN indicator information element in the SETUP message.
Incoming Gateway PINX functionality and Originating PINX functionality shall identify the call as a call in a VPN context.
The public network shall include the Calling party number information element and the Calling party subaddress information element in the SETUP message as follows:
– if received from a preceding PINX, a Transit PINX shall transfer the information elements to the physical PINX at the destination interface regardless of any supplementary service subscription information;
– if received from a preceding PINX, a Relay Node shall transfer the information elements to the physical PINX at the destination interface regardless of any possible supplementary service subscription information;
– an Incoming Gateway PINX may transfer the information from the other network;
NOTE – The handling of numbers, e.g. translations, presentation indications, is outside the scope of this Annex.
– an Originating PINX shall provide the Calling party number information element to the physical PINX at the destination interface regardless of any possible supplementary service subscription information. Furthermore, an Originating PINX shall transfer the Calling party subaddress information element if received from the calling user regardless of any possible supplementary service subscription information.
The public network shall include the Transit counter information element in the SETUP message if received from the preceding PINX.