FOOD FOR THOUGHT BulkVS.com -- Great Origination/Termination/TF rates!

[jerrm]

"Native" Windows Powershell version of http://nerdvittles.com/?p=32094 script:

param([string]$to,  [string]$msg)

$from="18005551212"
$apikey="ffffaaabbbcccdddeee"
$apisecret="eeedddcccbbbaaafff"

if (!$to  -Or !$msg)  { Write-Host "Syntax: send-sms-bulkvs 18005551212 'Your SMS message'"; exit }

$uri="https://portal.bulkvs.com/sendSMS"

Invoke-RestMethod -Uri $uri -ContentType "application/json" -Method Post -Body "{""apikey"":""$apikey"",""apisecret"":""$apisecret"",""from"":""$from"",""to"":""$to"",""message"":""$msg""}"

Save as sms-bulkvs.ps1

 

[phinphan]

thanks Jerm. I will give it a try.

 

[jerrm]

thanks Jerm. I will give it a try.

Almost forgot - Powershell will require enabling powershell scripts.

It's easy and useful to enable powershell scripts, but alternatives below use WSH wscript (or cscript):

As vbscript (save as sms-bulkvs.vbs):

if WScript.Arguments.Count < 2 then
  WScript.Echo "Syntax: send-sms-bulkvs 18005551212 ""Your SMS message"""
  WScript.Quit
end if

from="18005551212"
apikey="ffffaaabbbcccdddeee"
apisecret="eeedddcccbbbaaafff"
uri="https://portal.bulkvs.com/sendSMS"
recipient=WScript.Arguments.Item(0)
msg=WScript.Arguments.Item(1)

