How to forward the SIP from/to header domain to outgoing leg
Page 1 of 1
How to forward the SIP from/to header domain to outgoing leg
If you want to forward incoming SIP from/to header domain to outgoing leg you need to upgrade your FreeSBC to the minimum Release 3.0.114 With Release 3.0.114 we added forward_sip_domain script to our routing scripts.
This filter is used to forward the domain name (or IP address and port) from the incoming call to outgoing call, for the following SIP headers:
- from (update call attribute :calling by appending :calling_sip_host and calling_sip_port)
- to (update call attribute :called by appending :called_sip_host and called_sip_port)
- P-asserted-identity (update call attribute :private_address by appending :private_address_sip_host and private_address_sip_port)
Installing this script:
- This script is installed as a "route_remap" filter. In your main routing script, you need to add the follownig lines at appropriate places in the script:
- require 'forward_sip_domain' unless defined?(ForwardSipDomain)
- include ForwardSipDomain
- route_remap :method => :forward_sip_domain
- This script requires the routes to have a custom column named "forward_sip_domain", type boolean.
(custom route column can be created in the "Routes" section of the web portal under "Create New Route Column")
Using this script:
In the WEB Portal, "forward_sip_domain" attribute is configured per route:
- Under "Routes" section of the web portal (then under "Custom Parameters").
This filter is used to forward the domain name (or IP address and port) from the incoming call to outgoing call, for the following SIP headers:
- from (update call attribute :calling by appending :calling_sip_host and calling_sip_port)
- to (update call attribute :called by appending :called_sip_host and called_sip_port)
- P-asserted-identity (update call attribute :private_address by appending :private_address_sip_host and private_address_sip_port)
Installing this script:
- This script is installed as a "route_remap" filter. In your main routing script, you need to add the follownig lines at appropriate places in the script:
- require 'forward_sip_domain' unless defined?(ForwardSipDomain)
- include ForwardSipDomain
- route_remap :method => :forward_sip_domain
- This script requires the routes to have a custom column named "forward_sip_domain", type boolean.
(custom route column can be created in the "Routes" section of the web portal under "Create New Route Column")
Using this script:
In the WEB Portal, "forward_sip_domain" attribute is configured per route:
- Under "Routes" section of the web portal (then under "Custom Parameters").
Re: How to forward the SIP from/to header domain to outgoing leg
This script is coming as default after Rls. 3.0.116. You just need to set forward_sip_domain route column as enabled.
Similar topics
» Adding a pre-defined SIP header to outgoing leg
» Adding X-NAP header to outgoing INVITE
» Adding a SIP Header to outgoing call
» Domain Rewriting
» SIP - Domain Routing
» Adding X-NAP header to outgoing INVITE
» Adding a SIP Header to outgoing call
» Domain Rewriting
» SIP - Domain Routing
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum