Re: [Asterisk-Dev] SS7 for *
--On Tuesday, October 19, 2004 22:48 +0800 Steve Underwood <[EMAIL PROTECTED]> wrote: Hi Ben Have you bought into the hype about internet time? :-) I said it was being tested, and it is. SS7 is quite big, so you don't give it a quick try and say all is well. It is functioning well enough to be handling traffic at a test site in Europe. Give it a few more weeks, and a solid polished solution should be available. Excellent news Steve! Should be very interesting to start seeing what happens with * now that it's starting to get more 'carrier' protocols like MFC/R2 and SS7 variants bolted onto it. ___ Asterisk-Dev mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-dev To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [Asterisk-Dev] SS7 for *
Tom Zimnicki wrote: [...] Not knowing who these guys are, there may be at least two other *SS7 groups working out there. Possible, but somewhat unlikely. There have been a number of people who thought it must be easy to achieve SS7 for *, starting from openss7. Nobody has actually got anywhere with that approach. We looked at the openss7 code. We moved on, and built something new from scratch. Just from the looking at the history of this thing, I would be surprised if another viable SS7 for * project exists. Why waste resources and effort if folks can agree on a common set of goals? That assumes a common set of goals it achievable. With the problems we still face over approvals, and so on, we can't even agree on 100% of our own goals. :-) Regards, Steve ___ Asterisk-Dev mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-dev To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [Asterisk-Dev] SS7 for *
Steve Underwood wrote: Kevin P. Fleming wrote: When I was talking to my telco about this they got very skittish :-) Isn't that standard practice? :-) "The fault is at your end." "But, I can see smoke billowing from your exchange building" "I'm sorry Sir. The fault really is at your end" For telcos, denial is a way of life. :-) My favorite: "We didn't do anything, but the problem is now fixed." Nick ___ Asterisk-Dev mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-dev To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [Asterisk-Dev] SS7 for *
This is a your mileage may vary issue...it will depend on the jurisdiction. In some places I've dealt with, they can't really prohibit you from using what you want without having serious cause. All they really want from you is to declare a software version, and pass a test suite against that version. They'll use something like this: http://www.tek.com/Measurement/network/diagnostics/spectra/datasheet/ If you pass, you're in. It's incumbent on you not to bugger the other LECs network. If you do, they'll shut you down until you can fix it. But I agree, scenarios will vary. Regards, Tom - Original Message - From: "Steve Underwood" <[EMAIL PROTECTED]> To: "Asterisk Developers Mailing List" <[EMAIL PROTECTED]> Sent: Monday, October 04, 2004 2:22 AM Subject: Re: [Asterisk-Dev] SS7 for * [EMAIL PROTECTED] wrote: Hello Steve It would have been good if you took a little more time to tell what do you mean by "SS7 for * is now working.", since there has been no such announcement. It hasn't been announced. It is still in testing. It is, however, functional. It is providing non-fee paying service somewhere in Europe, while its stability and reliability are being evaluated. What happens next is under discussion. Many places demand it be approved. Approval would cost upwards of $100,000 and the approval may not be portable to the various markets wanting this thing. ___ Asterisk-Dev mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-dev To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [Asterisk-Dev] SS7 for *
What I believe has worked though is when someone puts the software and the plan for future development up for grabs, trusted third parties can verify current functionality and developer bona fides and the developer then names a price for which they will release the code. Some folks set up an escrow with those trusted parties and when the goals are reached the software and dollars get released. I know I would help out to see this come true. My guess is that a lot of other folks would also put their money where there mouths are if there was a tangible goal. Some will be service providers putting up bigger piles of dough, others individuals looking to play with it and willing to part with a few dollars via PayPal. Maybe now is the time for others to speak up about it. Not knowing who these guys are, there may be at least two other *SS7 groups working out there. Why waste resources and effort if folks can agree on a common set of goals? Regards, Tom - Original Message - From: "Steve Underwood" <[EMAIL PROTECTED]> To: "Asterisk Developers Mailing List" <[EMAIL PROTECTED]> Sent: Monday, October 04, 2004 2:22 AM Subject: Re: [Asterisk-Dev] SS7 for * Can you please explain (you do know there is a bounty on it). All that work for a chocolate bar. No way :-) Seriously, I have never found bounties on these things to be of any interest. If you offer a bounty for something of modest size - something that is at most a few days work - it sometimes gets people interested in doing the work. A bounty for something as complex as SS7 will never reach the level where it justifies the man years of effort. I'd be interested in hearing of any examples where this has not been true. Regards, Steve ___ Asterisk-Dev mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-dev To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [Asterisk-Dev] SS7 for *
We use Kingston in the UK, they wont be charging us for interconnect testing, so if you fancy testing it with us (which we would be MORE than happy to do) then we can get the approval done, with little costs involved. Although remember that won't get you on the BT approved list, all that covers is that KCL would be happy. Linus ___ Asterisk-Dev mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-dev To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
RE: [Asterisk-Dev] SS7 for *
We use Kingston in the UK, they wont be charging us for interconnect testing, so if you fancy testing it with us (which we would be MORE than happy to do) then we can get the approval done, with little costs involved. Ben Merrills -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Linus Surguy Sent: 04 October 2004 16:44 To: Asterisk Developers Mailing List Subject: Re: [Asterisk-Dev] SS7 for * >> UK-ISUP has more than minor differences from the ETSI brand of ISUP (it >> is effectively a BT version). ETSI-ISUP in use in the UK (both version 1 >> & 2) are identical and the EU approval version would be fine for the UK. > > Its a long time since I worked on UK SS7, but it didn't seem like such a > big difference. Maybe, but UKISUP v2 is to replace BT-IUP as the BT interconnect protocol, so BT have had to shove a whole load of stuff into it to make it 'conform' to the old way of doing things. Linus ___ Asterisk-Dev mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-dev To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev ___ Asterisk-Dev mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-dev To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [Asterisk-Dev] SS7 for *
UK-ISUP has more than minor differences from the ETSI brand of ISUP (it is effectively a BT version). ETSI-ISUP in use in the UK (both version 1 & 2) are identical and the EU approval version would be fine for the UK. Its a long time since I worked on UK SS7, but it didn't seem like such a big difference. Maybe, but UKISUP v2 is to replace BT-IUP as the BT interconnect protocol, so BT have had to shove a whole load of stuff into it to make it 'conform' to the old way of doing things. Linus ___ Asterisk-Dev mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-dev To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [Asterisk-Dev] SS7 for *
On Mon, 2004-10-04 at 14:25, Steve Underwood wrote: [snip] > > Not only that, but in the USA (at least), approval will cover a > > _specific_ version of the code, and will very likely not allow the > > code to be distributed in source form at all (because the end user > > could then modify it and be running a "non-approved" version). > > The source code thing varies. When doing telecom approvals, I've been > told I could not include various information, such as source code and > schematics, in the documentation for the customer. Not always though. I > haven't been through this for a while, and things are more relaxed. > ISDN4Linux has been approved in the EU, and source is available in the > Linux kernel. They just have an arrangement whereby if you modify the > code it complains you are not running an approved version. I think they > do CRC tagging of the source, or something similar. [snap] A few years back I was involved in several approvals for (then) WorldCom in Europe with Ascend ASG equipment for interconnection to European incumbents like BT. The different versions of ISUP are a pain. That makes it difficult from a software point of view but also in terms of cost as you have to validate with each individual telco. And only the soft/hardware combo that was approved is allowed for interconnection. All seems pretty prohibitive without some serious money to get this done. Access to a test setup with a couple of SS7 switches (and a SS7 simulator/protocol analyzer) makes things much easier. Bit rusty so with some help from google here is some background info: Standards to be met for e.g. BT: * ITU-T http://www.itu.int * ETSI http://www.etsi.org * NICC PNO-ISC http://www.nicc.org.uk Service: Class 4 or 5 (or both) What to test for e.g. BT (Class 5): * ISUP functionality http://www.nicc.org.uk/nicc-public/Public/interconnectstandards/spec/nd1005_2000_08.pdf * MTP levels 2 & 3 http://www.nicc.org.uk/nicc-public/Public/interconnectstandards/spec/nd1007_2001_07.pdf Focus on: * Signalling link management (MTP levels 2 and 3) * Circuit management * Call set-up, release, and failure variants * Subscriber services (where SS7 affecting) * Handling of invalid and unexpected message contents and sequences * Hardware maintenance and failures * Switch recovery actions * Transmission alarms * Automatic Congestion Control (ACC) For info on SS7/C7 check out these tutorials: * http://www.pt.com/tutorials/ss7/ * http://www.pt.com/tutorials/iptelephony/ Regards, Patrick ___ Asterisk-Dev mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-dev To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
