Solved Vitelity w/ 3CX not receiving calls

[Duggan Corp]

installed 3CX on-site, purchased a trunk from Vitelity but can't receive calls. i've seen the other threads here about similar issue. i am not on location so i cannot test outbound at this moment but can tomorrow. i believe the debian firewall is blocking the port(s) but i am unsure. i also have a hardware firewall but have the server 192.168.2.3 on DMZ. 3CX automatically opened the ports during install as i see them with a quick iptables -L command. please see 3CX activity log below (i have redacted any identifying bits)

09/07/2017 4:52:54 PM - [CM102001]: Authentication failed for AuthFail Recv Req REGISTER from 127.0.0.1:5488 tid=32186a556e19547b Call-ID=ZL1CoOEvmaIZfa-tX_AcOQ..: REGISTER sip:XXXX.west.3cx.us SIP/2.0 Via: SIP/2.0/UDP 127.0.0.1:5488;branch=z9hG4bK-524287-1---32186a556e19547b;rport=5488 Max-Forwards: 70 Contact: <sip:[email protected]:5488;rinstance=c4449f8864e329c3> To: "First Name Test Last Name Test"<sip:[email protected]> From: "First Name Test Last Name Test"<sip:[email protected]>;tag=96e3440e Call-ID: ZL1CoOEvmaIZfa-tX_AcOQ.. CSeq: 22 REGISTER Expires: 120 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE Proxy-Authorization: Digest username="4vzcmzc",realm="3CXPhoneSystem",nonce="414d535959b1dbd620:ee042520aa3f639d689257f08bfbfba1",uri="sip:XXXX.west.3cx.us",response="3363bc8b9e8a3280c83e5ed72606ca9b",algorithm=MD5 Supported: replaces User-Agent: 3CX Dialer for Ext.000 Content-Length: 0 ; Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings
09/07/2017 4:52:54 PM - [Auth] Provided response (3363bc8b9e8a3280c83e5ed72606ca9b doesn't match calc. (7056afadddefebe2d9dc76aeb0d747ab)
09/07/2017 4:49:41 PM - Call to T:Extn:000@[Dev:sip:[email protected]:5488;rinstance=c4449f8864e329c3] from L:3.1[Ivr: PlayFile] failed, cause: Cause: 404 Not Found/INVITE from 127.0.0.1:5488
09/07/2017 4:49:41 PM - [CM503003]: Call(C:3): Call to <sip:[email protected]:5060> has failed; Cause: 404 Not Found/INVITE from 127.0.0.1:5488
09/07/2017 4:49:41 PM - [Flow] Target endpoint for 5555555555 can not be built!
09/07/2017 4:24:08 PM - PBX has dropped a message with 'User-Agent: friendly-scanner' from IP 163.172.147.216 because it is on blocked UAs list
09/07/2017 4:19:56 PM - There's another STUN server that resolves to the same IP: 158.69.11.6:3478; ignored

09/06/2017 4:19:55 PM - Load license has failed, error: 5

09/06/2017 4:19:47 PM - Set log verbosity to MaxLevel = 2, Severity mask = 7
09/06/2017 4:19:47 PM - Loading Contact records from database
09/06/2017 4:19:29 PM - Currently active calls [none]
09/06/2017 4:19:27 PM - Supported Mime Type added:MESSAGE(x-chat/control)
09/06/2017 4:19:27 PM - User-Agent's that is configured to ignore: friendly-scanner,sipsak,smap,Elite 1.0 Brcm Callctrl,sipcli,VaxSIPUserAgent,VaxIPUserAgent,PortSIP,friendly-request,sip-scan,sipvicious,sundayddr,iWar,SIVuS,Gulp,sipv,siparmyknife,Test Agent,eyeBeam release 3006o stamp 17551,SIP Call,PortSIP VoIP,Conaito
09/06/2017 4:19:27 PM - There's no valid Domain certificate/key for server's IP 192.168.2.3
09/06/2017 4:19:27 PM - Adding secure SIP transport at 192.168.2.3:5061
09/06/2017 4:19:27 PM - Transport 0.0.0.0:5060 is joined to SIP multicast group (interface IP: 192.168.2.3)
09/06/2017 4:19:27 PM - Folder for SSL certificates : /var/lib/3cxpbx/Instance1/Bin/Cert
09/06/2017 4:19:27 PM - ** Initializing SIP stack **
09/06/2017 4:19:27 PM - [CM501006]: Default Local IP address: [192.168.2.3]
09/06/2017 4:19:27 PM - Configuration-specified SIP IP () differs from default local IP reported by system (192.168.2.3)
09/06/2017 4:19:27 PM - [CM501002]: Version: 15.5.0.3849
09/06/2017 4:19:27 PM - [CM501001]: Start 3CX PhoneSystem Call Manager
09/06/2017 4:19:27 PM - [CM501007]: *** Started Calls Controller thread ***
09/06/2017 4:19:27 PM - Startup completed for leo:5485/DBProvider
09/06/2017 4:19:27 PM - [EC200001]: Configuration server is connected: application:leo:5485/DBProvider local:127.0.0.1:35019 remote:127.0.0.1:5485
09/06/2017 4:19:27 PM - Application connected:leo:5485/DBProvider
09/06/2017 4:19:27 PM - Start management threads for leo:5485/DBProvider
09/06/2017 4:19:27 PM - Timezone offset: -420 min.

so i believe there's a possible license issue even though i am using freemium now, registration issue with SIP Trunk provider, and a firewall issue? any assistance is greatly appreciated!

 

[Duggan Corp]

Step 1: Configure the ports for your SIP Trunk / VoIP Provider
Open the following ports to allow 3CX Phone System to communicate with the VoIP Provider/SIP Trunk & WebRTC:

• Port 5060 (inbound, UDP) for SIP communications
• Port 9000-9500 (inbound, UDP) for RTP (Audio) communications, which contain the actual call. Each call requires 2 RTP ports, one to control the call and one for the call data. Therefore, you must open twice as many ports if you wish to support simultaneous calls.

let me go ahead and try step 1 first....

 

[leejor]

[CM503003]: Call(C:3): Call to <sip:[email protected]:5060> has failed; Cause: 404 Not Found/INVITE from 127.0.0.1:5488

Was there a valid extension where 000 is? Apparently ...it can't be found. Have you tried a really simple inbound rule to a single extension?

 

[Duggan Corp]

[CM503003]: Call(C:3): Call to <sip:[email protected]:5060> has failed; Cause: 404 Not Found/INVITE from 127.0.0.1:5488

Was there a valid extension where 000 is? Apparently ...it can't be found. Have you tried a really simple inbound rule to a single extension?

there is a valid extension at 000 and i believe inbound rules are set accurately. furthermore, i ran the firewall test and passed everything. i have tested both outbound and inbound, neither of which work.
i have some screenshots to share along with some interesting logs. please see below

09/08/2017 1:44:01 PM - [Flow] Target endpoint for XXXXXXXXXX can not be built!
09/08/2017 1:41:36 PM - [Flow] Target endpoint for XXXXXXXXXX can not be built!

09/08/2017 9:25:29 AM - Set log verbosity to MaxLevel = 2, Severity mask = 7
09/08/2017 9:25:29 AM - Loading Contact records from database
09/08/2017 9:25:29 AM - Failed to add outbound CID reformating rule for DN:10000: <Rules />
09/08/2017 9:25:29 AM - Failed to add outbound CID reformating rule for DN:10000: <Rules />
09/08/2017 9:25:29 AM - Line 10000 has been updated from DB
09/08/2017 9:25:29 AM - Dev(1414411623):[sip:XXXXXXXXXXXXt:5060 / XXXXXXX]: PBX contact is set to STUN resolved public IP: <sip:XXXXXXXXXX:5060>
09/08/2017 9:25:29 AM - Found transport 0.0.0.0:5060/UDP
09/08/2017 9:25:29 AM - Looking for transport to destination <sip:@XXXXXXXX:5060>
09/08/2017 9:25:29 AM - License loaded sucessfully. License level: 1
09/08/2017 9:25:29 AM - Supported Mime Type added:MESSAGE(x-chat/control)
09/08/2017 9:25:29 AM - User-Agent's that is configured to ignore: friendly-scanner,sipsak,smap,Elite 1.0 Brcm Callctrl,sipcli,VaxSIPUserAgent,VaxIPUserAgent,PortSIP,friendly-request,sip-scan,sipvicious,sundayddr,iWar,SIVuS,Gulp,sipv,siparmyknife,Test Agent,eyeBeam release 3006o stamp 17551,SIP Call,PortSIP VoIP,Conaito,Ozeki,Gbomba,MizuPhone,VoIP v11.2.4,VoIP SIP v11.0.0,VoIP v11.1.2
09/08/2017 9:25:29 AM - There's no valid Domain certificate/key for server's IP 192.168.2.3
09/08/2017 9:25:29 AM - Adding secure SIP transport at 192.168.2.3:5061
09/08/2017 9:25:29 AM - Transport 0.0.0.0:5060 is joined to SIP multicast group (interface IP: 192.168.2.3)
09/08/2017 9:25:29 AM - Folder for SSL certificates : /var/lib/3cxpbx/Instance1/Bin/Cert
09/08/2017 9:25:29 AM - ** Initializing SIP stack **
09/08/2017 9:25:29 AM - [CM501006]: Default Local IP address: [192.168.2.3]
09/08/2017 9:25:29 AM - Configuration-specified SIP IP () differs from default local IP reported by system (192.168.2.3)
09/08/2017 9:25:29 AM - [CM501002]: Version: 15.5.0.3849
09/08/2017 9:25:29 AM - [CM501001]: Start 3CX PhoneSystem Call Manager
09/08/2017 9:25:29 AM - [CM501007]: *** Started Calls Controller thread ***
09/08/2017 9:25:29 AM - Startup completed for leo:5485/DBProvider
09/08/2017 9:25:29 AM - [EC200001]: Configuration server is connected: application:leo:5485/DBProvider local:127.0.0.1:41677 remote:127.0.0.1:5485
09/08/2017 9:25:29 AM - Application connected:leo:5485/DBProvider
09/08/2017 9:25:29 AM - Start management threads for leo:5485/DBProvider
09/08/2017 9:25:29 AM - Timezone offset: -420 min.

 

[leejor]

What about a log of a failed outbound call. Is it being sent to the provider then rejected or does it even make it that far? Did this issue just start, or has it ever worked?

 

[Duggan Corp]

What about a log of a failed outbound call. Is it being sent to the provider then rejected or does it even make it that far? Did this issue just start, or has it ever worked?

that's a good question and i posed it to Vitelity, which explained it wasn't reaching them. at that time, support over there told me to change the outbound ip to same inbound ip address within 3CX and viola! OK, so 3CX can receive calls and make them, however there is no audio. my ports for 9000-9050 are opened up. ideas?

 

[YiannisH_3CX]

Do you have one way audio or is there no audio both ways?

 

[leejor]

there is no audio. my ports for 9000-9050 are opened up. ideas?

Is that a typo, have you opened ports beyond 9050?

https://www.3cx.com/blog/docs/ports-used/

 

[Duggan Corp]

Is that a typo, have you opened ports beyond 9050?

https://www.3cx.com/blog/docs/ports-used/

not a typo, i only opened 9000-9050. thought that was enough. i just purchased a standard license key and as i understand it, i have to reinstall the system now? i will be doing that and giving this another go from the 3CX debian ISO instead of previously used debian 8.8 ISO with 3CX installed post OS.

 

[Duggan Corp]

close this out. houston, we have lift off.
for those who want to know how i fixed everything: i reinstalled because i had bought the standard key. in doing so, i opted for the debain with 3CX presinstalled. all ports are already configured, which i think did the trick vs me trying to figure my way through iptables. everything is operational!! thank you leejor for you added assistance along the way!

 

[YiannisH_3CX]

Glad to hear the issue is now resolved and thank you for sharing your solution