AshleyD
(United Kingdom)
February 16, 2022, 12:44pm
1
Has anyone else seen the following and know how to get around it:
INVITE sip:+44XXXXXXXXXX%40192.XXX.XXX.XXX%[email protected] SIP/2.0
Via: SIP/2.0/UDP 10.XXX.XXX.XXX:5060;branch=z9hG4bK36ff634f;rport
Max-Forwards: 70
From: <sip:[email protected] >;tag=as285aa2fa
To: <sip:+44XXXXXXXXXX%40192.XXX.XXX.XXX%[email protected] >
The URI and To user parts contain the target ip and port, which isnt expected.
AshleyD
(United Kingdom)
February 16, 2022, 2:42pm
2
I might be wrong, but it appears this is the trunk name.
david55
(david55)
February 16, 2022, 3:38pm
3
Which channel driver are you using? How did you configure it?
AshleyD
(United Kingdom)
February 16, 2022, 3:57pm
4
Not sure what you mean by channel driver.
This is legacy chan_sip on FreePBX15.
david55
(david55)
February 16, 2022, 3:59pm
5
chan_sip is the channel driver. Awaiting the configuration.
AshleyD
(United Kingdom)
February 16, 2022, 4:04pm
6
Outgoing trunk config:
host=192.XXX.XXX.XXX
qualify=yes
type=peer
sendrpid=pai
trustrpid=yes
context=from-trunk
david55
(david55)
February 16, 2022, 4:13pm
7
I think we need the full log for the call, as it looks like the strange URI could have come on the inbound leg, or be the result of bad customisation of the dialplan.
AshleyD
(United Kingdom)
February 16, 2022, 4:18pm
8
Thanks for your assistance David, on reboot of the device (Note: no changes made to config) the issue is no longer persisting. Very odd!
Stewart1
(Stewart)
February 16, 2022, 4:50pm
9
This is at least the fourth time that this bug has bitten. Unfortunately, none of the victims took the effort to reproduce and report it.
Hello I have a really weird problem.
When I add a new trunk and set it for out calls, when a call comes Asterisk goes trough the call flow and adds @something to the CID before sending the call out.
so far it has been adding an already deleted names of a PJsip extensions.
I pares trought the config files there is no mention of the names that are being added to the CID.
Here is my trunk conf
host=10.10.12.98
port=5060
context=from-trunk
insecure=port,invite
qualify=yes
secret=something1…
1 Like
AshleyD
(United Kingdom)
February 16, 2022, 5:15pm
10
I searched high and low for tickets on this.
If I see the issue again, what logs would the community be interested in?
billsimon
(Bill Simon)
February 16, 2022, 5:36pm
11
If there is a bug in chan_sip, I do not think it will be addressed. Better to reconfigure your trunk for PJSIP.
2 Likes
PitzKey
(Itzik)
February 16, 2022, 9:38pm
12
You can still grab a call trace. If you can, please post one that was sure wrong, and then a good one so we can try to compare.
Please post the call traces via pastebin, see instructions: https://wiki.freepbx.org/display/SUP/Providing+Great+Debug#ProvidingGreatDebug-AsteriskLogs-PartII
system
(system)
Closed
March 19, 2022, 9:39pm
13
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.