I have chansip binding to port 5060 and pjsip to 5160.
Running into a strange problem when I create a new chansip endpoint and making a call to it.
The Invite the server is sending is messed up.
INVITE sip:18009220204%40Vitelity-Outbound_PJSIP@18.104.22.168 SIP/2.0
I am dialing 18009220204.
Why is the server turning this into 18009220204%40Vitelity-Outbound_PJSIP?
Vitelity-Outbound_PJSIP used to be a pjsip trunk endpoint with the same trunk host IP address, that has been deleted and does no longer exist.
Has anybody seen this before?
INVITE sip:18009220204%40Vitelity-Outbound_PJSIP@22.214.171.124 SIP/2.0 Via: SIP/2.0/UDP xxx.xxx.xx.xx:5060;branch=z9hG4bK5ad22270;rport Max-Forwards: 70 From: <sip:email@example.com>;tag=as77bfbd88 To: <sip:18009220204%40Vitelity-Outbound_PJSIP@126.96.36.199> Contact: <sip:firstname.lastname@example.org:5060> Call-ID: email@example.com:5060 CSeq: 102 INVITE User-Agent: FPBX-188.8.131.52(13.18.3) Date: Fri, 25 May 2018 15:35:08 GMT Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE Supported: replaces, timer Content-Type: application/sdp Content-Length: 343 Chansip trunk settings:
[Vitelity_Out] host=184.108.40.206 type=peer context=from-trunk