TIPS IPBX-2020 and Bulkvs

[wardmundy]

@Brianmac: Take a look at the Anveo article in Nerd Vittles. I think that may be the answer to your problem without having to allow anonymous inbound calls:

Just a word of explanation about why we’re using a custom trunk context for Anveo rather than using the standard from-trunk entry. Because of its environment, Anveo doesn’t pass the DID of the trunk in the traditional way.1 Instead, it passes the DID in a customized SIP header as shown above.

 

[Brianmac]

Ward, thanks, but my issue is, I am not using Anveo in a trunk. Anveo service(Home phone) is calling my BulkVS Did. BulkVS send to my iPBX, then iPBX doesn't know what to do with it, because of the "unique" way anveo handles the call... Can't believe I am the only lucky bastard that has come across this??

e.g. Did from anveo 123-456-7890(Home phone) calls BulkVS did 098-765-4321, BulkVS send to my iPBX, iPBX says, what the hell is this?? This is anonymous and I am rejecting it...

Brian
PS - might just leave anonymous call on...

 

[wardmundy]

That's why you need to set up an Anveo trunk... so you don't have to leave anonymous calling activated. Better yet, stop using Anveo. V1VoiIP offers same pricing without the SIP quirks.

 

[Brianmac]

Anveo is not part of the equation. I am helping a doctor friend of mine switchover to VOIP. I just stumbled on this as Anveo is being used as my home phone service during testing. I don't want calls to fail to the doctors office because a patient was using Anveo to call into his office....
See my other thread: Temp doctors office

Thanks,
Brian

 

[wardmundy]

Then set up an unregistered Anveo trunk and follow the tutorial for setting up the context. No registration is required, and the from-anveo context will convert the incoming calls to a normal DID entry which can be handled by your default inbound route. You certainly do not want a doctor's office set up with anonymous SIP calling in place.

This may also be a problem with a particular carrier. See this thread.

And, I repeat, Anveo is a very poor VoIP choice for someone that doesn't know what they're doing.

 

[dallas]

Then set up an unregistered Anveo trunk and follow the tutorial for setting up the context. No registration is required, and the from-anveo context will convert the incoming calls to a normal DID entry which can be handled by your default inbound route. You certainly do not want a doctor's office set up with anonymous SIP calling in place.

This may also be a problem with a particular carrier. See this thread.

And, I repeat, Anveo is a very poor VoIP choice for someone that doesn't know what they're doing.

Ward, from my reading of this thread... he doesn't have any Anveo services on his 2020. I previously suggested he trace good and bad incoming calls to see what's going wrong.
I suspect you may be correct about SIP signalling.

dallas

 

[jerrm]

Anveo setup is irrelevant. His outbound Anveo works. Pretend he said calls from Verizon fail and AT&T succeeds.

The successful AT&T calls come to the PBX from the BulkVS server the FreePBX gui-configured trunk is pointing at (sip.bulkvs.com/69.12.88.198).

The failing "pretend-Verizon" calls take a different route to BulkVS and are being sent to the PBX from the BulkVS server at 76.8.29.198(see post 8).

The sip_custom_post.conf host entries don't seem to be enough for some reason.

@Brianmac: Try configuring FreePBX GUI trunks for each host address and clear sip_custom_post.conf.

 

[Brianmac]

Yes, Anveo is NOT part of iPBX2020. I only used anveo as I have it for home service and I just called into the iPBX2020 to test my inbound routes(BulkVS).....
No outbound Anveo either, again Anveo is NOT part of this, I was only using anveo Did to call into the iPBX of the bulkVS Did. I also used a cell and callcentric..
iPBX2020 uses only BulkVS(trunk) for inbound\outbound, but calling into it from an Anveo Did causes a problem in iPBX....

And, I repeat, Anveo is a very poor VoIP choice for someone that doesn't know what they're doing.

agreed, We barely use home phone, but at $7/month or $84 year, was cheap enough to keep around and with obihai200, easy to get voicemail2email and not have to run an iPBX in the cloud...

 

[atsak]

76.8.29.198 this trunk configuration has something weird about it on your IPBX. The IP address when it hits your PBX isn't being seen as the trunk for some reason, even though you said it's configured; that's why anonymous works (and what the log says). That IP is the one that Anveo peers with whereas the other ones must use one of the other IP's by default in BulkVS's routing table. Have a careful look for an errant space or something like that, maybe try also deleting the trunk and carefully recreating it manually. The netsock errors I'm not sure if that's normal but it's like name resolution is looking up what that IP is as well, which seems weird. Is dns lookup working OK on your server (ie can you ping by name www.google.com)?

 

[Brianmac]

atsak, agree with everything you are saying about that trunk. Also why the calls from AT&T\callcentric are going through. There is something with the trunk. Now, not only did I delete and recreate the trunk(a couple of times and did not copy\paste), I also created a newiPBX on another instance and recereated everything. Same situation...

Thanks,
Brian

 

[jerrm]

atsak, agree with everything you are saying about that trunk. Also why the calls from AT&T\callcentric are going through. There is something with the trunk. Now, not only did I delete and recreate the trunk(a couple of times and did not copy\paste), I also created a newiPBX on another instance and recereated everything. Same situation...

Thanks,
Brian

Have you tried setting up a gui configured trunk for each bulkvs IP?

Post screen shots of the trunk(s) config and cut/paste the contents of sip_custom_post here.

 

[wardmundy]

Anveo setup is irrelevant. His outbound Anveo works. Pretend he said calls from Verizon fail and AT&T succeeds.

Then I would suspect a carrier problem as I documented above... with a solution.

 

[jerrm]

Then I would suspect a carrier problem as I documented above... with a solution.

The call is being presented to asterisk from a known BulkVS IP but asterisk is dropping it if anonymous is not enabled. Almost certainly config issue.

 

[atsak]

Then I would suspect a carrier problem as I documented above... with a solution.

There must be something obscure here. Why would asterisk mis-route this call if it's coming from that IP? I tried to duplicate this but interestingly I never receive calls from that bulkvs originating IP on any of my servers . . .

I have one other thought. On one of my servers I saw a problem once where for some reason one of the trunks would not save to the sip_additional.conf file when configured in the GUI. Somehow, the file permissions got mangled on the file and the sip_additional.conf file that held the trunks wouldn't write. So it looked fine in the GUI, but when you looked at the .conf file it was missing that trunk.

I fixed it quite inelegantly by renaming the file, then making a change in the GUI which wrote a new copy of the file out.

So, um, manually check sip_additional.conf and see if the trunk is configured in actual fact in there and there's no weird spaces or anything that doesn't belong.

 

[wardmundy]

On occasion, in testing various providers, we have run into situations where calls from a particular carrier fail to arrive. The usual solution was to route the calls through another carrier on the outbound leg. This is easy to do with Anveo by specifying the carrier for your outbound calls. By trying several, it will be simple to determine if this is an outbound carrier problem and, if so, which one.