- Joined
- Aug 27, 2019
- Messages
- 83
- Reaction score
- 16
Hello,
Today I experimented a bit with SIP TLS between our 3cx and our SBC. I noticed the following.
Even with the register, the 3cx sends its IP address instead of its host name, despite activated TLS. For later calls you can change this in the output parameters. But the registration with the IP on the SBC is actually not correct for TLS. This requires a setting on the SBC that worsens security by ignoring requests with IPs in the header during the certificate check.
I can't find a parameter for this in the options.
Do you have an idea? Or is the behavior of the 3cx hardcoded?
-----------
REGISTER sip:sbc.XXXXXXXXX.de:5063;transport=TLS SIP/2.0
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE, UPDATE
.
.
.
Contact: <sip:3cx-stage@172.30.36.137:5061;transport=TLS;rinstance=cff9397e8f9d459c>
Content-Length: 0
Cseq: 2 REGISTER
Expires: 60
From: <sip:[email protected]:5063;transport=TLS>;tag=bcef985d
Max-Forwards: 70
Supported: replaces, timer
To: <sip:[email protected]:5063;transport=TLS>
Via: SIP/2.0/TLS 172.30.36.137:5061;received=172.30.36.137;rport;branch=z9hG4bK-524287-1---4e6143423dd41e2a
Content-Length: 0
-----------
Today I experimented a bit with SIP TLS between our 3cx and our SBC. I noticed the following.
Even with the register, the 3cx sends its IP address instead of its host name, despite activated TLS. For later calls you can change this in the output parameters. But the registration with the IP on the SBC is actually not correct for TLS. This requires a setting on the SBC that worsens security by ignoring requests with IPs in the header during the certificate check.
I can't find a parameter for this in the options.
Do you have an idea? Or is the behavior of the 3cx hardcoded?
-----------
REGISTER sip:sbc.XXXXXXXXX.de:5063;transport=TLS SIP/2.0
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE, UPDATE
.
.
.
Contact: <sip:3cx-stage@172.30.36.137:5061;transport=TLS;rinstance=cff9397e8f9d459c>
Content-Length: 0
Cseq: 2 REGISTER
Expires: 60
From: <sip:[email protected]:5063;transport=TLS>;tag=bcef985d
Max-Forwards: 70
Supported: replaces, timer
To: <sip:[email protected]:5063;transport=TLS>
Via: SIP/2.0/TLS 172.30.36.137:5061;received=172.30.36.137;rport;branch=z9hG4bK-524287-1---4e6143423dd41e2a
Content-Length: 0
-----------