VoXaLot not working with PBXes (VoXaLot as an extension of PBXes)

[wilsonhlacerda]

any news???

[wilsonhlacerda]

Is this queued for investigation/support (any time expectation?) or should I give up?

[Tony]

Originally Posted by wilsonhlacerda

Is this queued for investigation/support (any time expectation?) or should I give up?

Hi Wilson,

The technical team has spent a fair bit of time trying to address this issue, as well as your original issue of not being able to register your provider - which has led you to try pbexs as an alternate route. Unfortunately we cannot continue to investigate every possible configuration. We do our best to try and assist every one and all possible combinations and configurations, but we cannot guarantee that they will all work despite our efforts and the rest of the community's efforts.

As martin stated in the last post of we provide a 100% SIP compliant service
http://forum.voxalot.com/voxalot-sup....html#post7475
which there was no response too from you. So I suggest you give up or find what your provider is doing that is not compliant with voxalot.

Perhaps when we are less busy we can come back and take a look at your particular issue.

Tony.

[ronison]

Hi Wilson. I'm from Brazil too. I have a two way route between Voxalot <-> PBXes working fine!

[wycodreams]

Ronison, please post your voxalot configuration in PBXES and your pbxes configuration in voxalot, please, you can help us to solve this problem. Thank you

[wilsonhlacerda]

ronison I'd thank you a lot if you post your configurations just like wycodreams asked. I've already tried it all ways and till now no sucess.

Tony thank you for your reply.
I know Voxalot "provide a 100% SIP compliant service", but the fact is that this Brazilian provider is also SIP and works 100% fine with Counterpath X-PRO, Counterpath eyeBeam, Grandstream HT-496 and PBXES but not with Voxalot. I myself tested with all of them.

So should we conclude that the provider, the X-PRO, the eyeBeam, the HT-496 and the PBXES are not 100% SIP compliant but they are somehow compliant among them? Is Voxalot the only "good guy"?

This suggests me that this "particular issue" maybe rising a broader problem.
Anyway, I really thank you for your effort to solve it till now.

Just like Martin I'm also waiting a reply for that post from the provider. Unfortunately only them and you can work on the problem. As I wrote in that topic I've asked for support to the Brazilian provider, but I got no reply from them to my 3 emails nor the topic (I sent its link to them). Seems they do not want to cooperate with us.

About Voxalot as an PBXES extension, let's wait ronison post his configuration that seems to work fine. I'm anxious for it. I really hope it is just a mistake of mine.

[ronison]

PBXes account settings at Voxalot Provider Setup:

Description: PBXes
Username: <login da extensão no PBXes>
Codecs: g729;ilbc;gsm;ulaw;alaw
SIP Proxy: pbxes.org
SIP Port: 5061
Active: Yes
SIP Register: Yes

Voxalot account setting at PBXes Trunk Setup:

Trunk Name: Voxalot
DTFM mode: auto
Audio bypass: No
Username: <voxalot account username>
Password: <voxalot account password>
SIP server: us.voxalot.com
Register: Yes (inbound and outbound calls)

[wilsonhlacerda]

Ronison, thanks for the post.

1. But when you put a call from PBXes to Voxalot how is the traffic for you? I mean:

A. you use PBXes trunk:
any PBXes extension ==> PBXes trunk linked to Voxalot ==> Voxalot

B. or you use PBXes extension:
any PBXes extension/trunk ==> PBXes extension linked to Voxalot ==> Voxalot


2. For this:

PBXes account settings at Voxalot Provider Setup:
Description: PBXes
Username: <login da extensão no PBXes>
Codecs: g729;ilbc;gsm;ulaw;alaw
SIP Proxy: pbxes.org
SIP Port: 5061
Active: Yes
SIP Register: Yes

What's the configuration on the PBXes side? I mean, how is this PBXes extension linked to Voxalot configured in PBXes?

3. How is set your "Enable symmetric NAT handling" in Voxalot?

Please check that an answer this 3 questions so that we can have your total configuration.

[wilsonhlacerda]

New working solution for PBXes ==> VoXaLot !!!

As I only need one way call (provider ==> PBXes ==> VoXaLot) I've just tried a new solution and this one works fine!

In a nutshell the difference of it to my first one is that I do not have VoXaLot registered to a PBXes extension and the PBXes' VoXaLot extension is now directly pointing to my VoXaLot SIP/URI.

Detailed configuration:

In VoXaLot:
do nothing.

In PBXes:
Create a SIP extension. Say number 1000, name VoXaLot.
Submit.
Click on it again (to edit the advanced options).
On dial put SIP/<your voxalot number>@voxalot.com
Submit.
Click on the red bar.

Now if some PBXes extension/trunk rings extension 1000 your VoXaLot will ring!

After having this working you can try to change the "audio bypass" option to "yes" in your VoXaLot extension, other extensions and trunks. If they continue to work fine it's better this way. For me it was not possible and so all are "no".

Now you, just like me, can have VoIP providers that VoXaLot can not register to, ringing VoXaLot! (Just register a PBXes trunk to the provider and redirect all inbound calls from this trunk to the VoXaLot extension.)

[ygeffens]

Originally Posted by wilsonhlacerda

New working solution for PBXes ==> VoXaLot !!!

As I only need one way call (provider ==> PBXes ==> VoXaLot) I've just tried a new solution and this one works fine!

I read through the whole thread, and maybe I missed it, but is there a sullotion for the opposite direction?

I created a provider:
PBXes myaccount-300 pbxes.org Yes - [Edit] [Delete]
I created a dialplan:
Priority Pattern Replacement Provider Active
1 _ZXXXXX ${EXTEN} VoXaLot Yes [Edit] [Delete]
2 _[124-9]XX ${EXTEN} VoXaLot Yes [Edit] [Delete]
7 _3XX ${EXTEN} PBXes 300 Yes [Edit] [Delete]

The extensions I want to reach in PBXes all start with "3", therefor I excluded "3" in rule number 2, and specifically tried to make a match in rule 7 for numbers starting with "3".

I created extention 300 in pbxes.
Now voxalot logs in to extention 300 in pbxes (I assume).
I call "311" (an existing extention in pbxes) but I don't get any connection.

What did I do wrong?