- Joined
- Nov 20, 2018
- Messages
- 10
- Reaction score
- 0
According to 3CX this is how a register packet gets its information:
Here is a TCP dump from a working FreePBX using the same trunk:
9:43:47.328183 IP (tos 0x60, ttl 64, id 45793, offset 0, flags [none], proto U$
X.84.79.22.sip > X.84.77.210.sip: [bad udp cksum 9b3c!] SIP, length: 416
REGISTER sip:X.84.79.22 SIP/2.0
Via: SIP/2.0/UDP X.84.79.22:5060;branch=z9hG4bK0c7dddb9;rport
Max-Forwards: 70
From: <sip:[email protected]>;tag=as30ee77c5
To: <sip:[email protected]>
Call-ID: [email protected]
CSeq: 102 REGISTER
Supported: replaces, timer
User-Agent: FPBX-13.0.195.13(13.23.1)
Expires: 120
Contact: <sip:[email protected]:5060>
Content-Length: 0
Here is a TCP dump from 3CX
192.168.2.11.sip > 208.84.77.210.sip: [bad udp cksum 0xe32a -> 0x4b8d!] SIP, length: 567
REGISTER sip:X.84.77.210:5060 SIP/2.0
Via: SIP/2.0/UDP X.168.2.11:5060;branch=z9hG4bK-524287-1---74b84b0722ba561f;rport
Max-Forwards: 70
Contact: <sip:[email protected]:5060;rinstance=821fd3fee80ce31b>
To: <sip:[email protected]:5060>
From: <sip:[email protected]:5060>;tag=46e09852
Call-ID: HQo0gVXnzc3zrpeyDjJBTQ..
CSeq: 1 REGISTER
Expires: 600
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE, UPDATE
Supported: replaces, timer
User-Agent: 3CXPhoneSystem 15.5.15502.6 (15502)
Content-Length: 0
As you can see, the to and from are different. 3CX has our trunk (registrar) (X.84.77.210) in the to and from. FreePBX has the PBX IP (X.84.79.22) in the to and from.
- ““To” header”: The Host Part includes the “Registrar” value set in the 3CX SIP Trunk settings.
- ““From” header”: The Host Part includes the “Registrar” value set in the 3CX SIP Trunk settings.
Here is a TCP dump from a working FreePBX using the same trunk:
9:43:47.328183 IP (tos 0x60, ttl 64, id 45793, offset 0, flags [none], proto U$
X.84.79.22.sip > X.84.77.210.sip: [bad udp cksum 9b3c!] SIP, length: 416
REGISTER sip:X.84.79.22 SIP/2.0
Via: SIP/2.0/UDP X.84.79.22:5060;branch=z9hG4bK0c7dddb9;rport
Max-Forwards: 70
From: <sip:[email protected]>;tag=as30ee77c5
To: <sip:[email protected]>
Call-ID: [email protected]
CSeq: 102 REGISTER
Supported: replaces, timer
User-Agent: FPBX-13.0.195.13(13.23.1)
Expires: 120
Contact: <sip:[email protected]:5060>
Content-Length: 0
Here is a TCP dump from 3CX
192.168.2.11.sip > 208.84.77.210.sip: [bad udp cksum 0xe32a -> 0x4b8d!] SIP, length: 567
REGISTER sip:X.84.77.210:5060 SIP/2.0
Via: SIP/2.0/UDP X.168.2.11:5060;branch=z9hG4bK-524287-1---74b84b0722ba561f;rport
Max-Forwards: 70
Contact: <sip:[email protected]:5060;rinstance=821fd3fee80ce31b>
To: <sip:[email protected]:5060>
From: <sip:[email protected]:5060>;tag=46e09852
Call-ID: HQo0gVXnzc3zrpeyDjJBTQ..
CSeq: 1 REGISTER
Expires: 600
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE, UPDATE
Supported: replaces, timer
User-Agent: 3CXPhoneSystem 15.5.15502.6 (15502)
Content-Length: 0
As you can see, the to and from are different. 3CX has our trunk (registrar) (X.84.77.210) in the to and from. FreePBX has the PBX IP (X.84.79.22) in the to and from.