Technical Tip: How to prevent FortiVoice use the calling number as user of the request-URI in a SIP trunk
| Description | This article describes a scenario where SIP INVITE Request-URI is being populated with the calling number instead of the called number. |
| Scope | FortiVoice 7.4.x. |
| Solution | This article describes a scenario where SIP INVITE Request-URI is being populated with the calling number instead of the destination (called) number. The SIP provider could reject or misroute calls because the Request-URI (INVITE sip:user@domain) contains the originating number, while the destination number only appears in the To: header.
Session Initiation Protocol (INVITE) Request-Line: INVITE sip:7820000000@island-world.com:5060 SIP/2.0 Message Header Via: SIP/2.0/UDP 52.87.80.255:5060;rport;branch=z9hG4bKPj68dccd35-1e3a-4e87-badd-d8549ce5d8eb From: <sip:7820000000@island-world.com>;tag=ce920cd4-cc22-4127-877f-d4ab83c70ee1 To: <sip:7830000000@island-world.com> Contact: <sip:7820000000@53.90.91.225:5060> Call-ID: 14e42b3f-65d7-4c0d-8426-d99353715769 To fix the issue, the admin can disable the setting use-username-in-request-uri under the config trunk sip-peer. config trunk sip-peer edit TRUNK set use-username-in-request-uri disable end end |
