Howto:How to customize the From/Identity header value at SIP interfaces: Difference between revisions

From innovaphone wiki
Jump to navigation Jump to search
No edit summary
Line 14: Line 14:
* for FROM: Fixed AOR, AOR with CGPN as Display, CGPN in user part of URI
* for FROM: Fixed AOR, AOR with CGPN as Display, CGPN in user part of URI
* for IDENTITY: CGPN in user part of URI, Fixed AOR
* for IDENTITY: CGPN in user part of URI, Fixed AOR


In this case, the header is built automatically with pieces of information already know by the system as CGPN, AOR.
In this case, the header is built automatically with pieces of information already know by the system as CGPN, AOR.
But in some case, the provider requires a value in these headers which is not related to any others known values. Then we need a way to store and apply this "fixed" value.
But in some case, the provider requires a value in these headers which is not related to any others known values. Then we need a way to store and apply this "fixed" value.
So we will use both configurations parameters:
So we will use both configurations parameters:
* "add UUI" in route map : [http://wiki.innovaphone.com/index.php?title=Reference12r2:Gateway/Routes/Map]
* "add UUI" in route map : [http://wiki.innovaphone.com/index.php?title=Reference12r2:Gateway/Routes/Map]

Revision as of 18:36, 16 January 2019

In some cases, SIP provider asks From/Identity header values we cannot build automatically. Then we will use the "add UUI" in route map and a specific configuration in SIP interface for this.

Applies To

This information applies to all innovaphone gateway

  • V12r2 and higher

More Information

Problem Details

If we look configuration of From or Identity header in SIP interface we see the innovaphone system try to build these headers with one of this way:

  • for FROM: Fixed AOR, AOR with CGPN as Display, CGPN in user part of URI
  • for IDENTITY: CGPN in user part of URI, Fixed AOR


In this case, the header is built automatically with pieces of information already know by the system as CGPN, AOR. But in some case, the provider requires a value in these headers which is not related to any others known values. Then we need a way to store and apply this "fixed" value. So we will use both configurations parameters:

  • "add UUI" in route map : [1]
  • the UUI option in SIP interface configuration : [2]

Route Map Configuration

The goal here is to use a MAP certainly used for all outgoing calls. For this the better way is to use the last one, should be the map send the call to the SIP interface.

Routesmaps.PNG

Open this map and add the required value in "add UUI" field.

AddUUI.PNG

As the UUI will be used in a SIP header you should write here a valid SIP URI: "<sip:UriUserPart@UriDomainPart>"

SIP interface configuration

In SIP interface select the UUI options in "From/Identity Header when Sending INVITE".

IdentityUUI.PNG


At this step, you should check the provider requirement, as we have many possibilities. UUI in From; UUI in Identity; we can also acting with advanced tweaks like "/pai on" for use P-Asserted-Identity or P-Preferred-Identity as Identity header.