Hi,
On 2013-06-27 07:48, Pavel Troller wrote:
Hi Kaloyan,
Hi all,
sorry for joining so late, but i am on holidays (by the end of the
week)
and rarely checking my mailbox. Thanks to bad weather i did that today
:)
Never mind, I'm happy you're here!
To the OP:
while reading the first posts
Hi Kaloyan,
> Hi all,
> sorry for joining so late, but i am on holidays (by the end of the week)
> and rarely checking my mailbox. Thanks to bad weather i did that today :)
Never mind, I'm happy you're here!
>
> To the OP:
> while reading the first posts i thought it is an old problem with REL/
The problem with stock libss7 is that one will never complete the tests
required from telcos in Europe as it is missing functionality which ITU
have described in the test procedures.
Without the ISUP timers (the main functionality added from the patches)
it is just not possible and the link may
Thanks Kaloyan.
Before this thread, there were no mentions at all to a KNK tree, so I
though this was stock libss7.
I'm using my own patched libss7.
I processed over one million call setups with ten servers, with many
difficult setups (third party STPs, STPs 1000 miles away with
transmission lines
Almost forgot. Please do not post patches (if any) in this list, but
attach them to the SS7-27 issue instead with proper license agreement,
so it can be included in Asterisk codebase
On 2013-06-26 14:57, Kaloyan Kovachev wrote:
Hi all,
sorry for joining so late, but i am on holidays (by the en
Hi all,
sorry for joining so late, but i am on holidays (by the end of the week)
and rarely checking my mailbox. Thanks to bad weather i did that today
:)
To the OP:
while reading the first posts i thought it is an old problem with
REL/RSC loop (persistent on start with ANSI signaling) which
There are no stupid questions, correct.
However most of us that started using the internet back when nettiquete
was the rule of the land, know that asking questions that have been
asked dozens of times before is rude.
RTFM was coined a long time ago and Google is your friend is as old as
Google's
Hi!
So, I'm replying to my own original post, to keep the question and a
possible answer together without any excessive or unrelated information.
I hope I've found the cause of the problem and I hope I solved it. A
modified libss7 is now online and I'm waiting for busy hours to see, whether
it
Hi Nick!
> Hello Gentlemen,
>
> I find this post very interesting. I have set up many traditional T1s
> with my father here in Canada (I am 17), and looking to experiment
> with SS7 signaling. I have been reading up on it quite a bit and have
> some questions. I see you guys are using T1 cards fo
Hello Gentlemen,
I find this post very interesting. I have set up many traditional T1s
with my father here in Canada (I am 17), and looking to experiment
with SS7 signaling. I have been reading up on it quite a bit and have
some questions. I see you guys are using T1 cards for the
interconnect. Is
Hi Hans!
> On 2013-06-25 14:56, Marcelo Pacheco wrote:
>> What code are you using ?
>> Is this not stock libss7 ? Stock libss7 can't decode ISUP SUS/RES like that.
>>
>> In my code, I explicitly ignore ALL SUS / RES, they have no needed
>> processing associated with Brazilian ISUP.
>>
>> Asterisk
Hello Marcelo,
> What code are you using ?
> Is this not stock libss7 ? Stock libss7 can't decode ISUP SUS/RES like that.
No, it's not stock libss7. It's written in the subject, as well as in my first
sentence in the first post. It's a special branch, available for both Asterisk
and libsss7 (vers
On 2013-06-25 14:56, Marcelo Pacheco wrote:
What code are you using ?
Is this not stock libss7 ? Stock libss7 can't decode ISUP SUS/RES like that.
In my code, I explicitly ignore ALL SUS / RES, they have no needed
processing associated with Brazilian ISUP.
Asterisk and kernel dahdi version ?
I
What code are you using ?
Is this not stock libss7 ? Stock libss7 can't decode ISUP SUS/RES like that.
In my code, I explicitly ignore ALL SUS / RES, they have no needed
processing associated with Brazilian ISUP.
Asterisk and kernel dahdi version ?
If you enable dahdi_pcap:
# dahdi_pcap -c 16 -f
Hello Marcelo,
so I did some tracing. It was really hard to isolate MSUs for one particular
connection, I had to collect them from about 5 MB file, but ok, it's done,
and it's in total harmony with my original ideas. So, let's look at it with
me:
Initial conditions: There is a call running on LS
Hello Marcelo,
> Another possibility is you're mixing the whole thing in a single linkset
> where you must use two linksets in the way you explained.
I hope I'm not doing this.
>
> Can you see those errors with just a few test calls ?
>
No. These errors are occuring only in the high traffic p
Another possibility is you're mixing the whole thing in a single linkset
where you must use two linksets in the way you explained.
Can you see those errors with just a few test calls ?
I found about 20 bugs / structural design flaws in stock libss7 / dahdi
mtp2 support. With my changes the mtp2/
Hello Marcelo,
> Per usual, read the fine manual. Wait, there's no manual !
You're right :-).
> Since you seem to have done your part and actually knows some ss7 and
> isup, here comes a hint.
>
> You created two or more linksets where you must have a single one.
> libss7 don't have the ss7 rou
Per usual, read the fine manual. Wait, there's no manual !
Since you seem to have done your part and actually knows some ss7 and
isup, here comes a hint.
You created two or more linksets where you must have a single one.
libss7 don't have the ss7 routing feature.
In libss7 linkset concept is difer
19 matches
Mail list logo
