>
>
> Thanks for the response, but no:
>
> # grep -R host * | grep callcentric
> exts/callcentric.sip.conf:host=callcentric.com
> # grep -R host * | grep 204
> #
>
> Why in the world is asterisk trying to match on the FROM header??
>
Because that's what Asterisk has always done to match an inbou
Oops, had it wrong. Here's how it works for me:
[callcentric-template](!)
type=friend
context=from-callcentric
fromdomain=callcentric.com
defaultuser=1777xxx
fromuser=1777xxx
secret=password
insecure=port,invite
dtmfmode=rfc2833
disallowed_methods=UPDATE
session-timers=refuse
videosupport=
>
> So do I need 7 contexts, one for each ip address?
>
> sean
>
Yes, if what you call a "context" is your peer definition in sip.conf. CC
routes calls through a varying number of SBCs, all (also) resolving to
callcentric.com, but each having their own name, typically "
alphaxy.callcenctric.com".
On 04/15/2014 05:24 PM, Sean Darcy wrote:
On 04/14/2014 11:47 AM, Kelvin Chua wrote:
wild guess would be a conflict on host= setting.
there might be another entity on your sip.conf which have type=friend
and host=callcentric.com or host=204.11.192.161
Kelvin Chua
On Mon, Apr 14, 2014 at 8:01 A
On 04/14/2014 11:47 AM, Kelvin Chua wrote:
wild guess would be a conflict on host= setting.
there might be another entity on your sip.conf which have type=friend
and host=callcentric.com or host=204.11.192.161
Kelvin Chua
On Mon, Apr 14, 2014 at 8:01 AM, Sean Darcy wrote:
On 11.9, trying to s
Josh Metzger wrote:
A little while back, I upgraded some systems from Asterisk 1.4 (I
believe it was 1.4.29.1, and they were already running DAHDI), to 11.
11 made the most sense as far as it being a LTS release so it would be
longer before being forced into a new version (as far as continued bu
A little while back, I upgraded some systems from Asterisk 1.4 (I believe
it was 1.4.29.1, and they were already running DAHDI), to 11. 11 made the
most sense as far as it being a LTS release so it would be longer before
being forced into a new version (as far as continued bug fixes and things),
a
On Mon, Apr 14, 2014 at 12:26 PM, Josh Metzger wrote:
> I've had years of experience using ODBC for CDR, SIP, and extensions with
> Asterisk. One thing that has been problematic in the past is with
> documentation as far as database tables changing between versions (even
> within minor releases,
Am 14.04.2014 16:19, schrieb Eric Wieling:
So few people use Asteisk on OSX that I doubt anyone will answer.
Look how many answers he got, i got none
--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
2014-04-15 10:37, Lee, John (Sydney) skrev:
Hello,
I have been running Asterisk for the past 5+ years on RedHat and I never
upgraded it before.
All my Asterisk software is of the following release:
1) Asterisk 1.4.21.2
2) Libpri-1.4.4
3) Zaptel-1.4.11
I would like to move the OS to CentOS and th
Hello,
I have been running Asterisk for the past 5+ years on RedHat and I never
upgraded it before.
All my Asterisk software is of the following release:
1) Asterisk 1.4.21.2
2) Libpri-1.4.4
3) Zaptel-1.4.11
I would like to move the OS to CentOS and then I thought I can at the same time
ponder ab
11 matches
Mail list logo
