Well, there is documentation.
/Fredrik
Original message
From: Johan Vikman
Date:
To: Fredrik Thulin
Cc: yxa-devel@lists.su.se
Subject: Re: [Yxa-devel] Changing transport to TLS/TCP
Hi again,
How can I proxy the request to the PSAP? What do I need to return in the
On Mon, 2013-09-02 at 13:47 +0200, Johan Vikman wrote:
...
> >
> > So, really, I don't think the requirement is for the 300 response in
> > step 3 to be sent using TLS/TCP (SIP does not support upgrading from
> > TCP/UDP for the response, IIRC). I think the requirement is that the
> > E-CSCF uses
On Mon, 2013-09-02 at 12:26 +0200, Johan Vikman wrote:
> Hi Fredrik,
>
> Of course, below I describe one way this could happen, the yxa stack is used
> in the LRF node.
>
> UE E-CSCF
> LRF
On Mon, 2013-09-02 at 11:20 +0200, Johan Vikman wrote:
> Hi,
>
> I am using the yxa stack to provide Geolocations over SIP.
>
> I now have gotten a requirement that says that if the Geolocation ultimately
> will be sent to a contact using sips, I need to respond to the request using
> TLS/TCP,
Hi all, it's been a while.
After 18 months of absence from YXA (I was away in the IT security
business) I've recently started my own consulting firm.
If anyone is interested in contracting me (maintenance contract for YXA,
systems design or developing something custom you need), feel free to
cont
On Thu, 2010-09-23 at 21:33 -0400, Vance Shipley wrote:
> This commit fixes the generation of release resource files with the
> appropriate installed library version numbers.
>
>
> http://github.com/vances/yxa/commit/8da65fe64d3b98464ec0c78cad77c8956d3824ea
>
It's friday afternoon and I'm pr
On Tue, 2010-08-10 at 22:39 +0200, Mikael Magnusson wrote:
...
> Please, merge http://github.com/mikma/yxa/tree/fix/topgit_cleanup, which
> remove these extra files.
Oops. Missed that. Merged fix/topgit_cleanup.
/Fredrik
___
Yxa-devel mailing list
Yxa
On Thu, 2010-07-22 at 12:12 +0200, Mikael Magnusson wrote:
> There is a problem with enum lookup with YXA on OTP R13 and newer. Fixed
> in the branch described below.
>
> Fix enum lookup on Erlang/OTP R13 and newer.
>
> All ENUM NAPTR records decoded by R13 and later were ignored
> since it adds
On Fri, 2010-06-04 at 18:35 +0400, Alexander Zhukov wrote:
> Hi!
>
> I have YXA installed and incomingproxy running with two phones connected
> and registered.
>
> My short goal is to make a SIP calls from an Erlang code.
> I tried esipua but to no success. It doesn't work.
> The code from yxa/sr
On Wed, 2010-06-02 at 14:42 +0400, Alexander Zhukov wrote:
...
> >> Why incomingroxy sets source IP address of the outgoing packet?
> >> Usually this job is done by an IP stack. Application which sits on
> >> the "application" level should not bother with such low level
> >> details.
>
> FT>
d runtime to use this (dunno if its there yet).
>
> Love
>
>
> 1 jun 2010 kl. 10:27 skrev Dmitriy Kargapolov:
>
>> When socket is not bound explicitly to particular interface it is not
>> possible to specify what IP will be used to send datagrams. OS decides
>&g
On Tue, 2010-06-01 at 19:39 +0400, Alexander Zhukov wrote:
...
> Thank you very much for your answer!
> I added myips option and it works.
Good.
> But I still do not undestand some points.
>
> In my case incomingproxy should send an INVITE to the 10.10.16.157. The
> correct interface to send the
On Tue, 2010-06-01 at 15:52 +0400, Alexander Zhukov wrote:
...
> 192.168.67.1 is an IP of the vmnet8 (virtual network interface used by
> vmware workstation) on the host where incomingpproxy is running.
>
> When I stopped vmware virtual interfaces the call was established
> without problems.
>
>
On Sun, 2010-04-11 at 21:45 +0200, Mikael Magnusson wrote:
...
> I have renamed the macros as you proposed, and pushed it to my config
> branch. Let me know if you want me to merge it with the previous commit
> with rebase.
Ok, merged and pushed. No need to rebase, I'm not a perfectionist and as
I
On Sun, 2010-04-11 at 10:53 +0200, Fredrik Thulin wrote:
...
> The idea sounds good to me, but I'd say there is precedent (hope I'm
> using that word correctly) to adding a hook to local.erl for doing that
> kind of thing. Was there a reason to add it to the YXA application
On Sat, 2010-04-10 at 23:01 +0200, Mikael Magnusson wrote:
> Customizable application config defaults
>
> Add config_defaults/0 to the YXA application behaviour, returning the
> application config defaults as a list of #cfg_entry{}.
>
> It allows setting application defaults in an (exte
Hi
I've changed my mind regarding pull requests at Github. Like the Erlang
guys write at http://wiki.github.com/erlang/otp/submitting-patches
> What about pull requests?
>
> We prefer emails, so that the discussion about patches will get
> archived so that other people can learn from them.
So,
On Tue, 2010-04-06 at 17:16 -0400, Dmitriy Kargapolov wrote:
> Hi all,
> I found non-critical bug in the sippacket.erl, see the fix below.
> This bug resulted in parser error when quoted display name contains
> character.
> Something like this:
>
> Error in process <0.23778.188> on node '' with e
I've now completed the move of the YXA source code to GitHub, and have
today processed the first pull request.
That change added the long waited for --disable-erlang-version-check to
'configure' - thanks to Mikael Magnusson and Jakob Schlyter!
http://github.com/fredrikt/yxa
git://github.com/f
On Mon, 2010-02-08 at 17:34 +0100, Mikael Magnusson wrote:
> Hello,
>
> it looks like eventserver compares URI differently than incomingproxy.
> Because, if there is a user with AOR sip:u...@host, then a INVITE to
> sip:u...@host;param=value will be routed to the registered clients of
> the user.
On Sun, 2010-01-10 at 21:49 +0100, Mikael Magnusson wrote:
> Fix bug introduced when cleaning up transactionsatelist. Correct
> transaction id when adding client transaction state.
>
> Add add_client_transaction/5 and get_client_transaction/2 testcases.
Thanks! Applied right away since you even i
On Wed, 2009-12-16 at 19:22 +0100, Mikael Magnusson wrote:
> On Wed, 2009-12-16 at 15:51 +0100, Fredrik Thulin wrote:
> > Should I do what most people seem to have done already and move YXA to
> > github?
> >
> > I'm not anywhere near confident in my git skills,
On Wed, 2009-12-16 at 10:43 -0500, Dmitriy Kargapolov wrote:
> What are the essential benefits over subversion?
1) To make YXA less dependent on myself, and my current employer.
2) Let's face it - I'm really lousy at applying peoples patches. I want
to think of it as a kind of quality control, wh
Should I do what most people seem to have done already and move YXA to
github?
I'm not anywhere near confident in my git skills, but what better way is
there to learn than to start using it?
/Fredrik
___
Yxa-devel mailing list
Yxa-devel@lists.su.se
ht
On Mon, 2009-11-30 at 21:15 -0500, Kaiduan Xie wrote:
> Fredrik,
>
> Adding line number and module name to the log is quite helpful to read
> the log, at least from my personal experience.
Well, I'm not sure... I see the current (debug) log as more of a story
about what happened when YXA process
On Tue, 2009-12-01 at 13:33 -0500, Vance Shipley wrote:
> On Mon, Nov 30, 2009 at 10:10:38AM -0500, Kaiduan Xie wrote:
> } Then we need to save the log level to ETS or Mnesia, and every time,
> } you want to log, we need to read from ETS/Mnesia.
>
> That is not the functional way. The debug lev
On Mon, 2009-11-30 at 10:10 -0500, Kaiduan Xie wrote:
...
> > Ejabberd's solution sounds neat, but I think it should be measured
> > against the much simpler variant of adding a case statement checking the
> > log level before calling format_msg in logger:do_log/3.
>
> Then we need to save the log
On Sat, 2009-11-28 at 13:39 +0100, Mikael Magnusson wrote:
> On Sat, 2009-11-28 at 12:40 +0100, Mikael Magnusson wrote:
> > The yaws node info page (node_info.yaws) broke when the transactionstate
> > record was removed from transactionstatelist.hrl. See patch.
> >
> > /Mikael
>
> Patch...
Appli
On Fri, 2009-11-27 at 15:08 -0500, Kaiduan Xie wrote:
> Thank you Fredrik for the clarification on the rationale.
You are most welcome.
> In fact, spawning a process for each request is not creating
> performance bottleneck at all. I just want to understand the reason.
>
> Logger creates a lot o
On Thu, 2009-11-26 at 09:09 +0100, Fredrik Thulin wrote:
...
> >Upon receiving Message 100-4, message 180-5, and message 200-7, YXA
> > creates a process, and then just passes the message to client and
> > server transaction.
>
> Does it? I don't have the time t
On Wed, 2009-11-25 at 16:58 -0500, Kaiduan Xie wrote:
> Hi, all,
>
> I have two questions on the design of YXA.
I appreciate that someone takes the time to look that deep into the
source code. Thanks!
> 1. Client transaction and server transaction are implemented as
> gen_server, why not choose
On Wed, 2009-11-25 at 14:19 +0100, Fredrik Thulin wrote:
> On Sun, 2009-11-22 at 23:06 +0100, Mikael Magnusson wrote:
> ...
> > The trunk doesn't handle CANCEL requests correctly. CANCEL requests are
> > now sent to the INVITE server transaction where they are dropped:
&g
On Sun, 2009-11-22 at 23:06 +0100, Mikael Magnusson wrote:
...
> The trunk doesn't handle CANCEL requests correctly. CANCEL requests are
> now sent to the INVITE server transaction where they are dropped:
>
> INVITE: Server transaction: Received request is not particularly
> alike the first on
On Sun, 2009-11-22 at 18:18 +0100, Mikael Magnusson wrote:
> NAPTR lookup in subversion trunk is broken with the Erlang R13. Patch
> included.
Thanks! r1744.
/Fredrik
___
Yxa-devel mailing list
Yxa-devel@lists.su.se
https://lists.su.se/mailman/listinf
On Tue, 2009-08-25 at 21:47 +0200, Mikael Magnusson wrote:
> On Fri, 2009-06-26 at 21:58 +0200, Mikael Magnusson wrote:
> > Hi,
> >
> > there is a problem with the transaction matching code. If Yxa receives
> > an INVITE request over TCP and CANCEL over UDP, then Yxa is not able to
> > find the IN
On Wed, 2009-10-21 at 23:11 +0200, Mikael Magnusson wrote:
...
> The dependency on m4/erlang-erts.m4, which is copyright FSF, could be
> removed but it means autoconf 2.64 is required instead.
>
> I may be able to change the license of m4/erlang-extra.m4.
Great, let me know.
> > 2) It doesn't wo
On Sat, 2009-10-17 at 11:23 +0200, Mikael Magnusson wrote:
> On Thu, 2009-08-13 at 12:36 +0200, Fredrik Thulin wrote:
> > On Thu, 2009-08-13 at 15:53 +0700, Maxim Treskin wrote:
> > > Hello, folk
> > >
> > > Is there any reasons to hard specification of Erla
On Thu, 2009-10-01 at 11:32 +0200, Costin-Tiberiu RADU wrote:
...
> Is there something in the reverse direction?
> somefunct(#request{...}) -> Packet
>
> I was looking for something like this, but I could not find.
> Can somebody point me in the right direction?
Follow the trail from transportla
On Tue, 2009-08-25 at 22:41 +0200, Mikael Magnusson wrote:
> Fix handling of Re-SUBSCRIBE in eventserver.
> Remove parameters in call to PackageM:is_allowed_subscribe.
>
> patch attached: fix_resubscribe.dpatch
Applied, thanks. r1719.
I'm working on applying all the other patches you've sent tha
On Sat, 2009-04-25 at 20:47 +0200, Mikael Magnusson wrote:
> On Thu, 2009-04-23 at 09:58 +0200, Fredrik Thulin wrote:
> > Mikael Magnusson wrote:
> > > On Mon, 2009-04-20 at 19:26 +0200, Fredrik Thulin wrote:
> > >> Mikael Magnusson wrote:
App
On Thu, 2009-08-13 at 15:53 +0700, Maxim Treskin wrote:
> Hello, folk
>
> Is there any reasons to hard specification of Erlang OTP release
> version and OTP libraries version in .rel files?
> Any time when I rebuild YXA, I must fix configure.ac and all .rel
> files for success compilation. It is n
On Mon, 2009-07-20 at 15:38 +0800, enst wrote:
> svn checkout svn://anonsvn.it.su.se/yxa/trunk yxa
>
> drwxr-sr-x 2 root src 4.0K 07-20 15:30 build
> -rw-r--r-- 1 root src 3.5K 07-20 15:29 CHANGES
> -rw-r--r-- 1 root src 4.1K 07-20 15:29 configure.ac
> -rw-r--r-- 1 root src 3.2K 07-20 15:29 CO
On Fri, 2009-05-15 at 16:29 +0200, Jakob Schlyter wrote:
> hi,
>
> is there any way to block a list of From: from using the
> incomingproxy? I have a list of regexp:s that are never allowed to
> contact our proxy (i.e. appear in From:).
Yes, by implementing whatever access control you want in
On Tue, 2009-05-05 at 22:33 +0200, Krister Jarl wrote:
...
> >They got more than one thing wrong though - correct formatting would
> >include a leading whitespace on the second line too.
> >
> >Contact : ,\r\n sip:s...@192.168.0.3\r\n
> >
> >I note that they ALSO missed the comma. A bit much to fix
On Tue, 2009-05-05 at 19:10 +0200, Peter Fassberg wrote:
...
> But according to Postels Law we shoud fix it at the receiving end
> as well, if possible. :-)
Propose a patch. I'm not sure it will be clean enough to adopt, but I'd
love to be wrong.
/Fredrik
___
On Tue, 2009-05-05 at 14:13 +0200, Krister Jarl wrote:
> Hi!
>
> I've got a question regarding Yxa and TCP.
>
> Yxa sends an INVITE using a previously established TCP-connection to a
> remote destination. However, the remote destination closes the
> connection just after the INVITE has been sent
On Tue, 2009-05-05 at 14:12 +0200, Krister Jarl wrote:
> Hi!
>
> I've noted an issue regarding the parser in Yxa.
>
> Consider the following line:
> Contact: \rsip:s...@192.168.0.3\r\n
>
> Note the CR before the second URI. This seems to be an attempt to
> specify multiple Contact-headers, but t
Mikael Magnusson wrote:
> On Mon, 2009-04-20 at 19:26 +0200, Fredrik Thulin wrote:
>> Mikael Magnusson wrote:
>>> On Mon, 2009-04-06 at 22:18 +0200, Mikael Magnusson wrote:
>>>> With this patch applied you don't need to enable bindv6only system wide
>>>
Mikael Magnusson wrote:
> On Mon, 2009-04-06 at 22:18 +0200, Mikael Magnusson wrote:
>> With this patch applied you don't need to enable bindv6only system wide
>> to use IPv6 with Yxa on Linux as described in the README file. Some
>> programs, such as some versions of the SUN Java jre/plug-in, are
Mikael Magnusson wrote:
> This patch fixes a problem with the presence package. Handling of
> PUBLISH refresh and update requests were mixed up.
Applied, thanks. r1716. I read the e-mail on my mobile (thus marking it
'read') and then forgot about it, sorry. I'll have a look at your IPv6
patch no
--- Begin Message ---
Mikael Magnusson wrote:
Current Yxa trunk doesn't build because of a typo in
src/eldap/Makefile.in
@@ -92,4 +92,4 @@
.SUFFIXES: .c .o .hrl .beam .erl .boot .rel .rel-in .app .app-in
$(ebin_dir)/%.beam: %.erl
- $(ERLC) $(ERLC_FLAGS) $<
+ $(ERLC) $(L_ERLC_FL
Mikael Magnusson wrote:
> The configuration variable eventserver_for_package contains url:s as
> strings which need to be parsed before returned by
> request_homedomain_event.
>
>>From Yxa README:
>
> Example:
> [{"presence", "sip:presence.example.com"},
> {"ua-config", "sip:prov.example.com"
Costin-Tiberiu RADU wrote:
> Managed to fix it (modified all the names in the user database so that
> they authenticate with full sip URI (u...@sip_server)
> e.g. :
> {user, [{name, "noet...@gottingen.exp.org"},...
> instead of just
> {user, [{name, "Noether"},...
>
> I do not know why
Costin-Tiberiu RADU wrote:
...
> What is most intreaguing to me is that despite the information seems to
> exist in the user database in yxa, still, when an INVITE comes from one
> of the users to the other, yxa does not know how to find it.
Sure it does - YXA just doesn't manage to send UDP datag
Costin-Tiberiu RADU wrote:
> Thanks a lot for the help.
> I attached all the config files (including for the dns zone (I called it
> exp.org (from experimental - i.e. it has nothing to do with any real
> domain))).
> And yes I did what you suggested, and increased the udp max size to over
> 3000.
Costin-Tiberiu RADU wrote:
> I agree this is expected behaviour from a UA.
> The problem is that when I try to initiate a SIP session calling from
> one UA the other one, using yxa as a proxy, incomingproxy reports 500 No
> reacheable destination to the caller.
> From this behaviour I understand th
Costin-Tiberiu RADU wrote:
> Configured a DNS server for a fictional domain (separated the network
> from internet - at this moment it is experimental setup) (including with
> ORIGIN entries with NAPTR )
> Configured incomingproxy.config for the new domain.
> Configured /var/yxa/userdb with the ne
Mikael Magnusson wrote:
> I have found a problem with loop detection in Yxa. The Request-URI used
> when creating the loop cookie is not the original URI but the URI after
> any translation, which is a problem.
...
>
> My test scenario is:
>
> User A calls a telephone number N which is looked up
Costin-Tiberiu RADU wrote:
...
>
> debug<0.331.0>:Transport layer: Failed sending request (1353 bytes) to udp:
> 192.168.34.148:5069, error eaddrnotavail
I've never seen an eaddrnotavail before - not sure what that is. Do you
have some kind of exotic interface connection, like IP aliases on the
Costin-Tiberiu RADU wrote:
> I solved (sort of accidentally) the authentication problem . (configuration
> problem of the userdb).
Good.
> The clients are all in the same subnet. They all know of each other via
> /etc/hosts
> (ping, ssh, whatever other protocol works, so connectivity is not a pro
Costin-Tiberiu RADU wrote:
> Checked.
>
> And partially solved the problem.
>
> The problem is that the server does not want to register ekiga.
>
> On the other hand wehn I tried with kphone the registration worked.
>
> However, when trying to place a call, even if all the parties registrated
>
Costin-Tiberiu RADU wrote:
> Hi all,
>
> I started again to play with yxa and on a simple setup (with user
> authentication, one server and 2 users) no matter what I do (obviously
> not enough)
> I can't seem to be able to authenticate.
> The best answer I get is something like
> "401 Authenticati
Kobi Eshun wrote:
> Thanks for the hint. Answers to your related Qs inline. Cheers,
> --
> kobi
>
>
> On Oct 23, 2008, at 12:19 PM, Fredrik Thulin wrote:
>
>> Kobi Eshun wrote:
>>> Hi,
>>> I'm interested in using yxa only as a registrar a
Kobi Eshun wrote:
> Hi,
>
> I'm interested in using yxa only as a registrar and perhaps an event
> server, downstream of an ingress proxy that handles authentication.
> What is the best way to configure the incomingproxy to skip all
> authentication, or to authenticate by source IP/port? Tha
Costin-Tiberiu Radu wrote:
> Actually, compiling with erlang version OTP R12B.3-2 fails saying that
> a number of variables are not bounded . (the actual list is quite about
> 10 items).
> Is the latest developed version on svn closer to version 1.1 ?
Yes. I have about one outstanding item I've
Costin-Tiberiu Radu wrote:
> Hello,
>
> Is there any work done on the yxa at this moment?
> I've noticed that the latest version is from 2007 and the problem that
> bothered me the most it required some specific Erlang version.
> Would it be a dead end to try to hardcode hack the source to reflect
Evgeniy Khramtsov wrote:
> I'm just wondering why transactionlayer doesn't "pass to core" incoming
> CANCEL requests which match against existing INVITE-transaction? This
> means that yxa application never knows about cancelling the INVITE it
> has received.
From src/transactionlayer/servertra
Evgeniy Khramtsov wrote:
> Fredrik Thulin wrote:
>
>> Because it doesn't let the application perform validation,
>> normalization etc. on the configuration data and it is unknown if
>> entering something looking sensible (uhh) e.g. :
>>
>> {ssl, [{pr
Vance Shipley wrote:
> On Thu, Jul 31, 2008 at 12:46:55PM +0200, Fredrik Thulin wrote:
> } I'm not very fond of the application environment anymore.
>
> Why not? It's the OTP way.
Because it doesn't let the application perform validation, normalization
etc. on the c
Evgeniy Khramtsov wrote:
> Fredrik Thulin wrote:
>
>> If you make your AppModule:init/0 return MnesiaTables 'none',
>> sipserver:init_mnesia/1 should not do anything harmful, or does this
>> have some other drawback to you?
>
> sipserver:init_mnesia(
Evgeniy Khramtsov wrote:
> Hello!
>
> I'm working on SIP gateway to a foreign protocol network and I'm using
> YXA's SIP stack for that. All works fine, YXA is a realy amazing thing,
Thanks!
> but I have some questions and proposals.
> 1. When YXA application starts, it passes MnesiaTables to
Krister Jarl wrote:
...
> Can you please clarify for me why this is incorrect DNS configuration? I
> had the following setup in mind when writing the question.
>
> _sip._udp.sip.example.com. 41520 IN SRV 1 1 5060
> server1.example.com.
> _sip._udp.sip.example.com. 41520 IN SRV 2 1 506
John Koenig wrote:
> Good news.
>
> I managed to figure out the problem. It turns out that yaws was not
> naming its node and therefore did not specify the proper erlang cookie.
Good to hear that you solved it - I'm a bit slow on responding these
days since I'm on paternity leave.
Should the
Krister Jarl wrote:
> Hi!
>
>
>
> I've noticed that Yxa (pstnproxy) doesn't seem to start options-pinging
> blacklisted destination unless there are outgoing requests to be sent to
> that destination.
Right.
> What happens is that if we have a very low rate of outgoing calls to a
> destinatio
Dmitriy Kargapolov wrote:
> Hi all,
> sippipe/cancel_transaction/3 must check if state field
> clienttransaction_pid is actually pid() but not atom none, this could
> happen when, for example there are no more reachable destination
> available. If server transaction happened to be canceled at th
Pradeep B wrote:
> Hi,
>
> I download the Yxa-1.0 from your website and tried installing it and I
> got the error message given below.
>
> I have Erlang/OTP R11B-2 installed on my SUN server. I installed Yxa as
> per the instructions given in README
> I ran configure , make and make install suc
John Koenig wrote:
> Hi, I am new here, and to SIP in general, so please excuse me if I
> happen to say something foolish.
>
> I stumbled across Yxa's site this morning while I was looking at
> open-source SIP solutions. I was very pleased to find an Erlang based
> solution as I am an Erlang d
Vance Shipley wrote:
...
> } Also, I now get warnings about the yxa_app behavior being undefined
>
> I had seen that at one point but never looked into it.
> I'm not seeing that behaviour any more though. Can you
> send me the errors?
Never mind, I fixed it (missing -pa $(ebin_dir) to $(ERLC)
Vance Shipley wrote:
> Folks,
>
> Attached are patches to HEAD which clean up application packaging.
>
> A new library application named "yxa" is created and included in
> the other application specifications. The lists of modules and
> registered processes has been updated. Changed *.rel to *.
Vance Shipley wrote:
> Folks,
>
> Attached are patches to HEAD which clean up application packaging.
>
> A new library application named "yxa" is created and included in
> the other application specifications. The lists of modules and
> registered processes has been updated. Changed *.rel to *.
Vance Shipley wrote:
> Folks,
>
> Attached are patches to HEAD which clean up application packaging.
>
> A new library application named "yxa" is created and included in
> the other application specifications. The lists of modules and
> registered processes has been updated. Changed *.rel to *.
Vance Shipley wrote:
> In the architecture document at ~/project/yxa/architecture.html there
> is an error:
>
>"The transport layer receives requests and responses from
> the network and pass them on to the transport layer."
> ^
>
> It shou
Hi
I've just set up Fisheye for YXA. You can find it here :
http://loka.it.su.se/fisheye/browse/yxa/
/Fredrik
___
Yxa-devel mailing list
Yxa-devel@lists.su.se
https://lists.su.se/mailman/listinfo/yxa-devel
Fredrik Thulin wrote:
> Bruce Fitzsimons wrote:
>> Matthew O'Gorman wrote:
>>> are the ssl patches going to make it into r12 or is r12 fixed?
>>>
>>> mog
>>>
>> Hey Mog,
>>
>> It wasn't in the R12 snapshot I last looked at
YXA 1.0 is finished!
I hereby declare YXA 1.0 released. A little over two years since the
first stable release, I consider the current state of YXA to be
conforming to the project goals of scalability, stability and
interoperability.
Another way to say it is that since the features currently a
Bruce Fitzsimons wrote:
> Matthew O'Gorman wrote:
>> are the ssl patches going to make it into r12 or is r12 fixed?
>>
>> mog
>>
>>
> Hey Mog,
>
> It wasn't in the R12 snapshot I last looked at. As Matthias just said:
...
> Cheers,
> Bruce (who is not even close to being saintly)
I'll try to g
Hi
What Erlang/OTP version should YXA 1.0 require?
Distributed Erlang over SSL is broken in R11B-3, R11B-4 and R11B-5. This
feature is needed if you have more than one YXA application, and want
their inter-node communication to be protected from eavesdropping.
A fix for this has been made avai
Peter Krnjevic wrote:
> Good day,
>
> I have an awkward Tekelec that ignores Record-Route and insists on
> talking directly to UAs, making it very difficult (impossible) to detect
> hangups - BYE is sent directly to the UA, bypassing YXA.
> However, if I force Contact to point to Yxa, the BYE me
I just released the second release candidate for YXA 1.0.
These are the changes between 1.0rc1 and 1.0rc2 :
- Start using edoc for documentation of all functions.
- Fix bug in handling of race condition with CANCEL, which could
result in phones that never stop ringing.
- Handle UTF-8 in
Peter Krnjevic wrote:
> Does anyone have experience with Yxa running on redundant servers and
> have suggestions about this can be best accomplished?
Do you mean like having two incomingproxys serve a domain? Yes - I do
that everywhere.
How to set up location database replication is described i
Peter Krnjevic wrote:
> I'm trying to use record_route with incomingproxy but without much
> success. With and with out a record_route_url. Should this work?
Yes. Describe the problem in more detail please.
/Fredrik
___
Yxa-devel mailing list
Yxa-devel
Dmitriy Kargapolov wrote:
> Hi
> It was come to my attention that sometimes CANCEL request does not pass
> through proxy to destination. Failing scenario feature - proxy receives
> CANCEL request from call originator BEFORE provisional response 100 come
> from destination.
> Sippipe sends cancel
Peter Krnjevic wrote:
> Is there a CDR module for Yxa? And perhaps a RADIUS interface?
> With any luck Yxa can do everything SER can but better!
Not to my knowledge. I haven't got the need for CDR:s myself (we only do
billing where calls actually cost money (i.e. the PSTN), and we let the
equipm
Peter Krnjevic wrote:
> I've no idea what I'm doing wrong, but whether "outgoingproxy" is
> running or not seems to make no difference.
> Phones that require NAT from my LAN appear in the location database with
> the same ip address and port and all inbound calls are routed to the
> first phone.
W
Matthew O'Gorman wrote:
> there are at least parts of it still distributed with yxa, but you are
> correct none of it currently works.
What parts is that? I can't think of any specific B2BUA stuff being
distributed with YXA (although I don't even remember what's in the
src/unused/ directory).
/
Peter Krnjevic wrote:
> Googling shows others having problems with SSL distribution, though I
> don't know enough yet to know if the causes are the same.
> In the meantime, since both Yxa and Yaws are running on the same server,
> simply disabling SSL did the trick.
> Long-term though, I need to
Knight Tiger wrote:
> Fredrik,
> Thank you ! I am able to start the proxy server and I can
> make calls (!) using UDP. I have two users and they work beautifully.
>
> Now, I would like to set up the TLS so that I could encrypt signaling. So I
> create a CA and have the CA generate
Knight Tiger wrote:
> Fredrik,
> I thank you again for your quick and helpful response ! It
> was stupid of me to not check that first before invoking incoming proxy.
>
> I am able to start incoming proxy now ! I am currently listening on port
> 5060 (UDP and TCP)
Good.
...
> 20
Knight Tiger wrote:
> Fredrik,
> I thank you for your quick response. I am attaching the log file
> to this email as an attachment (which is why I am sending this one to you as
> well as the mailing list) because the log file is terribly long and I dont
> want to clog all your inbox wit
Knight Tiger wrote:
> Hi,
> I am new to Erlang. I have installed Erlang and YXA and the
> installation works fine.
>
> $ hostname
> a.b.com
>
> so I try to bootstrap
>
> yxa-bootstrap
>
> (It says Bootstrap complete) and I have a directory incomingproxy in
> /var/yxa/db/
>
> Now I sta
1 - 100 of 124 matches
Mail list logo
