Here is what I suggest you do. Instead of quoting RFC's (which IMHO)
this community has enough understanding of, that you create a patch to
make this satisfy your need. Submit it for approval via a jira and
lobby for it to be accepted in trunk via the dev list. Retranmission of
request is de
Content-Type: text/plain;
charset="utf-8"
Content-Transfer-Encoding: 8bit
Organization: SipXecs Forum
In-Reply-To: <4ebdc89e.4030...@ezuce.com>
X-FUDforum: 08063afcdd00a6e76393c5b9527381e8 <64493>
Message-ID:
Joergen, again thank you for suggesting the Karoo solution.
I understand the issue
Content-Type: text/plain;
charset="utf-8"
Content-Transfer-Encoding: 8bit
Organization: SipXecs Forum
In-Reply-To:
X-FUDforum: 08063afcdd00a6e76393c5b9527381e8 <64492>
Message-ID:
Try the dev mailing list...
http://wiki.sipfoundry.org/display/sipXecs/Where+to+find+help
__
Content-Type: text/plain;
charset="utf-8"
Content-Transfer-Encoding: 8bit
Organization: SipXecs Forum
In-Reply-To:
X-FUDforum: 08063afcdd00a6e76393c5b9527381e8 <64491>
Message-ID:
Try the mailing list...
http://wiki.sipfoundry.org/display/sipXecs/Where+to+find+help
The mailing lists are
Content-Type: text/plain;
charset="utf-8"
Content-Transfer-Encoding: 8bit
Organization: SipXecs Forum
In-Reply-To:
X-FUDforum: 08063afcdd00a6e76393c5b9527381e8 <64490>
Message-ID:
There's not a lot of useful information here...
What version of sipXecs, what type of phones, what firmware
ar
Content-Type: text/plain;
charset="utf-8"
Content-Transfer-Encoding: 8bit
Organization: SipXecs Forum
In-Reply-To:
X-FUDforum: 08063afcdd00a6e76393c5b9527381e8 <64489>
Message-ID:
First, get your acodes up to 6.0 if you can...
Second, after you install sipXecs always run 'yum update'
from
Content-Type: text/plain;
charset="utf-8"
Content-Transfer-Encoding: 8bit
Organization: SipXecs Forum
In-Reply-To:
X-FUDforum: 08063afcdd00a6e76393c5b9527381e8 <64488>
Message-ID:
First, try the mailing list... much more active.
Second, sip trunks are configured as gateway devices...
Thi
Content-Type: text/plain;
charset="utf-8"
Content-Transfer-Encoding: 8bit
Organization: SipXecs Forum
In-Reply-To:
X-FUDforum: 08063afcdd00a6e76393c5b9527381e8 <64487>
Message-ID:
try the mailing list but i don't think you'll find many
takers here...
Content-Type: text/plain;
charset="utf-8"
Content-Transfer-Encoding: 8bit
Organization: SipXecs Forum
In-Reply-To:
X-FUDforum: 08063afcdd00a6e76393c5b9527381e8 <64486>
Message-ID:
fyi, most users who know what's going on with this project
use the mailing lists... mailing list is only poste
Content-Type: text/plain;
charset="utf-8"
Content-Transfer-Encoding: 8bit
Organization: SipXecs Forum
In-Reply-To:
X-FUDforum: 08063afcdd00a6e76393c5b9527381e8 <64485>
Message-ID:
DNS, dns, dns...
unless of course they are calling each other from outside /
behind NAT...
___
Content-Type: text/plain;
charset="utf-8"
Content-Transfer-Encoding: 8bit
Organization: SipXecs Forum
In-Reply-To:
X-FUDforum: 08063afcdd00a6e76393c5b9527381e8 <64484>
Message-ID:
This is because your client didn't have a proper DNS server
that knew about your SIP domain... sipXecs depends
11 matches
Mail list logo