TIPS IPBX-2020 and Bulkvs

B

Brianmac

Active Member
Joined
Oct 7, 2014
Messages
676
Reaction score
194
I just setup on Vultr Ipbx-2020 and using BulkVS. I made one call incoming and it worked. I cannot receive any more incoming calls. Below is what is in my log.
Any ideas? I get the number is not in service, blah, blah, blah. These are the 4 IP from Bulk that I have...

Thanks,
Brian

[2020-04-10 10:43:14] ERROR[1921] netsock2.c: getaddrinfo("76.8.29.198", "(null)", ...): Name or service not known
[2020-04-10 10:43:14] ERROR[1921] netsock2.c: getaddrinfo("76.8.29.198", "(null)", ...): Name or service not known
[2020-04-10 10:43:14] WARNING[1921] acl.c: Unable to lookup '76.8.29.198'
[2020-04-10 10:43:14] ERROR[1921] netsock2.c: getaddrinfo("69.12.88.198", "(null)", ...): Name or service not known
[2020-04-10 10:43:14] ERROR[1921] netsock2.c: getaddrinfo("69.12.88.198", "(null)", ...): Name or service not known
[2020-04-10 10:43:14] WARNING[1921] acl.c: Unable to lookup '69.12.88.198'
[2020-04-10 10:43:14] ERROR[1921] netsock2.c: getaddrinfo("162.249.171.198", "(null)", ...): Name or service not known
[2020-04-10 10:43:14] ERROR[1921] netsock2.c: getaddrinfo("162.249.171.198", "(null)", ...): Name or service not known
[2020-04-10 10:43:14] WARNING[1921] acl.c: Unable to lookup '162.249.171.198'
[2020-04-10 10:48:14] ERROR[1921] netsock2.c: getaddrinfo("76.8.29.198", "(null)", ...): Name or service not known
[2020-04-10 10:48:14] ERROR[1921] netsock2.c: getaddrinfo("76.8.29.198", "(null)", ...): Name or service not known
[2020-04-10 10:48:14] WARNING[1921] acl.c: Unable to lookup '76.8.29.198'
[2020-04-10 10:48:14] ERROR[1921] netsock2.c: getaddrinfo("69.12.88.198", "(null)", ...): Name or service not known
[2020-04-10 10:48:14] ERROR[1921] netsock2.c: getaddrinfo("69.12.88.198", "(null)", ...): Name or service not known
[2020-04-10 10:48:14] WARNING[1921] acl.c: Unable to lookup '69.12.88.198'
[2020-04-10 10:48:14] ERROR[1921] netsock2.c: getaddrinfo("162.249.171.198", "(null)", ...): Name or service not known
[2020-04-10 10:48:14] ERROR[1921] netsock2.c: getaddrinfo("162.249.171.198", "(null)", ...): Name or service not known
[2020-04-10 10:48:14] WARNING[1921] acl.c: Unable to lookup '162.249.171.198'
[2020-04-10 10:53:14] ERROR[1921] netsock2.c: getaddrinfo("76.8.29.198", "(null)", ...): Name or service not known
[2020-04-10 10:53:14] ERROR[1921] netsock2.c: getaddrinfo("76.8.29.198", "(null)", ...): Name or service not known
[2020-04-10 10:53:14] WARNING[1921] acl.c: Unable to lookup '76.8.29.198'
[2020-04-10 10:53:14] ERROR[1921] netsock2.c: getaddrinfo("69.12.88.198", "(null)", ...): Name or service not known
[2020-04-10 10:53:14] ERROR[1921] netsock2.c: getaddrinfo("69.12.88.198", "(null)", ...): Name or service not known
[2020-04-10 10:53:14] WARNING[1921] acl.c: Unable to lookup '69.12.88.198'
[2020-04-10 10:53:14] ERROR[1921] netsock2.c: getaddrinfo("162.249.171.198", "(null)", ...): Name or service not known
[2020-04-10 10:53:14] ERROR[1921] netsock2.c: getaddrinfo("162.249.171.198", "(null)", ...): Name or service not known
[2020-04-10 10:53:14] WARNING[1921] acl.c: Unable to lookup '162.249.171.198'
Click to expand...
 
I wound up having to register my inbound trunk to their servers to get inbound to work correctly. I am using PJSIP to connect with them.
 
Brianmac said:
These are the 4 IP from Bulk that I have...
Click to expand...
Are you sure you have all 4 IPs there? There should be one starting with 199.255. for origination and I don't see it in your snapshot.
 
I have these:
199.255.157.198
162.249.171.198
69.12.88.198
76.8.29.198
 