body="{""apikey"":""" & apikey & """,""apisecret"":""" & apisecret & """,""from"":""" & from & """,""to"":""" & recipient & """,""message"":""" & msg & """}"

set http=createObject("MSXML2.ServerXMLHTTP")
http.open "POST", uri, false
http.setRequestHeader "Content-Type","application/json"
http.send body

WScript.Echo "REQUEST: " & body & vbCrLf & "RESPONSE : " & http.responseText

As jscript (save as sms-bulkvs.js):

if (WScript.Arguments.Count() < 2) {
  WScript.Echo('Syntax: send-sms-bulkvs 18005551212 "Your SMS message"')
  WScript.Quit()
}

var from="18005551212"
var apikey="ffffaaabbbcccdddeee"
var apisecret="eeedddcccbbbaaafff"
var uri="https://portal.bulkvs.com/sendSMS"
var to=WScript.Arguments.Item(0)
var msg=WScript.Arguments.Item(1)

var body='{"apikey":"' + apikey + '", "apisecret":"' + apisecret + '", "from":"' + from + '", "to":"' + to + '", "message":"' + msg +'"}'

var http = new ActiveXObject("MSXML2.ServerXMLHTTP")
http.open("POST", uri, false)
http.setRequestHeader("Content-Type","application/json")
http.send(body)

WScript.Echo('REQUEST: ' + body + '\nRESPONSE:' + http.responseText)

 

[Prits]

Hello Guys,

I need your help with BulkVS please. Having seen the nerdvittle article on BulkVS, I thought I would give them a try.

I am a user of incredible PBX running asterisk 13-13 on my raspi.

I have been using voip.ms for years without any issues and am still using their sip trunk.

I want to use BulkVS so I successfully have registered my SIP trunk to them.

I can place outbound calls and receive calls (I purchased a DID to try things out).

However, here is my problem, outbound calls via BulkVS will not show my CID info to the receiving caller.

I placed calls from my PBX to my cellphone, to my landline, to my friends and all the get is 'UNKNOWN' on their phones too.

If I use my VOIP.MS trunk to place the outbound call, the CID info I have set on any of my pbx extensions show up on the recipients phone.

So I called BulkVS and asked for help. All they could do is provide me with the SIP log. They had me place a call while I was on the phone with them and they captured the below snippet that was emailed to me:

____________________________________________________________________________________________________________________________

Here is the INVITE, notice the caller ID in the from field shows pritstailor instead of a telephone number.

From: <sip:pritstailor@72.195.235.132>;tag=as0d26e319

Thank you,
Bulk Solutions Team


2020-07-10 10:51:26 -0400 : 72.195.235.132:5060 -> 76.8.29.198:5060
INVITE sip:[email protected] SIP/2.0
Via: SIP/2.0/UDP 72.195.235.132:5060;branch=z9hG4bK475493a1;rport
Max-Forwards: 70
From: <sipritstailor@72.195.235.132>;tag=as0d26e319
To: <sip:[email protected]>
Contact: <sip[email protected]:5060>
Call-ID: [email protected]:5060
CSeq: 102 INVITE
User-Agent: FPBX-13.0.195.28(13.22.0)
Date: Fri, 10 Jul 2020 14:51:26 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Type: application/sdp
Content-Length: 690
________________________________________________________________________________________________________________________________

Can someone please help me fix this?

Again, if I switch/use VOIP.MS as my outbound trunk, CID info shows on the recipients phone (mobile, landline, etc), but if I switch/use BulkVS as the outbound trunk, there is no CID info at the recipients end.

Thank you all!
Prits Tailor

 

[dev_null]

However, here is my problem, outbound calls via BulkVS will not show my CID info to the receiving caller.

Does the outbound route have a telephone number in the OUTBOUND ROUTE "Route CID" field, or in the TRUNK "Outbound CallerID"? If not set it in one or the other.

BVS accepts all phone numbers (or no number, as I suspect in your case) while VMS sets the caller ID in the account/subaccount portal (and this can't be over-ridden by a PBX).

 

[Prits]

Does the outbound route have a telephone number in the OUTBOUND ROUTE "Route CID" field, or in the TRUNK "Outbound CallerID"? If not set it in one or the other.

BVS accepts all phone numbers (or no number, as I suspect in your case) while VMS sets the caller ID in the account/subaccount portal (and this can't be over-ridden by a PBX).

Hello user17600,

Thank you for replying.

Yes there is a number in the outbound route field otherwise it would not also work on any other trunk like it does if I revert back to my VOIP.ms trunk (so yes, it must and does have a number, in the correct format in the CID field. it just simply does not want to work in BulkVS outgoing trunk lol, works on any of my other outgoing trunks).

 

[dev_null]

Yes there is a number in the outbound route field otherwise it would not also work on any other trunk like it does if I revert back to my VOIP.ms trunk (so yes, it must and does have a number, in the correct format in the CID field. it just simply does not want to work in BulkVS outgoing trunk lol, works on any of my other outgoing trunks).

Not sure I understand. You say trunk - but then you mention outbound route and then reverting back to VMS.

A TRUNK (the actual connection to the provider) should be set up dedicated to BVS. An OUTGOING ROUTE allows you to pick a trunk depending on various attributes, and your outgoing route would set the order for which provider (trunk) to use.

My recommendation (and others may have differing thoughts): set up a dedicated BVS TRUNK *without* anything in the "Outbound CallerID" field. This should be distinct and separate from your VMS trunk (do not repurpose a trunk). You will probably get a warning about an empty CID - ignore it. Save and apply the changes.

Then in your primary OUTBOUND ROUTE, put the CID you want delivered in the "Route CID" field. Then in the "Trunk sequence" field, pick the VMS trunk, save and apply the changes. Then make a call to see if it works.

If the call succeeds, then change the "Trunk sequence" to the BVS TRUNK, save and apply the changes.

Then try to make a call. If it fails, then there's something wonky with the BVS trunk. The setup above is exactly how I have my outgoing route configured (well, none of my VMS subaccounts have a pre-specified CID, but I have several DIDs).

 

[Prits]

Not sure I understand. You say trunk - but then you mention outbound route and then reverting back to VMS.

A TRUNK (the actual connection to the provider) should be set up dedicated to BVS. An OUTGOING ROUTE allows you to pick a trunk depending on various attributes, and your outgoing route would set the order for which provider (trunk) to use.

My recommendation (and others may have differing thoughts): set up a dedicated BVS TRUNK *without* anything in the "Outbound CallerID" field. This should be distinct and separate from your VMS trunk (do not repurpose a trunk). You will probably get a warning about an empty CID - ignore it. Save and apply the changes.

Then in your primary OUTBOUND ROUTE, put the CID you want delivered in the "Route CID" field. Then in the "Trunk sequence" field, pick the VMS trunk, save and apply the changes. Then make a call to see if it works.

If the call succeeds, then change the "Trunk sequence" to the BVS TRUNK, save and apply the changes.

Then try to make a call. If it fails, then there's something wonky with the BVS trunk. The setup above is exactly how I have my outgoing route configured (well, none of my VMS subaccounts have a pre-specified CID, but I have several DIDs).

Sorry for the interchange of words...

I have a dedicated trunk to VOIP.ms and another dedicated to BulkVS

I have an outbound route to VOIP.ms and also another outbound route to BulkVS just like a few other outbound routes I have to other trunks/providers.

Calls go out (and come in) just fine on all outbound routes, just that there is no CID info going out on the outbound route to BulkVS

(Yes, all CIDs fields are configured correctly and thus CID info goes out just fine on all other outbound routes/trunks)

Thank you

 

[dev_null]

(Yes, all CIDs fields are configured correctly and thus CID info goes out just fine on all other outbound routes/trunks)

If the outbound route has the CID you want delivered and BVS is picking up your name instead, then I'm fresh out of ideas. Maybe something got edited in one of the config files, but others would need to weigh in.

Did you check your trunks and outbound routes for the term "pritstailor" (since BVS states ' notice the caller ID in the from field shows pritstailor instead of a telephone number')?

 

[Prits]

If the outbound route has the CID you want delivered and BVS is picking up your name instead, then I'm fresh out of ideas. Maybe something got edited in one of the config files, but others would need to weigh in.

Did you check your trunks and outbound routes for the term "pritstailor" (since BVS states ' notice the caller ID in the from field shows pritstailor instead of a telephone number')?

Yeah, I checked it all and it's not there otherwise all my other outgoing providers would also have the same issue. ha

 

[dev_null]

Yeah, I checked it all and it's not there otherwise all my other outgoing providers would also have the same issue. ha

And you checked your ATA or app? For example, on Zoiper it pretty much lets you enter anything even though it says "Caller Name" it means phone number.

 

[Prits]

And you checked your ATA or app? For example, on Zoiper it pretty much lets you enter anything even though it says "Caller Name" it means phone number.

Yup, I'm using FreePBX 13 Incrediblepbx.

 

[dev_null]

Yup, I'm using FreePBX 13 Incrediblepbx.

No, I'm asking about the endpoint: the device you're actually dialing from, through to the PBX. Typically an app (on a phone) or an Analog Telephone Adapter (ATA) or a digital phone.

What you're sending actually sounds like the login name on the endpoint, entered into the Caller ID field.

 

[Prits]

No, I'm asking about the endpoint: the device you're actually dialing from, through to the PBX. Typically an app (on a phone) or an Analog Telephone Adapter (ATA) or a digital phone.

What you're sending actually sounds like the login name on the endpoint, entered into the Caller ID field.

Dialing from desk phones, through PBX and the Caller ID fields all have numbers ha, hence thats why it works on all my other trunks other than BulkVS

 

[DoctorJ]

@Prits ,

I had the exact same problem when I recently registered with BulkVS, which I have been using since my FlowRoute debacle. For what it's worth, I have been very happy with BulkVS service. And their support is very prompt.

I followed this guide on NerdVittles. I think your problem may be under "Peer Details" in your trunk registration. The NerdVittles guide includes a line "fromuser=yourBulkVSacctname" --> and, of course, I added that information. Once doing that, no matter what CID you set, the trunk sends the alphanumeric text of your account name / username as the CID. You can see this behavior in your SIP log above. Not knowing how to parse this, the BulkVS trunk just puts "UNKNOWN" as the calledID.

Try removing the "fromuser" entry from your Peer Details, and reset the trunk as in your original configuration.

 

[Halea]

The peer entry "fromuser" is definitely not needed according to BulkVS' FreePBX setup guide, that I attached to this post.
I setup my interconnect to BulkVS sometime last year with help from their write-up and got things going quickly and flawlessly.

 

[Prits]

@Prits ,

I had the exact same problem when I recently registered with BulkVS, which I have been using since my FlowRoute debacle. For what it's worth, I have been very happy with BulkVS service. And their support is very prompt.

I followed this guide on NerdVittles. I think your problem may be under "Peer Details" in your trunk registration. The NerdVittles guide includes a line "fromuser=yourBulkVSacctname" --> and, of course, I added that information. Once doing that, no matter what CID you set, the trunk sends the alphanumeric text of your account name / username as the CID. You can see this behavior in your SIP log above. Not knowing how to parse this, the BulkVS trunk just puts "UNKNOWN" as the calledID.

Try removing the "fromuser" entry from your Peer Details, and reset the trunk as in your original configuration.

Hello DoctorJ,

Thank you this information!

yeah I too had followed Wards article to the T, but following your suggestion, it seems to have fixed my issue!!!

i appreciate your knowledge and help. When I asked BulkVS, the said that they did not know and that I had to troubleshoot on my own. I was surprised at this because I had read on this forum that their support is very good. Oh well, hopefully that was just an isolated experience!

 

[Prits]

The peer entry "fromuser" is definitely not needed according to BulkVS' FreePBX setup guide, that I attached to this post.
I setup my interconnect to BulkVS sometime last year with help from their write-up and got things going quickly and flawlessly.

hello Halea,

thank you for this information! I appreciate your knowledge and advice! I tried looking for any documentation on setting up the trunk, but only had Wards article to go off. Thank you for the PDF attachment!

 

[Eliad]

I have a PJSIP trunk with BulkVS.
For some reason DTMF is not sensed when I dial to a FreePBX but seems to work on other services where I use DTMF. Any idea what could be wrong?

 

[atsak]

I'm concerned about companies like this cause I don't know them. My worst fear is that I port numbers to them, they go belly up and then I lose my dids. What would happen in that scenario?

The originating carrier would have your DID's, or you could do an emergency port. BulkVS has been around a while . . .