ISUP Version for LibSS7

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



"ITU" means ETSI - on most standards because ETSI is mostly a 1:1 implementation of most ITU standards. The main difference is that ETSI might remove some of the optional, ambiguity en ITU. Keep in mind that while ANSI is the national standards for US, in Europe you have loads of nations with national standards - but these will for most use ETSI 1:1 these days - but, well older stuff have a shitload of variants and custom solutions.
 
What country are u connecting to?
 
Vodafone in EMEA usually means that you connect to an Ericsson E10 MSC?
 
1. Do you actually have alignment on MTP2 and MTP3?
2. If so - do the MSC actually see the IAM when you call out - or do they attempt sending you an IAM?
 
Jan
 
> Date: Thu, 10 Feb 2011 20:55:34 +0300
> From: research at businesstz.com
> To: research at businesstz.com
> CC: asterisk-ss7 at lists.digium.com
> Subject: Re: [asterisk-ss7] ISUP Version for LibSS7
> 
> Hello Jan
> 
> Thanks for your reply. May you please advice how to check and conclude
> based on the CIC field and the PC. I am not in US so i presume the best
> option for me is ETSI as i am using ITU. Do i have to get it from the
> debugging or from the isup.c code? I cant see nothing on neither isup.c
> nor ss7.c nor their header files
> 
> The problem is that Vodafone are failing to make a connection until the
> version issue has been cleared.
> 
> Kind regards
> Sam
> 
> > hi Sam,
> >
> > I have not checked the code for some time, but it is in general 2 main
> > versions of ISUP - ANSI and ETSI. The easiest way to detect this is to
> > look at the size of CIC fields and Point Codes in the MTP layer.
> >
> > But, allowing a guess:
> >
> > I will assume libss7 is at least ANSI since it's developed in US
> > Chan_SS7 was developed in Denmark, meaning it is ETSI at least.
> >
> > Also, maybe more important - These ISUP implementations are to my
> > knowledge "a bare minimum", meaning you can just about send/receive an IAM
> > call - nothing more. But, again - its more than a year since I checked
> > theire code.
> >
> > Jan
> >
> >> Date: Thu, 10 Feb 2011 13:10:42 +0300
> >> From: research at businesstz.com
> >> To: asterisk-ss7 at lists.digium.com
> >> Subject: Re: [asterisk-ss7] ISUP Version for LibSS7
> >>
> >> Can someone be so kindly to let me know the version of SS7 ISUP used to
> >> implement libss7. How about chan_ss7.
> >>
> >> Regards
> >> Sam
> >> Muro, Sam wrote:
> >> > Hi Matt
> >> >
> >> > Can you please assist to tell the ISUP version used for libss7
> >> > implementation. I have tried to go though the source codes and README
> >> > files but couldnt find any clue. A link to the signaling document used
> >> for
> >> > this implementation will also help
> >> >
> >> > Regards
> >> > Sam
> >> > Muro, Sam wrote:
> >> >> Hi there
> >> >>
> >> >> We have libss7 installed but we are experiencing some call setup
> >> >> problem.
> >> >> Telco has requested to know SS7 ISUP version for them to match the
> >> same.
> >> >>
> >> >> Kindly advice
> >> >>
> >> >> Sam
> >> >>
> >> >>
> 
> 
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> 
> asterisk-ss7 mailing list
> To UNSUBSCRIBE or update options visit:
> http://lists.digium.com/mailman/listinfo/asterisk-ss7
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-ss7/attachments/20110212/c8b5bc65/attachment.htm>


[Index of Archives]     [Asterisk App Development]     [PJ SIP]     [Gnu Gatekeeper]     [IETF Sipping]     [Info Cyrus]     [ALSA User]     [Fedora Linux Users]     [Linux SCTP]     [DCCP]     [Gimp]     [Yosemite Backpacking]     [Deep Creek Hot Springs]     [Yosemite Campsites]     [ISDN Cause Codes]     [Asterisk Books]

  Powered by Linux