Asterisk setup with OBi110
MichiganTelephone:
justin, are you 1000% SURE that you are using the EXACT SAME 10 digit number under Physical Interface, Line Port, InboundCallRoute on the Obi, AND in the [custom-from-obi] context, AND in your Inbound Route as the DID? If you are then I'm sorry but it's not making sense to me — if your trunk is working for other calls then it should handle the inbound PSTN calls as well.
If you don't have Caller ID on your PSTN line you could set the RingDelay to 0 to get calls into your Asterisk system faster, but that wouldn't impact the routing of incoming calls. However that brings up another possibility — check your FreePBX Blacklist to make sure you're not blocking calls with no Caller ID (make sure that the checkbox for "Block Unknown/Blocked Caller ID" is NOT checked).
Other than that, I'm afraid you have me stumped. ???
MichiganTelephone:
I'm going to give you some specific examples just so we are clear on what you need to do. Let's say your PSTN phone number is 234-555-2345.
On the OBi, under Physical Interface, Line Port, the InboundCallRoute must be:
SP2(2345552345)
In your [custom-from-obi] context in /etc/asterisk/extensions_custom.conf you need a line like this:
exten => 2345552345,1,Goto(from-trunk,${EXTEN},1)
Note the above is an exact match, not a pattern, so there is no underscore in front of the first digit (just wanted to mention that in case maybe you thought there should be).
And then you have to create an Inbound route, and in the DID Number field you need to put 2345552345. Do not fill in the Caller ID Number.
If those three things are correct, and it still doesn't work, and yet you can receive other calls (such as Google Voice call) over the trunk, then I simply have no idea what the problem is. Are you sure you have a good physical connection to your PSTN Line?
justin:
POTS > ASterisk is now working
GV > Asterisk is working too.
The problem is I had GV number listed in the incoming settings for user context in the asterisk trunk.
Now to work on the outgoing calls to GV and POTS
MichiganTelephone:
Quote from: justin on February 25, 2011, 10:47:56 am
POTS > ASterisk is now working
GV > Asterisk is working too.
The problem is I had GV number listed in the incoming settings for user context in the asterisk trunk.
That should not be a problem if you had also used that same number in the SP2 Service SIP Credentials. The USER Context field is like your Login name - you could probably just as easily use something like obi-inbound if you also used that in your SP2 Service SIP Credentials, as both the AuthUserName and the first part of the URI (I have not actually tried that, so don't hold me to that).
What I can't understand is, if changing the USER Context field made it work, how was it working before? Because that would indicate you weren't registering (which might explain that 404 you were seeing). So I don't understand how the GV calls were getting through. But then there are a lot of things about Asterisk that mystify me.
But hey, let's not look a gift horse in the mouth — I'm glad you got it working, no matter how you did it!
Quote from: justin on February 25, 2011, 10:47:56 am
Now to work on the outgoing calls to GV and POTS
Good luck, I sincerely hope that is easier for you! ;D
justin:
Well It says the OBi110 is busy.
Got SIP response 486 "Busy Here" back from 192.168.1.140:5061
-- SIP/OBi110-000001e3 is busy
Any Reason why it would say that?
Navigation
[0] Message Index
[#] Next page
[*] Previous page