Hi,
As the title says this is what I have problems with. However, I can register Zoiper both over TCP/UDP.
<EDIT>
I've read the post underneath suggesting register phones with TCP which I also have tried to no avail
Setup: AWS
I currently have a freeswitch up and running on AWS which works. I can register the same phone to freeswitch but not to fusionpbx.
On FusionPBX I have everything else working except registering the SNOM phones. I've setup provisioning of a SNOM phone which also works.
Tried with one identity to register with fusionpbx and the other to register with freeswitch, The one to freeswitch registers.
If I use the same extension ID/Passwd on zoiper it registers.
I've whitelisted all necessary IPs in
/etc/fail2ban/jail.local separated by space
[DEFAULT]
ignoreip =
I don't get a reply to the registration message.
FusionPBX on AWS registration message
2019/02/06 07:36:05.857534 <public_ip>:51857 -> <internal_aws_ip>:5060
REGISTER sip:foo.bar.com:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.10.100:51857;branch=z9hG4bK-fozqte1ckhm7;rport
From: "fusionpbx" <sip:fusionpbx_ext@foo.bar.com:5060>;tag=clta1uho86
To: "fusionpbx" <sip:fusionpbx_ext@foo.bar.com:5060>
Call-ID: 313534393334333431373338333730-2p0k5q332hd8
CSeq: 206 REGISTER
Max-Forwards: 70
User-Agent: snom715/10.1.33.33
Contact: <sip:fusionpbx_ext@192.168.10.100:51857;line=2ev93p2o>;reg-id=1;q=1.0;+sip.instance="<urn:uuid:snom_uuid>";audio;mobility="fixed";duplex="full";description="snom715";actor="principal";events="dialog"
ethods="INVITE,ACK,CANCEL,BYE,REFER,OPTIONS,NOTIFY,SUBSCRIBE,PRACK,MESSAGE,INFO"
Allow-Events: dialog, talk, hold, check-sync
X-Real-IP: <LAN_IP>
Supported: path, gruu
Expires: 120
Content-Length: 0
Freeswitch on AWS registration message
2019/02/06 07:50:06.850678 <public_ip>:37970 -> <internal_aws_ip>:5070
REGISTER sip:foo.bar.com:5070 SIP/2.0
Via: SIP/2.0/UDP <public_ip>:37970;branch=z9hG4bK-cwi25abcv1fk;rport
From: "freeswitch" <sip:my_freeswitch_ext@foo.bar.com:5070>;tag=p4j952j3uw
To: "freeswitch" <sip:my_freeswitch_ext@foo.bar.com:5070>
Call-ID: 313534393334333431373432333438-jid77gvdpt2i
CSeq: 1121 REGISTER
Max-Forwards: 70
User-Agent: snom715/10.1.33.33
Contact: <sip:my_freeswitch_ext@<public_ip>:37970;line=voh97zyu>;reg-id=1;q=1.0;+sip.instance="<urn:uuid:snom_uuid>";audio;mobility="fixed";duplex="full";description="snom715";actor="principal";events="dialog"
ethods="INVITE,ACK,CANCEL,BYE,REFER,OPTIONS,NOTIFY,SUBSCRIBE,PRACK,MESSAGE,INFO"
Allow-Events: dialog, talk, hold, check-sync
X-Real-IP: <LAN_IP>
Supported: path, gruu
Authorization: Digest username="my_freeswitch_ext",realm="foo.bar.com",nonce="ab83718e-315d-46f1-bef6-d2dfbd36642c",uri="sip:foo.bar.com:5070",qop=auth,nc=00001150,cnonce="5aaab7b6",response="0d53e3242d4f2958f68193113d81fa20",al
rithm=MD5
Expires: 120
Content-Length: 0
What I can deduce from these messages are that the authorization is not coming through.
Attached is the output from: iptables -L -n
Any ideas how to go about this?
As the title says this is what I have problems with. However, I can register Zoiper both over TCP/UDP.
<EDIT>
I've read the post underneath suggesting register phones with TCP which I also have tried to no avail
Setup: AWS
I currently have a freeswitch up and running on AWS which works. I can register the same phone to freeswitch but not to fusionpbx.
On FusionPBX I have everything else working except registering the SNOM phones. I've setup provisioning of a SNOM phone which also works.
Tried with one identity to register with fusionpbx and the other to register with freeswitch, The one to freeswitch registers.
If I use the same extension ID/Passwd on zoiper it registers.
I've whitelisted all necessary IPs in
/etc/fail2ban/jail.local separated by space
[DEFAULT]
ignoreip =
I don't get a reply to the registration message.
FusionPBX on AWS registration message
2019/02/06 07:36:05.857534 <public_ip>:51857 -> <internal_aws_ip>:5060
REGISTER sip:foo.bar.com:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.10.100:51857;branch=z9hG4bK-fozqte1ckhm7;rport
From: "fusionpbx" <sip:fusionpbx_ext@foo.bar.com:5060>;tag=clta1uho86
To: "fusionpbx" <sip:fusionpbx_ext@foo.bar.com:5060>
Call-ID: 313534393334333431373338333730-2p0k5q332hd8
CSeq: 206 REGISTER
Max-Forwards: 70
User-Agent: snom715/10.1.33.33
Contact: <sip:fusionpbx_ext@192.168.10.100:51857;line=2ev93p2o>;reg-id=1;q=1.0;+sip.instance="<urn:uuid:snom_uuid>";audio;mobility="fixed";duplex="full";description="snom715";actor="principal";events="dialog"
ethods="INVITE,ACK,CANCEL,BYE,REFER,OPTIONS,NOTIFY,SUBSCRIBE,PRACK,MESSAGE,INFO"
Allow-Events: dialog, talk, hold, check-sync
X-Real-IP: <LAN_IP>
Supported: path, gruu
Expires: 120
Content-Length: 0
Freeswitch on AWS registration message
2019/02/06 07:50:06.850678 <public_ip>:37970 -> <internal_aws_ip>:5070
REGISTER sip:foo.bar.com:5070 SIP/2.0
Via: SIP/2.0/UDP <public_ip>:37970;branch=z9hG4bK-cwi25abcv1fk;rport
From: "freeswitch" <sip:my_freeswitch_ext@foo.bar.com:5070>;tag=p4j952j3uw
To: "freeswitch" <sip:my_freeswitch_ext@foo.bar.com:5070>
Call-ID: 313534393334333431373432333438-jid77gvdpt2i
CSeq: 1121 REGISTER
Max-Forwards: 70
User-Agent: snom715/10.1.33.33
Contact: <sip:my_freeswitch_ext@<public_ip>:37970;line=voh97zyu>;reg-id=1;q=1.0;+sip.instance="<urn:uuid:snom_uuid>";audio;mobility="fixed";duplex="full";description="snom715";actor="principal";events="dialog"
ethods="INVITE,ACK,CANCEL,BYE,REFER,OPTIONS,NOTIFY,SUBSCRIBE,PRACK,MESSAGE,INFO"
Allow-Events: dialog, talk, hold, check-sync
X-Real-IP: <LAN_IP>
Supported: path, gruu
Authorization: Digest username="my_freeswitch_ext",realm="foo.bar.com",nonce="ab83718e-315d-46f1-bef6-d2dfbd36642c",uri="sip:foo.bar.com:5070",qop=auth,nc=00001150,cnonce="5aaab7b6",response="0d53e3242d4f2958f68193113d81fa20",al
rithm=MD5
Expires: 120
Content-Length: 0
What I can deduce from these messages are that the authorization is not coming through.
Attached is the output from: iptables -L -n
Any ideas how to go about this?
Last edited: