SlideServe
Télécharger Obtenir Pro
Menu
Accueil Pro
Préférences
ApparenceLight Aide et commentaires
© SlideServe · v2026

Introduction to SS7: Basic and Distributed Setup for SMG-SS7

rudolf avatar
rudolf
16 diapositives · 319 Views · Jul 21, 2014

This text provides a comprehensive overview of SS7 (Signaling System No. 7), focusing on basic and distributed setup for the SMG-SS7 system. It explains how all signaling and voice channels can be managed within a single system, accommodate multiple application servers, and handle up to 32 E1s. The document also covers scenarios such as hardware failures and geographic distribution of voice gateways. Detailed instructions on managing channels, message handling, and recovery procedures are included, making it essential for understanding SS7 operational mechanics.

#introduction to ss7: basic and distributed setup for smg-ss7 #introduction to ss7: basic and distributed setup for smg-ss7 ppt #powerpoint #presentation
Introduction to SS7: Basic and Distributed Setup for SMG-SS7 - slide 1
01 / 16Introduction to SS7: Basic and Distributed Setup for SMG-SS7
1 / 17

Télécharger la présentation

Introduction to SS7: Basic and Distributed Setup for SMG-SS7
Une image / un lien ci-dessous est fourni (tel quel) pour télécharger la présentation

Politique de téléchargement : le contenu du site vous est fourni TEL QUEL pour votre information et votre usage personnel ; il ne peut être vendu, concédé sous licence ni partagé sur d’autres sites sans l’accord de son auteur.Le contenu vous est fourni TEL QUEL, pour votre information et votre usage personnel uniquement. Téléchargez la présentation en cliquant sur ce lien. Lors du téléchargement, si vous ne parvenez pas à télécharger une présentation, l’éditeur a peut-être supprimé le fichier de son serveur.Pendant le téléchargement, si vous ne parvenez pas à obtenir une présentation, le fichier a peut-être été supprimé par l’éditeur.

F I N

Plus de contenu associé

Transcription de la présentation

  1. Introduction to SS7 – Part 4 Konrad Hammel Sangoma Technologies

  2. SMG-SS7 – Basic Setup

  3. SMG-SS7 – Basic Setup • All sig and voice channels go to 1 system • Can talk to multiple application servers • Can handle up to 32 E1s • What if the customer has more E1s? • What happens if there is a hardware failure? • What if the customer has voice only E1s going to a different physical location?

  4. SMG-SS7 – Distributed Setup

  5. SMG-SS7 – Distributed Setup • “Multiple systems acting as 1” • Voice T1/E1s can be balanced over multiple systems • Voice GWs can fail with out customer loosing everything • Voice GWs can be located in different geographical locations since inter-system communication is over IP

  6. Trillium’s Relay • The simplest form of information exchange between two software modules is one module calling a predefined function of the other, restricting both modules to the same process space. However, modules can reside indifferent process spaces, with processes running on the same processor, different processors, or on two different machines. Relay software provides a communication channel to exchange information between two software modules independent of process space. (Relay – Service Definition, page 1-1)

  7. Trillium’s Layer Communication

  8. Pst Structure typedefstructpst /* parameters for SPstTsk */ { ProcIddstProcId; /* destination processor id (U16) */ ProcIdsrcProcId; /* source processor id (U16) */ EntdstEnt; /* destination entity (U8) */ Inst dstInst; /* destination instance (U8) */ EntsrcEnt; /* source entity (U8) */ Inst srcInst; /* source instance (U8) */ Prior prior; /* priority (U8) */ Route route; /* route (U8) */ Event event; /* event (U8) */ Region region; /* region (U8) */ Pool pool; /* pool (U8) */ Selector selector; /* selector (U8) */ CmIntfVerintfVer; /* interface version (U16) */ } Pst;

  9. Trillium’s Layer Communication - Relay

  10. Relay Channels in SMG-SS7

  11. Back to SMG-SS7

  12. Details of Relay in SMG-SS7 • Sig Channels • MTP3/ISUP runs on ProcId 1 only • MTP2/Layer1 can run on any ProcId • Each channel gets a unique ID value, and has it’s ProcId stored during configuration • Voice Channels • Cktsconfig info is stored in all systems (cc_spans) • Ckt ID values are based on ProcID • i.e. Proc 1 has 1000-1999

  13. Handling ISUP messages • Most messages (IAM, ACM, ANM, RSC, etc) are destined for 1 circuit only so we “hacked” ISUP to check the ckt ID and redirect the messages accordingly • Group messages (GRS, CGB, etc) aren’t allowed to span E1/T1 lines so ISUP again can use the ckt ID to redirect the message • Global messages (resume and pause) are broadcasted to all ProcIds

  14. Procedure on Relay Loss/Recovery ProcID 1 ProcID 2-9 Loss Bring sig_status to “down” for all ckts and throw Relay flag Sig links will fail on their own Recovery Send Layer manager status request for all circuits, if “unequipped” re-configure, if “equipped” sync the block state of circuit, clear relay flag Sig links will be activated by ProcID 1 • Loss • Send a BLO for all circuits on procID that is no longer reachable • Deactivate all sig links on ProcID • Recovery • Send UBL for all circuits on procId that is now reachable • Activate all sig links on ProcID

  15. Thank you.