# incoming route not uses
**URL:** https://forums.vitalpbx.org/t/incoming-route-not-uses/5939
**Category:** VitalPBX
**Created:** [December 22, 2025, 11:20pm UTC](https://forums.vitalpbx.org/t/incoming-route-not-uses/5939 "2025-12-22T23:20:33Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@Tomek\_M](https://forums.vitalpbx.org/u/Tomek_M)
#### Post date: [December 22, 2025, 11:20pm UTC](https://forums.vitalpbx.org/t/incoming-route-not-uses/5939/1 "2025-12-22T23:20:33Z")
Hi, i want to setup vitalpbx to use with voip provider to make and recieve calls.
Trunk is registered:
But when call is made from my mobile to PSTN , in SNGREP I see:
2025/12/22 17:48:07.095393 213.218.117.66:5060 → 10.10.70.145:5060
INVITE sip:s@192.168.55.99:5060;line=nytjror SIP/2.0
Record-Route: sip:213.218.117.66;lr
Record-Route: sip:213.218.117.92;lr=on;ftag=as5ac7fdcc;vsf=AAAAAAAAAAAAAAAAAABBWEMAW19XWlRdGV5bNw--
Via: SIP/2.0/UDP 213.218.117.66:5060;branch=z9hG4bKeb08.abde9de.0
Via: SIP/2.0/UDP 213.218.117.92;branch=z9hG4bKeb08.0054e56.0
Via: SIP/2.0/UDP 213.218.117.77:5060;received=213.218.117.77;branch=z9hG4bK7008331a;rport=5060
Max-Forwards: 68
From: sip:793982\*\*\*@sip.inotel.pl;tag=as5ac7fdcc
To: sip:334876797@sip.inotel.pl:5060
Contact: sip:MYNUMBER793982\*\*\*@213.218.117.77:5060
Call-ID: 763e39426643cec968a85c3145a5cdec@213.218.117.77:5060
CSeq: 102 INVITE
User-Agent: Asterisk PBX
Date: Mon, 22 Dec 2025 16:48:07 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces
Content-Type: application/sdp
Content-Length: 455
2025/12/22 17:48:07.097640 10.10.70.145:5060 → 213.218.117.66:5060
SIP/2.0 484 Address Incomplete
Via: SIP/2.0/UDP 213.218.117.66:5060;rport=5060;received=213.218.117.66;branch=z9hG4bKeb08.abde9de.0
Via: SIP/2.0/UDP 213.218.117.92;branch=z9hG4bKeb08.0054e56.0
Via: SIP/2.0/UDP 213.218.117.77:5060;rport=5060;received=213.218.117.77;branch=z9hG4bK7008331a
Record-Route: sip:213.218.117.66;lr
Record-Route: sip:213.218.117.92;lr;ftag=as5ac7fdcc;vsf=AAAAAAAAAAAAAAAAAABBWEMAW19XWlRdGV5bNw--
Call-ID: 763e39426643cec968a85c3145a5cdec@213.218.117.77:5060
From: sip:793982\*\*\*@sip.inotel.pl;tag=as5ac7fdcc
To: sip:334876797@sip.inotel.pl;tag=a883b123-a3d8-4c10-8fca-7d1e52ae23dd
CSeq: 102 INVITE
Server: VitalPBX
Content-Length: 0
2025/12/22 17:48:07.120702 213.218.117.66:5060 → 10.10.70.145:5060
ACK sip:s@192.168.55.99:5060;line=nytjror SIP/2.0
Via: SIP/2.0/UDP 213.218.117.66:5060;branch=z9hG4bKeb08.abde9de.0
From: sip:793982\*\*\*@sip.inotel.pl;tag=as5ac7fdcc
Call-ID: 763e39426643cec968a85c3145a5cdec@213.218.117.77:5060
To: sip:334876797@sip.inotel.pl;tag=a883b123-a3d8-4c10-8fca-7d1e52ae23dd
CSeq: 102 ACK
Max-Forwards: 70
User-Agent: Inotel SIP Proxy
Content-Length: 0
and in asterisk debug log:
[2025-12-22 17:48:03] DEBUG[1363]: manager.c:7103 process\_message: Running action ‘Command’
[2025-12-22 17:48:07] DEBUG[1267]: res\_pjsip/pjsip\_distributor.c:390 find\_dialog: Could not find matching transaction for Request msg INVITE/cseq=102 (rdata0x7f7368000f98)
[2025-12-22 17:48:07] DEBUG[1267]: res\_pjsip/pjsip\_distributor.c:468 ast\_sip\_get\_distributor\_serializer: Calculated serializer pjsip/distributor-00000025 to use for Request msg INVITE/cseq=102 (rdata0x7f7368000f98)
[2025-12-22 17:48:07] DEBUG[1268]: res\_pjsip\_outbound\_registration.c:733 line\_identify: Determined relationship to outbound registration ‘kodery001’ based on line ‘nytjror’, using configured endpoint ‘kodery001’
[2025-12-22 17:48:07] DEBUG[1268]: res\_pjsip\_session.c:4306 session\_on\_rx\_request: (null session) Request: INVITE
[2025-12-22 17:48:07] DEBUG[1268]: res\_pjsip\_session.c:4141 handle\_new\_invite\_request: Request:
[2025-12-22 17:48:07] DEBUG[1268]: res\_pjsip/pjsip\_distributor.c:468 ast\_sip\_get\_distributor\_serializer: Calculated serializer pjsip/distributor-00000025 to use for Request msg INVITE/cseq=102 (rdata0x7f73680232b8)
[2025-12-22 17:48:07] DEBUG[1268]: chan\_pjsip.c:2914 chan\_pjsip\_session\_begin: kodery001
[2025-12-22 17:48:07] DEBUG[1268]: chan\_pjsip.c:2918 chan\_pjsip\_session\_begin: Direct media no glare mitigation
[2025-12-22 17:48:07] DEBUG[1268]: res\_pjsip\_session.c:3995 new\_invite: kodery001
[2025-12-22 17:48:07] DEBUG[1268]: res\_pjsip\_session.c:4027 new\_invite: kodery001: Call (UDP:213.218.117.66:5060) to extension ‘s’ - partial match
[2025-12-22 17:48:07] DEBUG[1268]: res\_pjsip\_session.c:4597 handle\_outgoing\_response: kodery001: Method is INVITE, Response is 484 Address Incomplete
[2025-12-22 17:48:07] DEBUG[1268]: res\_pjsip\_session/pjsip\_session\_reason\_header.c:60 reason\_header\_outgoing\_response: kodery001: Response Code: 484
[2025-12-22 17:48:07] DEBUG[1268]: res\_pjsip\_session/pjsip\_session\_reason\_header.c:68 reason\_header\_outgoing\_response: kodery001: RC 484 not eligible for Reason header
[2025-12-22 17:48:07] DEBUG[1268]: res\_pjsip\_session.c:4616 handle\_outgoing\_response: kodery001
but i have inbound route like this:
and trunk setup like this:
I need to add that local IP address you see in logs (192.168.55.99) is WAN ip of my router placed at DMZ of provider router. Public IP is set on provider router.
Can You tell me whats wrong?
---
### Author:  [@hlev](https://forums.vitalpbx.org/u/hlev)
#### Post date: [December 24, 2025, 12:21am UTC](https://forums.vitalpbx.org/t/incoming-route-not-uses/5939/2 "2025-12-24T00:21:49Z")
> [@Tomek\_M](#):
>
> INVITE sip:s@192.168.55.99:5060;line=nytjror SIP/2.0
Something is wrong with the INVITE from the provider as they are sending s instead of your expected DID number. This could be something related to an error in how you are registering with them or you have to configure on their side what to send to your pbx.
---
### Author:  [@system](https://forums.vitalpbx.org/u/system)
#### Post date: [January 23, 2026, 12:21am UTC](https://forums.vitalpbx.org/t/incoming-route-not-uses/5939/3 "2026-01-23T00:21:53Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.