2talk and Freepbx

Forums › VoIP › 2talk and Freepbx

mikeeatr

2 posts

Wannabe Geek

#177202 26-Jul-2015 11:38

Hi, I try and set up the 2talk with freepbx, but I can make outbound calls fine. But inbound call and it goes to 2talk voice mail. According to 2talk the number is registered and online.

The PBX is behind a nat (pfsense)

Any help would be appreciated.

Thanks

sbiddle

30853 posts

Uber Geek
+1 received by user: 9996

Retired Mod

Trusted

Biddle Corp

Lifetime subscriber

#1351885 26-Jul-2015 11:39

I assume you haven't yet Googled the known issues and resolutions for VoIP issues with pfsense?

mikeeatr

2 posts

Wannabe Geek

#1351886 26-Jul-2015 11:40

sbiddle: I assume you haven't yet Googled the known issues and resolutions for VoIP issues with pfsense?

sbiddle

30853 posts

Uber Geek
+1 received by user: 9996

Retired Mod

Trusted

Biddle Corp

Lifetime subscriber

#1352041 26-Jul-2015 16:43

mikeeatr:
sbiddle: I assume you haven't yet Googled the known issues and resolutions for VoIP issues with pfsense?

No

That will be the best place to start. pfsense and VoIP don't necessarily play nicely together. It's one of the reasons I'd never go near it as a s solution.

chevrolux

4962 posts

Uber Geek
+1 received by user: 2638
Inactive user

#1352101 26-Jul-2015 19:14

sbiddle:
mikeeatr:
sbiddle: I assume you haven't yet Googled the known issues and resolutions for VoIP issues with pfsense?

No

That will be the best place to start. pfsense and VoIP don't necessarily play nicely together. It's one of the reasons I'd never go near it as a s solution.

Agreed. It's a pain in the butt.

You need to add some nat rules so that pfsense doesn't muck around with the ports as they get nat'd out. I think they have a sip alg type package you can add now too but that is probably going to be just as useful as every other alg out there.

Perhaps TLS might solve the issue but then there is heaps more to do on your FreePBX box instead and is probably actually harder than getitng pfsense to do what you want.

Glazza

279 posts

Ultimate Geek
+1 received by user: 11

Trusted

#1378253 2-Sep-2015 13:52

Hey

If you got this resolved - would you mind seeing if you have the same issue as I do?

I have an issue where a remote party calling in to a FreePBX installation is able to make use of the Call Features (such as *1, *2, etc).

In my testing I have called in from my mobile to a FreePBX extension, and upon the call being answered I am able to dial *2 from my mobile, and I am able to transfer my own call to another extension.

If I call from my FreePBX extension to my mobile, I am not able to use the call feature codes - in fact I can not even hear the DTMF tones pressed on the mobile on the extension...

I'm trying to work out if this is something I have done, or a setting I have over looked, or expected behaviour.

Thanks

sbiddle

30853 posts

Uber Geek
+1 received by user: 9996

Retired Mod

Trusted

Biddle Corp

Lifetime subscriber

#1378258 2-Sep-2015 14:01

Glazza: Hey

If you got this resolved - would you mind seeing if you have the same issue as I do?
I have an issue where a remote party calling in to a FreePBX installation is able to make use of the Call Features (such as *1, *2, etc). In my testing I have called in from my mobile to a FreePBX extension, and upon the call being answered I am able to dial *2 from my mobile, and I am able to transfer my own call to another extension. If I call from my FreePBX extension to my mobile, I am not able to use the call feature codes - in fact I can not even hear the DTMF tones pressed on the mobile on the extension...

I'm trying to work out if this is something I have done, or a setting I have over looked, or expected behaviour.

Thanks

This is controlled by the Dial Command settings which should be at the default 'tr'

DO NOT under any circumstances play with this unless you fully understand what you're doing (and I'd suggest now you don't understand these settings) as it opens up some massive security holes.

You should not be able to call in and dial * feature codes and you should not allow this unless you're fully aware of the risks.

If you're not hearing DTMF tones when calling out it suggests you have your DTMF settings set incorrectly.

New World

Shop on-line at New World now for your groceries (affiliate link).

Glazza

279 posts

Ultimate Geek
+1 received by user: 11

Trusted

#1378290 2-Sep-2015 14:31

Hi Steve

FreePBX out of the box sets Asterisk Outbound Trunk Dial Options to Ttr (advanced settings)

And for each Trunk it defaults to Tt..

if I override this - removing the T - I believe this should stop the calling user (mobile in my example) being able to dial any 'Feature Code' - however it doesn't!

Cheers

sbiddle

30853 posts

Uber Geek
+1 received by user: 9996

Retired Mod

Trusted

Biddle Corp

Lifetime subscriber

#1378294 2-Sep-2015 14:36

Oops yes tr is what I use as default for lots of things on Asterisk, Ttr is the current settings in FreePBX

It's not an issue I've seen before.

Glazza

279 posts

Ultimate Geek
+1 received by user: 11

Trusted

#1378299 2-Sep-2015 14:45

Thanks - I have just run through a fresh build from the ISO - added a single extension, added a 2Talk trunk... and issue is replicated...

I've tried to override the T - which by all accounts should resolve the issue.

Thanks