On Tue, Nov 15, 2011 at 11:15 PM, Roy Walker roy.walker...@gmail.comwrote:
Content-Type: text/plain;
charset=utf-8
Content-Transfer-Encoding: 8bit
Organization: SipXecs Forum
In-Reply-To: 4eb7bf66.1050...@ezuce.com
X-FUDforum: 08063afcdd00a6e76393c5b9527381e8 64545
Message-ID:
Domains and DNS matter...
You can use aliases to receive calls fine but as a general practice I've
always done user auth through the SIP domain. Planning out an installation
and thinking about DNS name space inside and outside your network in my
experience will always provide a better result.
Content-Type: text/plain;
charset=utf-8
Content-Transfer-Encoding: 8bit
Organization: SipXecs Forum
In-Reply-To: 4eb7bf66.1050...@ezuce.com
X-FUDforum: 08063afcdd00a6e76393c5b9527381e8 64545
Message-ID: fc21.4ec33...@forum.sipfoundry.org
Wow, I ran into this over a year ago and could not
Anyone?
On request I added a snapshot to the tracker
From: sipx-users-boun...@list.sipfoundry.org
[mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of Henry
Dogger
Sent: vrijdag 4 november 2011 11:19
To: Discussion list for users of sipXecs software
Subject: [sipx-users] CallerID not
Henry,
I looked at the code and the query indeed is checking the entire
identity (user@domain) as the parameter. Unfortunately, there is no
simple way to do this in fastdb besides fetching all users and and
compare user + port against all possible aliases. This can be done in
mongo though
