It seems to be a bug in transactionlayer.erl, function
from_transportlayer_response_no_transaction/3 should return
continue | {pass_to_core, AppModule, YxaCtx}
instead of
continue | {pass_to_core, AppModule}
Otherwise we got case clause exception in sipserver:my_apply/3 where
transactionlayer:fro
When you use @equiv, you should place next line @end, otherwise edoc
complains about the syntax invalid.
Thank you.
Fredrik Thulin wrote:
> I have just made the first YXA 1.0 release candidate available.
>
> YXA's development by no means stop at version 1.0, but I must say that
> it feels great
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 request to client transaction but th
I would prefer to get #2, since not everyone uses distributed over SSL
mode. Beside this it's better to stick with latest OTP release.
Second preference would be #4.
Fredrik Thulin wrote:
> Hi
>
> What Erlang/OTP version should YXA 1.0 require?
>
> Distributed Erlang over SSL is broken in R11B-
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 this moment,
we'll get function clau
What are the essential benefits over subversion?
___
Yxa-devel mailing list
Yxa-devel@lists.su.se
https://lists.su.se/mailman/listinfo/yxa-devel
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 exit value:
{{caught_error,{badmatch,{unparseable,{unquoted_displayname_is_n
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
on that.
On Tue, Jun 1, 2010 at 11:39 AM, Alexander Zhukov wrote:
>> Fredrik Thulin (FT) writes:
>
> FT> On Tue, 2010-06-01 at 15:52 +0400, Alexander Z
