I have a 3CX setup configured with one SIP trunk set to use TLS and SRTP. The TLS side of things seems to be working, and inbound calls are working too. The instance is using the 3CX domain, running on a VMWare server. In UDP / RTP mode, inbound and outbound calls work, with the same authentication and codec selections.
When calling out, I get a not allowed error. Looking at the log initially, this was reported as 488 Not acceptable here/INVITE
Turning on verbose logging, there is something standing out:
The above is a little sanitized. The point is I notice the second last line... Where is this coming from? I vagely recall at some point when first setting up the VMWare instance or during the 3CX installation process, we called this instance pbx.serversdomain.com.au, but ended up selecting the 3CX domain option. How can I change this, and will it solve my problem?
When calling out, I get a not allowed error. Looking at the log initially, this was reported as 488 Not acceptable here/INVITE
Turning on verbose logging, there is something standing out:
Code:
06/01/2020 2:14:46 PM - L:148.1[Extn:666] Sending: OnSendResp Send 488/INVITE from 0.0.0.0:0 tid=2a9e00e6f2e04e38a6815128653d90 Call-ID=4231626818@10_0_0_54:
SIP/2.0 488 Not Acceptable Here
Via: SIP/2.0/TCP 10.0.0.54:60871;branch=z9hG4bK2a9e00e6f2e04e38a6815128653d90;rport=60871;received=111.111.111.111
To: <sip:[email protected];user=phone>;tag=0e35fe70
From: "My Name"<sip:[email protected]>;tag=1312009368
Call-ID: 4231626818@10_0_0_54
CSeq: 3 INVITE
Warning: 499 pbx.serversdomain.com.au "Not Acceptable Here"
Content-Length: 0The above is a little sanitized. The point is I notice the second last line... Where is this coming from? I vagely recall at some point when first setting up the VMWare instance or during the 3CX installation process, we called this instance pbx.serversdomain.com.au, but ended up selecting the 3CX domain option. How can I change this, and will it solve my problem?
