Howto:How to customize the From/Identity header value at SIP interfaces: Difference between revisions
No edit summary |
|||
| Line 1: | Line 1: | ||
In some cases, SIP | In some cases, SIP providers ask for From/Identity Header values which we cannot build automatically. | ||
In such circumstances we can use the "add UUI" in Route Map and a specific configuration in the SIP interface for this. | |||
==Applies To== | ==Applies To== | ||
This information applies to all innovaphone | This information applies to all innovaphone gateways | ||
* V12r2 and higher | * V12r2 and higher | ||
| Line 11: | Line 11: | ||
===Problem Details=== | ===Problem Details=== | ||
If we look configuration of From or Identity | If we look into the configuration of From or Identity Header in the SIP interface, we see that the innovaphone system tries to build these headers with either one of the following: | ||
* 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 | In this case, the header is built automatically with parts of information already known by the system as CGPN or AOR. | ||
But in some | But in some cases, the provider requires a value in these Headers which is not related to any other known values. In such an event, we need a way to store and apply this "fixed" value. | ||
So we will use both | So we will use both configuration 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] | ||
* the UUI option in SIP interface configuration : [http://wiki.innovaphone.com/index.php?title=Reference12r2:Gateway/Interfaces/SIP] | * the UUI option in the SIP interface configuration : [http://wiki.innovaphone.com/index.php?title=Reference12r2:Gateway/Interfaces/SIP] | ||
=== Route Map Configuration=== | === Route Map Configuration=== | ||
The goal here is to use a MAP ''' | The goal here is to use a MAP '''generally used for all outgoing calls'''. In order to achieve this, the better approach is to use the last one, which should be the MAP that sends the call to the SIP interface. | ||
[[Image:Routesmaps.PNG]] | [[Image:Routesmaps.PNG]] | ||
| Line 32: | Line 32: | ||
[[Image:AddUUI.PNG]] | [[Image:AddUUI.PNG]] | ||
As the UUI will be used in | As the UUI will be used in the SIP header, we should write here a valid SIP URI: "<sip:UriUserPart@UriDomainPart>" | ||
| Line 42: | Line 42: | ||
At this | At this point, you should also check your provider's requirements, as we have also a few other possibilities to adjust: UUI in From or UUI in Identity. | ||
UUI in From | We can also go further with Advanced Tweaks like "/pai on" used for P-Asserted-Identity or P-Preferred-Identity as Identity header. | ||
[[Category:Howto|{{PAGENAME}}]] | [[Category:Howto|{{PAGENAME}}]] | ||
Revision as of 10:22, 17 January 2019
In some cases, SIP providers ask for From/Identity Header values which we cannot build automatically. In such circumstances we can use the "add UUI" in Route Map and a specific configuration in the SIP interface for this.
Applies To
This information applies to all innovaphone gateways
- V12r2 and higher
More Information
Problem Details
If we look into the configuration of From or Identity Header in the SIP interface, we see that the innovaphone system tries to build these headers with either one of the following:
- 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 parts of information already known by the system as CGPN or AOR.
But in some cases, the provider requires a value in these Headers which is not related to any other known values. In such an event, we need a way to store and apply this "fixed" value.
So we will use both configuration parameters:
Route Map Configuration
The goal here is to use a MAP generally used for all outgoing calls. In order to achieve this, the better approach is to use the last one, which should be the MAP that sends the call to the SIP interface.
Open this map and add the required value in "add UUI" field.
As the UUI will be used in the SIP header, we 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".
At this point, you should also check your provider's requirements, as we have also a few other possibilities to adjust: UUI in From or UUI in Identity.
We can also go further with Advanced Tweaks like "/pai on" used for P-Asserted-Identity or P-Preferred-Identity as Identity header.