# Issue with Inbound Route not matching DID from Gupshup WhatsApp SIP Integration
**URL:** https://forums.vitalpbx.org/t/issue-with-inbound-route-not-matching-did-from-gupshup-whatsapp-sip-integration/5680
**Category:** VitalPBX
**Created:** [August 29, 2025, 9:28pm UTC](https://forums.vitalpbx.org/t/issue-with-inbound-route-not-matching-did-from-gupshup-whatsapp-sip-integration/5680 "2025-08-29T21:28:43Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@ArturoPonce25](https://forums.vitalpbx.org/u/ArturoPonce25)
#### Post date: [August 29, 2025, 9:28pm UTC](https://forums.vitalpbx.org/t/issue-with-inbound-route-not-matching-did-from-gupshup-whatsapp-sip-integration/5680/1 "2025-08-29T21:28:43Z")
Hello community,
I’m working on a SIP trunk integration between VitalPBX (v) and Gupshup WhatsApp Voice.
The trunk registers/authenticates correctly, and I can see the INVITE arriving from Gupshup in `sngrep`.
Example INVITE:
```auto
From: +5212XXXXXXXX
To: +521XXXXXXXXX
Codec: opus/48000
```
However, the call fails with `603 Decline`.
I have created an Inbound Route with the following DID Pattern:
```auto
521XXXXXXXX
```
(but also tried with `_X.`, `_521XXXXXXXXXX`, etc.)
When using `_X.` as a catch-all, the system shows the error “Please enter a valid Asterisk pattern.”
**My questions:**
1. How should I properly configure the Inbound Route so that VitalPBX matches the DID including the “+” prefix?
2. Does VitalPBX strip the `+` symbol automatically, or should I always define the DID without the `+`?
3. Is there a recommended way to handle international format DIDs for SIP trunks in VitalPBX?
Any help or suggestions would be appreciated.
Thanks in advance!
---
### Author:  [@system](https://forums.vitalpbx.org/u/system)
#### Post date: [September 28, 2025, 9:29pm UTC](https://forums.vitalpbx.org/t/issue-with-inbound-route-not-matching-did-from-gupshup-whatsapp-sip-integration/5680/2 "2025-09-28T21:29:31Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.