OK, ready to start drinking at 9:41am(ok, drank last night, so might wait till 10am - I'm not a lush!!!):wacko:

So, I have been going crazy. Got a good incoming call yesterday, then later in the day could NOT get a call in. I kept getting, "Number not in service...I finally figured out the issue. Calling from my home phone(Anveo) gives me this problem. when I call from my cell phone, no issues...

any ideas?
Thanks,
brian

PS - call from callcentric works fine, too
 
Report it to BulkVS. It's a problem with their upstream provider.
 
After I do that, can I have a cocktail.....?

Thanks Ward!
brian
 
Call logs are different from Anveo(failed) and Callcentric\At&t(succeed) ? Remember I am dialing the same number from two different phone numbers(anveo – bad),(callcentric-good or AT&T-good).

Calling from Anveo, I get:
[2020-04-11 10:35:39] VERBOSE[7775][C-0000000e] pbx.c: Executing [1234567890@from-sip-external:1] NoOp("SIP/76.8.29.198-0000000d", "Received incoming SIP connection from unknown peer to 1234567890") in new stack


but not from Callcentric or AT&T for that matter:
[2020-04-11 10:34:30] VERBOSE[7687][C-0000000d] pbx.c: Executing [1234567890@from-trunk-sip-Bulkvs:1] Set("SIP/Bulkvs-0000000c", "GROUP()=OUT_17") in new stack



Thanks,

Brian
 
but the call is getting to my Ipbx... So not sure how it's Anveo or Bulkvs isssue????
 
Brianmac said:
Call logs are different from Anveo(failed) and Callcentric\At&t(succeed) ? Remember I am dialing the same number from two different phone numbers(anveo – bad),(callcentric-good or AT&T-good).

Calling from Anveo, I get:
[2020-04-11 10:35:39] VERBOSE[7775][C-0000000e] pbx.c: Executing [1234567890@from-sip-external:1] NoOp("SIP/76.8.29.198-0000000d", "Received incoming SIP connection from unknown peer to 1234567890") in new stack


but not from Callcentric or AT&T for that matter:
[2020-04-11 10:34:30] VERBOSE[7687][C-0000000d] pbx.c: Executing [1234567890@from-trunk-sip-Bulkvs:1] Set("SIP/Bulkvs-0000000c", "GROUP()=OUT_17") in new stack



Thanks,

Brian
Click to expand...
The call that succeeded is in the context from-sip-external while the failed calls are in the from-trunk-sip-Bulkvs context. Check you trunk configurations and you inbound routes.
 
dallas said:
The call that succeeded is in the context from-sip-external while the failed calls are in the from-trunk-sip-Bulkvs context. Check you trunk configurations and you inbound routes.
Click to expand...
No, he said that calls from Anveo to BulkVS failed. So, what's in from-sip-external didn't work. Callcentric & AT&T ending up in from-trunk-sip-Bulkvs are the good calls.
 
Brianmac said:
but the call is getting to my Ipbx... So not sure how it's Anveo or Bulkvs isssue????
Click to expand...
What are your trunk parameters for BulVS? They are not preset by the distro I think, you had to enter them yourself right?
 
Halea said:
No, he said that calls from Anveo to BulkVS failed. So, what's in from-sip-external didn't work. Callcentric & AT&T ending up in from-trunk-sip-Bulkvs are the good calls.
Click to expand...
Oops! My bad, I got them the wrong way around...
 
Brianmac said:
On the trunks, the directions from Ward in here BulkVS Configuration for Incredible PBX 2020 shows 1 trunk, yet in BulkVS directions FreePBX directions is shows 4 trunks, a main and 1 for each of the 4 IP addresses. wondering if this is where I went wrong...

Happy Easter Gang!!!

Thanks for all the help!
Brian
Click to expand...
In both cases they are referring to chan_sip driver accessed trunks, so for bulkvs you need 1 for termination (outgoing) and 4 for origination (incoming) as your PBX may get a handshake from any one of their 4 servers (depending on your geographic location). Additionally you need to allow access to your RTP range for the UDP protocol. Alternatively or additionally you can create a registration based trunk and skip the termination+origination type split trunking. Just to make sure that you are using the proper credentials from the bulkvs dashboard for your DID(s).
Happy Easter
 
Update...
Fired up a new Ipbx2020 and made changes to BulkVS to use the new serve(vultr) IP. The same issue. Inbound from anveo provider calling in causes the error, AT&T, callcentric, no issues calling in...
Think next step is to change IP based authentication to registration to see if it makes a difference...
 
Brianmac said:
Update...
Fired up a new Ipbx2020 and made changes to BulkVS to use the new serve(vultr) IP. The same issue. Inbound from anveo provider calling in causes the error, AT&T, callcentric, no issues calling in...
Think next step is to change IP based authentication to registration to see if it makes a difference...
Click to expand...
Did you contact BulkVS' tech support? They truly have outstanding service - very fast to respond, very knowledgeable and they have excellent investigational tools.
 
Yes, and agree, their support has been fantastic!!!!
Here's the issue, the call gets to the iPBX, but then is rejected. It only happens when I call from a phone on anveo. when i call from AT&T cell or callcentric, it goes right through..

note 1234567890 = my incoming Did(BulkVS) that I am calling from anveo did, AT&T did, and Callcentric did;

Calling from Anveo, I get:
[2020-04-11 10:35:39] VERBOSE[7775][C-0000000e] pbx.c: Executing [1234567890@from-sip-external:1] NoOp("SIP/76.8.29.198-0000000d", "Received incoming SIP connection from unknown peer to 1234567890") in new stack


but not from Callcentric or AT&T for that matter:
[2020-04-11 10:34:30] VERBOSE[7687][C-0000000d] pbx.c: Executing [1234567890@from-trunk-sip-Bulkvs:1] Set("SIP/Bulkvs-0000000c", "GROUP()=OUT_17") in new stack
 
Follow up...
If I - Allow Anonymous Inbound SIP Calls then the call from anveo to iPBX works.
 
You must log in or register to reply here.

Members online

Total: 33 (members: 1, guests: 32)

Latest Posts

Forum statistics

Threads
26,686
Messages
174,406
Members
20,257
Latest member
Dempan
Get 3CX - Absolutely Free!

Link up your team and customers Phone System Live Chat Video Conferencing

Hosted or Self-managed. Up to 10 users free forever. No credit card. Try risk free.

3CX
A 3CX Account with that email already exists. You will be redirected to the Customer Portal to sign in or reset your password if you've forgotten it.
Verify your Email

Check your inbox!

We’ve sent you an email. Click on the button in the email body to verify your email address – (if you can not find it, check your spam folder).

Upon verification you will be directed to the 3CX setup wizard.

Back
Top