FAQ
SIP Refer Forwarding
Why Does IXICA Not Support SIP REFER?
IXICA does not support SIP REFER on its SIP trunks. This security policy helps reduce exposure to unauthorized call transfers, toll fraud, and the disclosure of sensitive call information.
Customers should configure their telephone systems to manage transfers within the PBX rather than rely on carrier-side SIP REFER.
What is SIP REFER?
SIP REFER is a signalling method that asks another telephone system or device to contact a specified destination. It is commonly used for call transfers, with the destination supplied in a field called Refer-To.
SIP REFER is a legitimate protocol feature and is not inherently a security vulnerability. However, it requires careful authentication, authorization, and handling to prevent misuse. Improperly configured systems may accept transfer requests from parties that should not have permission to redirect calls or initiate new connections.
Why has IXICA chosen not to support it?
IXICA takes a preventative approach to call-transfer security. We do not support this mechanism on our SIP trunks because improperly controlled transfer requests can introduce several risks.
Toll fraud and unauthorized charges
An inadequately protected telephone system may allow an outside party to trigger calls to unauthorized destinations, including expensive international or premium-rate numbers. Abused transfer permissions can generate substantial charges without the account holder’s knowledge or approval.
Unauthorized call redirection
A malicious or compromised system may attempt to redirect an active call to a destination that neither the caller nor the account holder intended. Without appropriate authorization checks, a telephone system could process that request as though it were a legitimate transfer.
Misleading transfer identities
A transfer request may claim to originate from a trusted person or system. Information such as the Referred-By identity is not, by itself, proof of authorization. Without appropriate protection and verification, that information can be falsified or reused to influence how a call is handled.
Exposure of sensitive information
Depending on the implementation, status notifications associated with REFER can reveal endpoint availability, IP addresses, or other signalling details. Excessive information in these notifications can undermine privacy and disclose information that would otherwise remain protected.
Our policy is to avoid this additional transfer mechanism at the carrier connection and require customers to use PBX-managed alternatives.
Does this mean I cannot transfer calls?
No. Not supporting carrier-side SIP REFER does not prevent call transfers altogether.
A compatible, properly configured PBX can manage transfers itself, including:
- Blind transfers: Sending the caller to another destination without first speaking to the recipient.
- Attended transfers: Speaking with the recipient before completing the transfer.
These functions can be handled within the PBX rather than delegated to the carrier. The exact configuration and supported behaviour depend on your telephone system.
Can my phones still use SIP REFER internally?
Yes. This policy concerns the SIP connection between your telephone system and IXICA.
Your phones may still use REFER internally to communicate transfer instructions to your PBX, provided the PBX processes those instructions locally instead of passing them to IXICA.
Do not disable internal transfer functions indiscriminately. Your administrator should distinguish between transfers handled within your telephone system and transfer requests sent across the IXICA SIP trunk.
How should transfers to external telephone numbers work?
Configure your PBX to retain control of the call and bridge it to a separate outbound call, rather than ask IXICA to complete a carrier-side REFER transfer.
For example, when an incoming caller needs to be transferred to an employee’s mobile phone, the PBX can place an outbound call to that mobile number and connect the two call legs. The PBX remains responsible for managing the connection.
The new outbound call should remain subject to your normal calling permissions and destination restrictions. A transfer should not provide a way around the restrictions that apply when a user dials an external number directly.
What should my telephone system administrator configure?
Ask your administrator or PBX provider to review the following:
- Disable carrier-side REFER for the IXICA trunk. Configure transfers to be handled by the PBX instead of relying on IXICA to process a REFER request.
- Restrict external transfer destinations. Permit only the destinations your business requires, and limit international or high-cost calling to authorized users.
- Control access to SIP services. Use appropriate authentication and trusted-source restrictions. Where a Session Border Controller (SBC) is deployed, configure it to reject disallowed REFER requests at the trunk boundary—not merely remove individual headers.
- Maintain and monitor the system. Apply vendor security updates promptly and review unusual outbound calling activity. Network access restrictions are not a substitute for correcting vulnerabilities in the telephone system itself.
Test both internal and external transfers after making configuration changes.
Does using authentication or an SBC change IXICA’s policy?
No. SIP REFER remains unsupported on IXICA SIP trunks.
Authentication, access restrictions, and an SBC can provide important security protections, but they do not change IXICA’s supported transfer method. Your telephone system must remain configured to use PBX-managed transfers.
Does this policy eliminate all toll-fraud risks?
No. Restricting one transfer mechanism is not a complete defence against telephone fraud.
Outbound calling permissions, destination restrictions, secure credentials, access controls, software maintenance, and monitoring remain important safeguards. Customers should review these controls regularly with their telephone system administrator.
Where can I get help?
Contact IXICA Support at support@ixica.com with your PBX make, software version, and a description of the transfer you are trying to perform.
Include whether the destination is an internal extension or an external telephone number, and whether the issue occurs during a blind or attended transfer. This information will help us review the issue and guide you toward an appropriate configuration.
Share
