The chan_ss7 module is a framework, and yes it is the ITU model, not the US
ANSI model. But could we not take this framework, identify differences, ie,
point codes, layout of IAM, etc, and start a patch program to move it closer
to the ANSI model. There is a lot of really good code in the program, and
it's not like starting from scratch....
The first goal would be to get the ISUP signaling functions working....
Thank You
Tom Chandler
----- Original Message -----
From: "P.B." <[EMAIL PROTECTED]>
To: <asterisk-ss7@lists.digium.com>
Sent: Friday, April 07, 2006 7:45 AM
Subject: Re: [asterisk-ss7] Chan_ss7.so
Hello.
It seems that there are quite a few people who want to use chan_ss7 in the
US.
I wrote this before - but the SS7 version used in the US is the ANSI
version which is quite different on many protocol levels from the
(European / rest of the world) ITU version.
Chan_ss7 is currently only implemented for the ITU version.
You can get it to work on a T1 (1.544 Mbit/s) trunk between two Asterisk /
chan_ss7 machines but not with any other live equipment.
Not even a simple audio channel since the US uses uLaw audio compression
and chan_ss7 is hardcoded to aLaw compression.
It is quite a big undertaking to create an ANSI compatible version of the
current chan_ss7 and then add other protocol layers which are
used quite often in the US like SCCP etc.
Sorry folks - but chan_ss7 currently only works in a ITU / E1 enviroment.
Peter.
Tim Danner wrote:
I would like to use this in the US, my problem is that I don't have much
time to work independantly currently. My issue really is that I need to
see the different levels of SS7 be laid out like:
TCAP: local databse
SCCP: remote SS7 database
ISUP: Circuit info
MTP3: GateWay for services
In some Configuation file to interface with Asterisk.
-----Original Message-----
From: Tom Chandler [mailto:[EMAIL PROTECTED] Sent: Thu 3/30/2006 11:50
AM To: asterisk-ss7@lists.digium.com Cc: Subject: [asterisk-ss7]
Chan_ss7.so
I have got chan_ss7.so (8.3) running on two Asterisk 1.2.4 servers back
to back with T1.5 connection between them.
I can complete calls in both directions between the two switches, so I
believe that SS7 is working.
I would like to extend the package,however before I work on it,
questions:
1. Is anyone using this package in the US, and if so, are the
connections to a STP or to other switch.
2. First requirement is to expand the package to support two signaling
links.
3. Add trunk cic (pic code ie, 0288 = AT&T), so it can be included in
the IAM.
4. As anyone studied the dump file, when capturing MSU's. I am having
trouble with the fields before the message type, and some other minor
layout issues.
If anyone has answers to the above, I would appreciate, and would welcome
anyone who wishes to work on these extensions to the package(Many more to
add, but start small).
Thank You
Tom Chandler
------------------------------------------------------------------------
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
asterisk-ss7 mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-ss7
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
asterisk-ss7 mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-ss7
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
asterisk-ss7 mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-ss7
