Hi everyone! I’ve tried several times this day to get it work, and i got in the right direction. The connection (trunk) to my FreePBX system and the SPA3000 registers. In the FreePBX Dashboard, it shows me ‘‘1 trunk online’’. In the SPA3000 it says me ‘‘registered’’. I didn’t get the message (when i want to call outbound) ‘‘all circuits are busy now’’. But, i get a unavailable tone when i dial the number i want to dial. My Openstage 20 shows me on the display a ‘‘cross’’ when i try to dial. In the log files of FreePBX, it shows me this:
[2016-05-28 19:54:02] VERBOSE[31825][C-00000014] app_dial.c: – Called SIP/31464377605/0639051650
[2016-05-28 19:54:02] VERBOSE[1947] chan_sip.c:
<— SIP read from UDP:172.16.2.113:5060 —>
SIP/2.0 100 Trying
To: sip:[email protected]:5060
From: sip:[email protected];tag=as6f5f61c2
Call-ID: [email protected]:5060
CSeq: 102 INVITE
Via: SIP/2.0/UDP 172.16.2.112:5060;branch=z9hG4bK42116cc7
Server: Linksys/SPA3000-3.1.20(GW)
Content-Length: 0
<------------->
[2016-05-28 19:54:02] VERBOSE[1947] chan_sip.c: — (8 headers 0 lines) —
[2016-05-28 19:54:02] VERBOSE[1947] chan_sip.c:
<— SIP read from UDP:172.16.2.113:5060 —>
SIP/2.0 504 Service Unavailable
To: sip:[email protected]:5060;tag=5d4d02738be15b62i1
From: sip:[email protected];tag=as6f5f61c2
Call-ID: [email protected]:5060
CSeq: 102 INVITE
Via: SIP/2.0/UDP 172.16.2.112:5060;branch=z9hG4bK42116cc7
Server: Linksys/SPA3000-3.1.20(GW)
Content-Length: 0
Sometimes, it shows me this (a OK message):
[2016-05-28 20:04:28] VERBOSE[1947] chan_sip.c:
<— SIP read from UDP:172.16.2.113:5060 —>
SIP/2.0 200 OK
To: sip:172.16.2.113;tag=5d4d02738be15b62i1
From: “Unknown” sip:[email protected];tag=as0f6c8239
Call-ID: [email protected]:5060
CSeq: 102 OPTIONS
Via: SIP/2.0/UDP 172.16.2.112:5060;branch=z9hG4bK761bd8bc
Server: Linksys/SPA3000-3.1.20(GW)
Content-Length: 0
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER
Supported: x-sipura, replaces
<------------->
[2016-05-28 20:04:28] VERBOSE[1947] chan_sip.c: — (10 headers 0 lines) —
[2016-05-28 20:04:28] VERBOSE[1947] chan_sip.c: Really destroying SIP dialog ‘[email protected]:5060’ Method: OPTIONS
[2016-05-28 20:04:28] VERBOSE[1947] chan_sip.c: Reliably Transmitting (no NAT) to 172.16.2.113:5060:
OPTIONS sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 172.16.2.112:5060;branch=z9hG4bK15207316
Max-Forwards: 70
From: “Unknown” sip:[email protected];tag=as72398964
To: sip:[email protected]:5060
Contact: sip:[email protected]:5060
Call-ID: [email protected]:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-13.0.74(11.21.0)
Date: Sat, 28 May 2016 19:04:28 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0
[2016-05-28 20:04:28] VERBOSE[1947] chan_sip.c:
<— SIP read from UDP:172.16.2.113:5060 —>
SIP/2.0 200 OK
To: sip:[email protected]:5060;tag=5d4d02738be15b62i1
From: “Unknown” sip:[email protected];tag=as72398964
Call-ID: [email protected]:5060
CSeq: 102 OPTIONS
Via: SIP/2.0/UDP 172.16.2.112:5060;branch=z9hG4bK15207316
Server: Linksys/SPA3000-3.1.20(GW)
Content-Length: 0
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER
Supported: x-sipura, replaces
<------------->
[2016-05-28 20:04:28] VERBOSE[1947] chan_sip.c: — (10 headers 0 lines) —
[2016-05-28 20:04:28] VERBOSE[1947] chan_sip.c: Really destroying SIP dialog ‘[email protected]:5060’ Method: OPTIONS
[2016-05-28 20:05:28] VERBOSE[1947] chan_sip.c: Reliably Transmitting (no NAT) to 172.16.2.113:5060:
OPTIONS sip:172.16.2.113 SIP/2.0
Via: SIP/2.0/UDP 172.16.2.112:5060;branch=z9hG4bK74bbfb74
Max-Forwards: 70
From: “Unknown” sip:[email protected];tag=as0af35be8
To: sip:172.16.2.113
Contact: sip:[email protected]:5060
Call-ID: [email protected]:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-13.0.74(11.21.0)
Date: Sat, 28 May 2016 19:05:28 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0
[2016-05-28 20:05:28] VERBOSE[1947] chan_sip.c:
<— SIP read from UDP:172.16.2.113:5060 —>
SIP/2.0 200 OK
To: sip:172.16.2.113;tag=5d4d02738be15b62i1
From: “Unknown” sip:[email protected];tag=as0af35be8
Call-ID: [email protected]:5060
CSeq: 102 OPTIONS
Via: SIP/2.0/UDP 172.16.2.112:5060;branch=z9hG4bK74bbfb74
Server: Linksys/SPA3000-3.1.20(GW)
Content-Length: 0
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER
Supported: x-sipura, replaces
<------------->
[2016-05-28 20:05:28] VERBOSE[1947] chan_sip.c: — (10 headers 0 lines) —
[2016-05-28 20:05:28] VERBOSE[1947] chan_sip.c: Really destroying SIP dialog ‘[email protected]:5060’ Method: OPTIONS
[2016-05-28 20:05:28] VERBOSE[1947] chan_sip.c: Reliably Transmitting (no NAT) to 172.16.2.113:5060:
OPTIONS sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 172.16.2.112:5060;branch=z9hG4bK5b5cdbb4
Max-Forwards: 70
From: “Unknown” sip:[email protected];tag=as46d024f0
To: sip:[email protected]:5060
Contact: sip:[email protected]:5060
Call-ID: [email protected]:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-13.0.74(11.21.0)
Date: Sat, 28 May 2016 19:05:28 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0
[2016-05-28 20:05:28] VERBOSE[1947] chan_sip.c:
<— SIP read from UDP:172.16.2.113:5060 —>
SIP/2.0 200 OK
To: sip:[email protected]:5060;tag=5d4d02738be15b62i1
From: “Unknown” sip:[email protected];tag=as46d024f0
Call-ID: [email protected]:5060
CSeq: 102 OPTIONS
Via: SIP/2.0/UDP 172.16.2.112:5060;branch=z9hG4bK5b5cdbb4
Server: Linksys/SPA3000-3.1.20(GW)
Content-Length: 0
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER
Supported: x-sipura, replaces
<------------->
[2016-05-28 20:05:28] VERBOSE[1947] chan_sip.c: — (10 headers 0 lines) —
[2016-05-28 20:05:28] VERBOSE[1947] chan_sip.c: Really destroying SIP dialog ‘[email protected]:5060’ Method: OPTIONS
I don’t know what this means, but i think that the connection between the SPA3000 and FreePBX works, but the SPA3000 can’t dial the number
whereby i got the ‘‘504 service unavailable’’’ message. Ofcourse i can recieve calls, but outbound? No, that’s without any reason, not possible.