VSAT satellite dish installation for Standard Chartered Bank in Ethiopia

Satellite Internet Forum.

Welcome, Guest.
Welcome to this satellite broadband discussion forum. Wherever you are and whatever your problem we are here to help each other. Connecting to the internet via satellite is not always easy but is critically important to those in remote places or with poor terrestrial infrastructure. Service providers and customers are encouraged to contribute. Register at the bottom of the forum home page if you wish to contribute or ask a question. VSAT service providers and satellite equipment sellers may feature their products free of charge; just register and get posting. Paid-for adverts, top left and top right, on all forum pages, are also available. Read the Forum rules.

Home Login Register

Satellite Internet forum › Satellite Internet - Americas › iDirect 5000 series Satellite Modem/Router

Pages: 1

Send Topic | Print

iDirect 5000 series Satellite Modem/Router

(Read 5923 times)

Ex Member Ex Member	May 23^rd, 2007 at 8:53am Hi All, Pls i need information on this series of iDirect satellite modem/router, particularly on the issue of the number of links that this equipment can carry. Thanks.
Back to top	IP Logged

Ex Member Ex Member	Reply #1 - May 23^rd, 2007 at 4:24pm What do you mean by "number of links"? Do you mean how many PCs can it support? Hundreds - depending on what they are doing. Do you mean, how many VoIP lines can it support? Probably around 18 depending on the codec used and the amount and type of other data traffic. Pat
Back to top	IP Logged

Ex Member Ex Member	Reply #2 - May 24^th, 2007 at 10:29am I mean supposing it has enough power, can it be used as a hub for other satellite links connected to it? Secondly what layer 2 protocol does it support?
Back to top	IP Logged

Ex Member

Ex Member

Reply #3 - May 24^th, 2007 at 3:20pm

No. It's not a hub - it's a terminal.

It supports a single VSAT link. It can be configured to run as a remote terminal on an iDirect shared network with services originating from a Hub at a teleport or corporate data center.

It can also be configured to run a single point-to-point iSCPC circuit (IP over SCPC).

It can't do both at the same time.

The protocol used over the VSAT link is an iDirect proprietary protocol designed to optimize efficiency and throughput.

Pat

IP Logged

Ex Member Ex Member	Reply #4 - May 24^th, 2007 at 3:39pm Thanks Pat but do u know what the proprietary protocol is called?
Back to top	IP Logged

Ex Member

Ex Member

Reply #5 - May 24^th, 2007 at 4:40pm

I'm sorry to say, I don't know what it's called. I have a very old document that traces the life of a packet through the iDirect link, which I obtained back when I worked for iDirect some 4 or 5 years ago when they first got started. I pulled it out, but it doesn't have any protocol identification name. It would probably be some cute name like iLA or iDirect Link Architecture or something like that. In looking at it, I can see that it's HDLC'ish in nature, once all the overhead is stripped off and then represented with a few select bits for reassembly on the other side.

It doesn't really matter what it's called because it's only going to work with another iDirect Hub or modem in iSCPC mode.

IP Logged

Ex Member

Ex Member

Reply #6 - May 27^th, 2007 at 1:25pm

The protocol is very similiar to Slotted Aloha, but has some significant differences. �

In iDirect proprietary, the payload of each upstream timeslot varies by type of FEC. �For example: at .793 the payload of a timeslot is 392 bytes. �You still have all the TDMA overhead (Unique Word) in the header and trailers and you can also add additional bytes to the Inroute Protocol Structure if you use things such as SAR, PAD, etc.

As for your original question: You have a remote (terminal). �Not a hub. �It is capable of locking onto a downstream carrier and can freq hop in mulitple D-TDMA upstreams to get back to the hub. �For instance, you can lock onto a large downstream carrier (say 6MB downstream carrier) and you might have return channels aka (inbounds/upstreams) configed as 3ea 2048k channels (TDMA, Freq hop) to get you back to the HUB (hence, return channels). �Heck, nothing says they have to be 2048k each. �They could be larger, say 2ea 3MB channels? �The config of your upstreams are dependent on the capability of your terminal and buying the right amount of MHz to support your requirement.

« Last Edit: Jun 8^th, 2007 at 3:34am by N/A »

IP Logged

Pages: 1

Send Topic | Print

Disclaimer, Terms of Use and Privacy Forum User Agreement Forum rules Cookie policy.