<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>ICT Blog &#187; Startpagina</title>
	<atom:link href="http://ictblog.nl/category/startpagina/feed/" rel="self" type="application/rss+xml" />
	<link>http://ictblog.nl</link>
	<description>Weblog over Informatie en Communicatie Technologie</description>
	<lastBuildDate>Tue, 15 May 2012 13:20:26 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>ISDN Protocol</title>
		<link>http://ictblog.nl/2006/04/24/isdn-protocol/</link>
		<comments>http://ictblog.nl/2006/04/24/isdn-protocol/#comments</comments>
		<pubDate>Mon, 24 Apr 2006 17:15:02 +0000</pubDate>
		<dc:creator>Johan</dc:creator>
				<category><![CDATA[isdn]]></category>
		<category><![CDATA[Startpagina]]></category>

		<guid isPermaLink="false">http://ictblog.nl/?p=29</guid>
		<description><![CDATA[Aangezien de beschrijving van het ISDN protocol niet meer te vinden is op protocols.com heb ik via de Google cache het originele document opgezocht en hier geplaatst. ISDN protocols LAPD International Variants of ISDN ISDN Frame Structure ISDN Terminology ISDN (Integrated Services Digital Network) is an all digital communications line that allows for the transmission [...]]]></description>
			<content:encoded><![CDATA[<p>Aangezien de beschrijving van het ISDN protocol niet meer te vinden is op protocols.com heb ik via de Google cache het originele document opgezocht en hier geplaatst.</p>
<p><span id="more-29"></span></p>
<h1>ISDN protocols</h1>
<p><a href="#LAPD">LAPD</a><br />
<a href="#International">International Variants of ISDN</a><br />
<a href="#FrameStructure">ISDN Frame Structure</a><br />
<a href="#Terminology">ISDN Terminology</a></p>
<p>ISDN (Integrated Services Digital Network) is an all digital communications line that allows for the transmission of voice, data, video and graphics, at very high speeds, over standard communication lines. ISDN provides a single, common interface with which to access digital communications services that are required by varying devices, while remaining transparent to the user. Due to the large amounts of information that ISDN lines can carry, ISDN applications are revolutionizing the way businesses communicate.ISDN is not restricted to public telephone networks alone; it may be transmitted via packet switched networks, telex, CATV networks, etc.</p>
<p>The  ISDN is illustrated here in relation to the OSI model:</p>
<p><a href="http://ictblog.nl/files/2006/04/isdn-osi-model.gif" title="ISDN OSI Model" class="imagelink"><img src="http://ictblog.nl/files/2006/04/isdn-osi-model.gif" alt="ISDN OSI Model" /></a></p>
<p><a href="http://ictblog.nl/files/2006/04/isdn-access.gif" title="ISDN Access" class="imagelink"><img src="http://ictblog.nl/files/2006/04/isdn-access.gif" alt="ISDN Access" /></a><br />
ISDN applications</p>
<p><a title="LAPD" name="LAPD"></a><strong>LAPD</strong></p>
<p>The LAPD (Link Access Protocol &#8211; Channel D) is a layer 2 protocol which is defined in CCITT Q.920/921. LAPD works in the Asynchronous Balanced Mode (ABM). This mode is totally balanced (i.e., no master/slave relationship). Each station may initialize, supervise, recover from errors, and send frames at any time. The protocol treats the DTE and DCE as equals.</p>
<p>The format of a standard LAPD frame is as follows:</p>
<table border="1" cellpadding="3" cellspacing="0">
<tr>
<td>Flag</td>
<td>Address field</td>
<td>Control field</td>
<td>Information</td>
<td>FCS</td>
<td>Flag</td>
</tr>
</table>
<p><strong>Flag</strong><br />
The value of the flag is always (0x7E). In order to ensure that the bit pattern of the frame delimiter flag does not appear in the data field of the frame (and therefore cause frame misalignment), a technique known as Bit Stuffing is used by both the transmitter and the receiver.</p>
<p><strong>Address field</strong><br />
The first two bytes of the frame after the header flag is known as the address field. The format of the address field is as follows:</p>
<table border="1" cellpadding="3" cellspacing="0">
<tr align="center" bgcolor="#ffffff" valign="top">
<td>8</td>
<td>7</td>
<td>6</td>
<td>5</td>
<td>4</td>
<td>3</td>
<td>2</td>
<td>1</td>
</tr>
</table>
<table border="1" cellpadding="3" cellspacing="0">
<tr>
<td valign="top">EA1</td>
<td colspan="2">First Address Extension bit which is always set to 0.</td>
</tr>
<tr>
<td valign="top">C/R</td>
<td colspan="2">Command/Response bit. Frames from the user with this bit set to 0 are command frames, as are frames from the network with this bit set to 1. Other values indicate a response frame.</td>
</tr>
<tr>
<td valign="top">EA2</td>
<td colspan="2">Second Address Extension bit which is always set to 1.</td>
</tr>
<tr>
<td valign="top">TEI</td>
<td colspan="2">Terminal Endpoint Identifier. Valid values are as follows:</td>
</tr>
<tr>
<td valign="top"> </td>
<td>0-63</td>
<td>Used by non-automatic TEI assignment user equipment.</td>
</tr>
<tr>
<td valign="top"> </td>
<td>64-126</td>
<td>Used by automatic TEI assignment equipment.</td>
</tr>
<tr>
<td valign="top"> </td>
<td>127</td>
<td>Used for a broadcast connection meant for all Terminal Endpoints.</td>
</tr>
</table>
<p><strong>Control field</strong><br />
The field following the Address Field is called the Control Field and serves to identify the type of the frame. In addition, it includes sequence numbers, control features and error tracking according to the frame type.</p>
<p><strong>FCS</strong><br />
The Frame Check Sequence (FCS) enables a high level of physical error control by allowing the integrity of the transmitted frame data to be checked. The sequence is first calculated by the transmitter using an algorithm based on the values of all the bits in the frame. The receiver then performs the same calculation on the received frame and compares its value to the CRC.</p>
<p><strong>Window size</strong><br />
LAPD supports an extended window size (modulo 128) where the number of possible outstanding frames for acknowledgement is raised from 8 to 128. This extension is generally used for satellite transmissions where the acknowledgement delay is significantly greater than the frame transmission times. The type of the link initialization frame determines the modulo of the session and an &#8220;E&#8221; is added to the basic frame type name (e.g., SABM becomes SABME).</p>
<p><strong>Frame types</strong><br />
The following are the Supervisory Frame Types in LAPD:</p>
<table border="1" cellpadding="3" cellspacing="0">
<tr>
<td valign="top">RR</td>
<td>Information frame acknowledgement and indication to receive more.</td>
</tr>
<tr>
<td valign="top">REJ</td>
<td>Request for retransmission of all frames after a given sequence number.</td>
</tr>
<tr>
<td valign="top">RNR</td>
<td>Indicates a state of temporary occupation of station (e.g., window full).</td>
</tr>
</table>
<p>The following are the Unnumbered Frame Types in LAPD:</p>
<table border="1" cellpadding="3" cellspacing="0">
<tr>
<td valign="top">DISC</td>
<td>Request disconnection</td>
</tr>
<tr>
<td valign="top">UA</td>
<td>Acknowledgement frame.</td>
</tr>
<tr>
<td valign="top">DM</td>
<td>Response to DISC indicating disconnected mode.</td>
</tr>
<tr>
<td valign="top">FRMR</td>
<td>Frame reject.</td>
</tr>
<tr>
<td valign="top">SABM</td>
<td>Initiator for asynchronous balanced mode. No master/slave relationship.</td>
</tr>
<tr>
<td valign="top">SABME</td>
<td>SABM in extended mode.</td>
</tr>
<tr>
<td valign="top">UI</td>
<td>Unnumbered Information.</td>
</tr>
<tr>
<td valign="top">XID</td>
<td>Exchange Information.</td>
</tr>
</table>
<p>There is one Information Frame Type in LAPD:</p>
<table border="1" cellpadding="3" cellspacing="0">
<tr>
<td>Info</td>
<td>Information transfer frame.</td>
</tr>
</table>
<p><a href="http://ictblog.nl/files/2006/04/isdn-decode.gif" title="ISDN Decode" class="imagelink"><img src="http://ictblog.nl/files/2006/04/isdn-decode.gif" alt="ISDN Decode" /></a><br />
ISDN decode</p>
<p><strong><a title="International" name="International"></a>International Variants of ISDN</strong></p>
<p>The organization primarily responsible for producing the ISDN standards is the CCITT. The CCITT study group responsible for ISDN first published a set of ISDN recommendations in 1984 (Red Books). Prior to this publication, various geographical areas had developed different versions of ISDN. This resulted in the CCITT recommendation of a common ISDN standard for all countries, in addition to allocated variants definable for each country.</p>
<p>The use of nation-specific information elements is enabled by using the Codeset mechanism which allows different areas to use their own information elements within the data frames.</p>
<p>Following is a description of most ISDN variants:</p>
<p><strong>National ISDN1 (Bellcore)</strong><br />
This variant is used in the USA by Bellcore. It has four network-specific message types. It does not have any single octet information elements. In addition to Codeset 0 elements it has four Codeset 5 and five Codeset 6 information elements.</p>
<p><strong>National ISDN-2 (Bellcore)</strong><br />
The main difference between National ISDN-1 and ISDN-2 is parameter downloading via components (a component being a sub-element of the Extended Facility information element). These components are used to communicate parameter information between ISDN user equipment, such as an ISDN telephone, and the ISDN switch.</p>
<p>Other changes are the addition of the SEGMENT, FACILITY and REGISTER message types and the Segmented Message and Extended Facility information elements. Also, some meanings of field values have changed and some new accepted field values have been added.</p>
<p><strong>5ESS (AT&amp;T)</strong><br />
This variant is used in the USA by AT&amp;T. It is the most widely used of the ISDN protocols and contains 19 network-specific message types. It has no Codeset 5, but does have 18 Codeset 6 elements and an extensive information management element.</p>
<p><strong>Euro ISDN (ETSI</strong>)<br />
This variant is to be adopted by all of the European countries. Presently, it contains single octet message types and has five single octet information elements. Within the framework of the protocol there are no Codeset 5 and Codeset 6 elements, however each country is permitted to define its own individual elements.</p>
<p><strong>VN3, VN4 (France)</strong><br />
These variants are prevalent in France. The VN3 decoding and some of its error messages are translated into French. It is a sub-set of the CCITT document and only has single octet message types. The more recent VN4 is not fully backward compatible but closely follows the CCITT recommendations. As with VN3, some translation has taken place. It has only single octet message types, five single octet information elements, and two Codeset 6 elements.</p>
<p><strong>1TR6 (Germany)</strong><br />
This variant is prevalent in Germany. It is a sub-set of the CCITT version, with minor amendments. The protocol is part English and part German.</p>
<p><strong>ISDN 30 [DASS-2] (England)</strong><br />
This variant is used by British Telecom in addition to ETSI (see above). At layers 2 and 3 this standard does not conform to CCITT structure. Frames are headed by one octet and optionally followed by information. However most of the information is IA5 coded, and therefore ASCII decoded.</p>
<p><strong>Australia</strong><br />
This protocol is being superseded by a new Australian protocol. (The name of the protocol has not been released). It is a subset of the CCITT standard and has only single octet message types and information elements; it only has Codeset 5 elements.</p>
<p><strong>TS014 Australia</strong><br />
This is the new Australian ISDN PRI standard issued by Austel. This standard is very similar to ETSI.</p>
<p><strong>NTT-Japan</strong><br />
The Japanese ISDN service provided by NTT is known as INS-Net and its main features are as follows:</p>
<ul>
<li>Provides a user-network interface that conforms to the CCITT Recommendation Blue Book.</li>
<li>Provides both basic and primary rate interfaces.</li>
<li>Provides a packet-mode using Case B.</li>
<li>Supported by Signalling System No. 7 ISDN User Part with the network.</li>
<li>Offered as a public network service.</li>
</ul>
<p><strong>ARINC 746</strong><br />
In passenger airplanes today there are phones in front of each passenger. These telephones are connected in a T1 network and the conversation is transferred via a satellite. The signalling protocol used is based on Q.931, but with a few modifications and is known as ARINC 746. The leading companies in this area are GTE and AT&amp;T. In order to analyze ARINC, the LAPD variant should also be specified as ARINC.</p>
<p><strong>ARINC 746 Attachment 11</strong><br />
ARINC (Aeronautical Radio, INC.) Attachment 11 describes the Network Layer (layer 3) message transfer necessary for equipment control and circuit switched call control procedures between the Cabin Telecommunications Unit (CTU) and SATCOM system, North American Telephone System (NATS), and Terrestrial Flight Telephone System (TFTS). The interface described in this attachment is derived from the CCITT recommendations Q.930, Q.931 and Q.932 for call control and the ISO/OSI standards DIS 9595 and DIS 9596 for equipment control. These Network Layer messages should be transported in the information field of the Data Link Layer frame.</p>
<p><strong>ARINC 746 Attachment 17</strong><br />
ARINC (Aeronautical Radio, INC.) Attachment 17 represents a system which provides passenger and cabin crew access to services provided by the CTU and intelligent cabin equipment. The distribution portion of the CDS transports the signalling and voice channels from headend units to the individual seat units. Each zone within the aircraft has a zone unit that controls and services seat units within that zone.</p>
<p><strong>Northern Telecom &#8211; DMS 100</strong><br />
This variant represents Northern Telecom&#039;s implementation of National ISDN-1. It provides ISDN BRI user-network interfaces between the Northern Telecom ISDN DMS-100 switch and terminals designed for the BRI DSL. It is based on CCITT ISDN-1 and Q Series Recommendations and the ISDN Basic Interface Call Control Switching and Signalling Requirements and supplementary service Technical References published by Bellcore.</p>
<p><strong>DPNSS1</strong><br />
DPNSS1 (Digital Private Network Signalling System No. 1) is a common-channel signalling system used in Great Britain. It extends facilities normally only available between extensions on a single PBX to all extensions on PBXs that are connected together in a private network. It is primarily intended for use between PBXs in private networks via time-slot 16 of a 2048 kbit/s digital transmission system. Similarly it may be used in time-slot 24 of a 1.544 kbit/s digital transmission system. Note that the LAPD variant should also be selected to be DPNSS1.</p>
<p><strong>Swiss Telecom</strong><br />
The ISDN variant operated by the Swiss Telecom PTT is called SwissNet. The DSS1 protocol for SwissNet is fully based on ETS. Amendments to this standard for SwissNet fall into the category of definitions of various options in the standard and of missing requirements. They also address SwissNet-specific conditions, e.g., assuring compatibility between user equipment and SwissNet exchanges of different evolution steps.</p>
<p><strong>QSIG</strong><br />
QSIG is a modern, powerful and intelligent inter-private PABX signalling system. QSIG standards specify a signalling system at the Q reference point which is primarily intended for use on a common channel; e.g. a G.703 interface. However, QSIG will work on any suitable method of connecting the PINX equipment. The QSIG protocol stack is identical in structure to the DSSI protocol stack. Both follow the ISO reference model. Both can have an identical layer 1 and layer 2 (LAPD), however, at layer 3 QSIG and DSS1 differ.</p>
<p><strong><a title="FrameStructure" name="FrameStructure"></a>ISDN Frame Structure</strong></p>
<p>Shown below is the general structure of the ISDN frame.</p>
<table border="1" cellpadding="3" cellspacing="0">
<tr bgcolor="#ffffff">
<td align="center">
<p align="center">8</p>
</td>
<td align="center">
<p align="center">7</p>
</td>
<td align="center">
<p align="center">6</p>
</td>
<td colspan="2" align="center">5</td>
<td align="center">
<p align="center">4</p>
</td>
<td align="center">
<p align="center">3</p>
</td>
<td align="center">
<p align="center">2</p>
</td>
<td align="center">
<p align="center">1</p>
</td>
</tr>
<tr>
<td colspan="9" align="center" valign="top">
<p align="center">Protocol discriminator</p>
</td>
</tr>
<tr>
<td align="center">0</td>
<td align="center">0</td>
<td align="center">0</td>
<td align="center">0</td>
<td colspan="5" align="center">Length of reference call value</td>
</tr>
<tr>
<td align="center">Flag</td>
<td colspan="8" align="center">Call reference value</td>
</tr>
<tr>
<td align="center">0</td>
<td colspan="8" align="center">Message type</td>
</tr>
<tr>
<td colspan="9" align="center">Other information elements as required</td>
</tr>
<tr>
<td colspan="9" align="center">ISDN frame structure</td>
</tr>
</table>
<p><strong>Protocol discriminator</strong><br />
The protocol used to encode the remainder of the Layer.</p>
<p><strong>Length of call reference value</strong><br />
Defines the length of the next field. The Call reference may be one or two octets long depending on the size of the value being encoded.</p>
<p><strong>Flag</strong><br />
Set to zero for messages sent by the party that allocated the call reference value; otherwise set to one.</p>
<p><strong>Call reference value</strong><br />
An arbitrary value that is allocated for the duration of the specific session, which identifies the call between the device maintaining the call and the ISDN switch.</p>
<p><strong>Message type</strong><br />
Defines the primary purpose of the frame. The message type may be one octet or two octets (for network specific messages). When there is more than one octet, the first octet is coded as eight zeros. A complete list of message types is given in <em>ISDN Message Types</em> below.</p>
<p>ISDN Information Elements</p>
<p>There are two types of information elements: single octet and variable length.</p>
<p><strong>Single octet information elements</strong><br />
The single octet information element appears as follows:</p>
<table border="1" cellpadding="3" cellspacing="0">
<tr bgcolor="#ffffff">
<td valign="top">8</td>
<td valign="top">7</td>
<td valign="top">6</td>
<td valign="top">5</td>
<td valign="top">4</td>
<td colspan="2" valign="top">3</td>
<td valign="top">2</td>
<td valign="top">1</td>
</tr>
<tr>
<td valign="top">
<p align="center">1</p>
</td>
<td colspan="5" nowrap="nowrap" valign="top">
<p align="center">Information element identifier</p>
</td>
<td colspan="3" nowrap="nowrap" valign="top">
<p align="center">Information element</p>
</td>
</tr>
</table>
<p>Following are the available single octet information elements:</p>
<table border="1" cellpadding="3" cellspacing="0">
<tr>
<td nowrap="nowrap">1 000 &#8212;-</td>
<td>Reserved</td>
</tr>
<tr>
<td nowrap="nowrap">1 001 &#8212;-</td>
<td>Shift</td>
</tr>
<tr>
<td nowrap="nowrap">1 010 0000</td>
<td>More data</td>
</tr>
<tr>
<td style="height: 24px" nowrap="nowrap">1 010 0001</td>
<td style="height: 24px">Sending Complete</td>
</tr>
<tr>
<td nowrap="nowrap">1 011 &#8212;-</td>
<td>Congestion Level</td>
</tr>
<tr>
<td nowrap="nowrap">1 101 &#8212;-</td>
<td>Repeat indicator</td>
</tr>
</table>
<p><strong>Variable length information elements</strong><br />
The following is the format of the variable length information element:</p>
<table border="1" cellpadding="3" cellspacing="0">
<tr bgcolor="#ffffff">
<td valign="top">
<p align="center">8</p>
</td>
<td valign="top">
<p align="center">7</p>
</td>
<td valign="top">
<p align="center">6</p>
</td>
<td valign="top">
<p align="center">5</p>
</td>
<td valign="top">
<p align="center">4</p>
</td>
<td valign="top">
<p align="center">3</p>
</td>
<td valign="top">
<p align="center">2</p>
</td>
<td valign="top">
<p align="center">1</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="center">0</p>
</td>
<td colspan="7" valign="top">
<p align="center">Information element identifier</p>
</td>
</tr>
<tr>
<td colspan="8" valign="top">
<p align="center">Length of information elements</p>
</td>
</tr>
<tr>
<td colspan="8" valign="top">
<p align="center">Information elements (multiple bytes)</p>
</td>
</tr>
</table>
<p>The information element identifier identifies the chosen element and is unique only within the given Codeset. The length of the information element informs the receiver as to the amount of the following octets belonging to each information element. Following are possible variable length information elements:</p>
<table border="1" cellpadding="3" cellspacing="0">
<tr>
<td nowrap="nowrap" valign="top">0 0000000</td>
<td nowrap="nowrap" valign="top">Segmented Message</td>
</tr>
<tr>
<td valign="top">0 0000100</td>
<td valign="top">Bearer Capability</td>
</tr>
<tr>
<td valign="top">0 0001000</td>
<td valign="top">Cause</td>
</tr>
<tr>
<td valign="top">0 0010100</td>
<td valign="top">Call identify</td>
</tr>
<tr>
<td valign="top">0 0010100</td>
<td valign="top">Call state</td>
</tr>
<tr>
<td valign="top">0 0011000</td>
<td valign="top">Channel identification</td>
</tr>
<tr>
<td valign="top">0 0011100</td>
<td valign="top">Facility</td>
</tr>
<tr>
<td valign="top">0 0011110</td>
<td valign="top">Progress indicator</td>
</tr>
<tr>
<td valign="top">0 0100000</td>
<td valign="top">Network-specific facilities</td>
</tr>
<tr>
<td valign="top">0 0100111</td>
<td valign="top">Notification indicator</td>
</tr>
<tr>
<td valign="top">0 0101000</td>
<td valign="top">Display</td>
</tr>
<tr>
<td valign="top">0 0101001</td>
<td valign="top">Date/time</td>
</tr>
<tr>
<td valign="top">0 0101100</td>
<td valign="top">Keypad facility</td>
</tr>
<tr>
<td valign="top">0 0110100</td>
<td valign="top">Signal</td>
</tr>
<tr>
<td valign="top">0 0110110</td>
<td valign="top">Switchhook</td>
</tr>
<tr>
<td valign="top">0 0111000</td>
<td valign="top">Feature activation</td>
</tr>
<tr>
<td valign="top">0 0111001</td>
<td valign="top">Feature indication</td>
</tr>
<tr>
<td valign="top">0 1000000</td>
<td valign="top">Information rate</td>
</tr>
<tr>
<td valign="top">0 1000010</td>
<td valign="top">End-to-end transit delay</td>
</tr>
<tr>
<td valign="top">0 1000100</td>
<td nowrap="nowrap" valign="top">Packet layer binary parameters</td>
</tr>
<tr>
<td valign="top">0 1000101</td>
<td valign="top">Packet layer window size</td>
</tr>
<tr>
<td valign="top">0 1000110</td>
<td valign="top">Packet size</td>
</tr>
<tr>
<td valign="top">0 1101100</td>
<td valign="top">Calling party number</td>
</tr>
<tr>
<td valign="top">0 1101101</td>
<td valign="top">Calling party subaddress</td>
</tr>
<tr>
<td valign="top">0 1110000</td>
<td valign="top">Called party number</td>
</tr>
<tr>
<td valign="top">0 1110001</td>
<td valign="top">Called Party subaddress</td>
</tr>
<tr>
<td valign="top">0 1110100</td>
<td valign="top">Redirecting number</td>
</tr>
<tr>
<td valign="top">0 1111000</td>
<td valign="top">Transit network selection</td>
</tr>
<tr>
<td valign="top">0 1111001</td>
<td valign="top">Restart indicator</td>
</tr>
<tr>
<td valign="top">0 1111100</td>
<td valign="top">Low layer compatibility</td>
</tr>
<tr>
<td valign="top">0 1111101</td>
<td valign="top">High layer compatibility</td>
</tr>
<tr>
<td valign="top">0 1111110</td>
<td valign="top">User-user</td>
</tr>
<tr>
<td valign="top">0 1111111</td>
<td valign="top">Escape for ex</td>
</tr>
<tr>
<td valign="top">Other values</td>
<td valign="top">Reserved</td>
</tr>
</table>
<p>ISDN  Message Types</p>
<p>Following are possible ISDN message types:</p>
<p>Call Establishment</p>
<table border="1" cellpadding="3" cellspacing="0">
<tr>
<td>000 00001</td>
<td>Alerting</td>
</tr>
<tr>
<td>000 00010</td>
<td>Call Proceeding</td>
</tr>
<tr>
<td>000 00011</td>
<td>Progress</td>
</tr>
<tr>
<td>000 00101</td>
<td>Setup</td>
</tr>
<tr>
<td>000 00111</td>
<td>Connect</td>
</tr>
<tr>
<td>000 01101</td>
<td>Setup Acknowledge</td>
</tr>
<tr>
<td nowrap="nowrap">000 01111</td>
<td nowrap="nowrap">Connect Acknowledge</td>
</tr>
</table>
<p>Call Information Phase</p>
<table border="1" cellpadding="3" cellspacing="0">
<tr>
<td>001 00000</td>
<td>User Information</td>
</tr>
<tr>
<td>001 00001</td>
<td>Suspend Reject</td>
</tr>
<tr>
<td>001 00010</td>
<td>Resume Reject</td>
</tr>
<tr>
<td>001 00100</td>
<td>Hold</td>
</tr>
<tr>
<td>001 00101</td>
<td>Suspend</td>
</tr>
<tr>
<td>001 00110</td>
<td>Resume</td>
</tr>
<tr>
<td>001 01000</td>
<td>Hold Acknowledge</td>
</tr>
<tr>
<td>001 01101</td>
<td>Suspend Acknowledge</td>
</tr>
<tr>
<td>001 01110</td>
<td>Resume Acknowledge</td>
</tr>
<tr>
<td>001 10000</td>
<td>Hold Reject</td>
</tr>
<tr>
<td>001 10001</td>
<td>Retrieve</td>
</tr>
<tr>
<td>001 10011</td>
<td nowrap="nowrap">Retrieve Acknowledge</td>
</tr>
<tr>
<td nowrap="nowrap">001 10111</td>
<td>Retrieve Reject</td>
</tr>
</table>
<p>Call Clearing</p>
<table border="1" cellpadding="3" cellspacing="0">
<tr>
<td>010 00101</td>
<td>Disconnect</td>
</tr>
<tr>
<td>010 00110</td>
<td>Restart</td>
</tr>
<tr>
<td>010 01101</td>
<td>Release</td>
</tr>
<tr>
<td>010 01110</td>
<td nowrap="nowrap">Restart Acknowledge</td>
</tr>
<tr>
<td nowrap="nowrap">010 11010</td>
<td>Release Complete</td>
</tr>
</table>
<p>Miscellaneous</p>
<table border="1" cellpadding="3" cellspacing="0">
<tr>
<td>011 00000</td>
<td>Segment</td>
</tr>
<tr>
<td>011 00010</td>
<td>Facility</td>
</tr>
<tr>
<td nowrap="nowrap">011 00100</td>
<td>Register</td>
</tr>
<tr>
<td>011 01110</td>
<td>Notify</td>
</tr>
<tr>
<td>011 10101</td>
<td>Status inquiry</td>
</tr>
<tr>
<td>011 11001</td>
<td nowrap="nowrap">Congestion Control</td>
</tr>
<tr>
<td>011 11011</td>
<td>Information</td>
</tr>
<tr>
<td>011 11101</td>
<td>Status</td>
</tr>
</table>
<p><strong><a title="Terminology" name="Terminology"></a>ISDN Terminology</strong></p>
<p><strong>BRI</strong><br />
The Basic Rate Interface is one of the two services provided by ISDN. BRI is comprised of two B-channels and one D-channel (2B+D). The B-channels each operate at 64 Kbps and the D-channel operates at 16 Kbps. It is used by single line business customers for typical desk-top type applications.</p>
<p><strong>C/R</strong><br />
C/R refers to Command or Response. The C/R bit in the address field defines the frame as either a command frame or a response frame to the previous command.</p>
<p><strong>Codeset</strong><br />
Three main Codesets are defined. In each Codeset, a section of the information elements are defined by the associated variant of the protocol:</p>
<table border="1" cellpadding="3" cellspacing="0">
<tr>
<td valign="top">Codeset 0</td>
<td>The default code, referring to the CCITT set of information elements.</td>
</tr>
<tr>
<td valign="top">Codeset 5</td>
<td>The national specific Codeset.</td>
</tr>
<tr>
<td valign="top">Codeset 6</td>
<td>The network specific Codeset.</td>
</tr>
</table>
<p>The same value may have different meanings in various Codesets. Most elements usually appear only once in each frame.</p>
<p>In order to change Codesets two methods are defined:</p>
<table border="1" cellpadding="3" cellspacing="0">
<tr>
<td valign="top">Shift</td>
<td>This method enables a temporary change to another Codeset. Also termed as non-locking shift, the shift only applies to the next information element.</td>
</tr>
<tr>
<td>Shift Lock</td>
<td>This method implements a permanent change until indicated otherwise. Shift-Lock may only change to a higher Codeset.</td>
</tr>
</table>
<p><strong>CPE</strong><br />
Customer Premises Equipment &#8211; refers to all ISDN compatible equipment connected at the user sight. Examples of devices are telephone, PC, Telex, Facsimile, etc. The exception is the FCC definition of NT1. The FCC views the NT1 as a CPE because it is on the customer sight, but the CCITT views NT1 as part of the network. Consequently the network reference point of the network boundary is dependent on the variant in use.</p>
<p><strong>ISDN Channels B, D and H</strong><br />
The three logical digital communication channels of ISDN perform the following functions:</p>
<table border="1" cellpadding="3" cellspacing="0">
<tr>
<td valign="top">B-Channel</td>
<td>Carries user service information including: digital data, video, and voice.</td>
</tr>
<tr>
<td valign="top">D-Channel</td>
<td>Carries signals and data packets between the user and the network</td>
</tr>
<tr>
<td valign="top">H-Channel</td>
<td>Performs the same function as B-Channels, but operates at rates exceeding DS-0 (64 Kbps).</td>
</tr>
</table>
<p><strong>ISDN Devices</strong><br />
Devices connecting a CPE and a network. In addition to facsimile, telex, PC, telephone, ISDN devices may include the following:</p>
<table border="1" cellpadding="3" cellspacing="0">
<tr>
<td valign="top">TA</td>
<td>Terminal Adapters &#8211; devices that are used to portray non-ISDN equipment as ISDN compatible.</td>
</tr>
<tr>
<td valign="top">LE</td>
<td>Local Exchange &#8211; ISDN central office (CO). The LE implements the ISDN protocol and is part of the network.</td>
</tr>
<tr>
<td valign="top">LT</td>
<td valign="top">Local Termination &#8211; used to express the LE responsible for the functions associated with the end of the Local Loop.</td>
</tr>
<tr>
<td valign="top">ET</td>
<td>Exchange Termination &#8211; used to express the LE responsible for the switching functions.</td>
</tr>
<tr>
<td valign="top">NT</td>
<td>Network Termination equipment exists in two forms and is referred to accordingly. The two forms are each responsible for different operations and functions.</p>
<ul>
<li>NT1 &#8211; Is the termination of the connection between the user sight and the LE. NT1 is responsible for performance, monitoring, power transfer, and multiplexing of the channels.</li>
<li>NT2 &#8211; May be any device that is responsible for providing user sight switching, multiplexing, and concentration: LANs, mainframe computers, terminal controllers, etc. In ISDN residential environments there is no NT2</li>
</ul>
</td>
</tr>
<tr>
<td valign="top">TE</td>
<td>Terminal Equipment &#8211; any user device e.g.: telephone or facsimile. There are two forms of terminal equipment:</p>
<ul>
<li>TE1 &#8211; Equipment is ISDN compatible.</li>
<li>TE2 &#8211; Equipment is not ISDN compatible</li>
</ul>
</td>
</tr>
</table>
<p><strong>ISDN Reference Points</strong><br />
Reference points define the communication points between different devices and suggest that different protocols may be used at each side of the point. The main points are as follows:</p>
<table border="1" cellpadding="3" cellspacing="0">
<tr>
<td valign="top">R</td>
<td>A communication reference point between a non-ISDN compatible TE and a TA.</td>
</tr>
<tr>
<td valign="top">S</td>
<td>A communication reference link between the TE or TA and the NT equipment.</td>
</tr>
<tr>
<td valign="top">T</td>
<td>A communication reference point between user switching equipment and a Local Loop Terminator.</td>
</tr>
<tr>
<td valign="top">U</td>
<td>A communication reference point between the NT equipment and the LE. This reference point may be referred to as the network boundary when the FCC definition of the Network terminal is used.</td>
</tr>
</table>
<p>The following diagram illustrates the ISDN Functional Devices and Reference Points:<br />
<a href="http://ictblog.nl/files/2006/04/incompatible-isdn-devices.gif" title="Incompatible ISDN devices" class="imagelink"><img src="http://ictblog.nl/files/2006/04/incompatible-isdn-devices.gif" alt="Incompatible ISDN devices" /></a></p>
<p><strong>LAPD</strong><br />
The Link Access Protocol on the D-channel. LAPD is a bit orientated protocol on the data link layer of the OSI reference model. Its prime function is ensuring the error free transmission of bits on the physical layer (layer 1).</p>
<p><strong>PRI</strong><br />
The Primary Rate Interface is one of the two services provided by ISDN. PRI is standard dependent and thus varies according to country. In North America, PRI has twenty-three B-channels and one D-channel (23B+D). In Europe, PRI has thirty B-channels and one D-channel (30B+D).</p>
<p>The American B- and D-channels operate at an equal rate of 64 Kbps. Consequently, the D-channel is sometimes not activated on certain interfaces, thus allowing the time slot to be used as another B-channel. The 23B+D PRI operates at the CCITT designated rate of 1544 Kbps.</p>
<p>The European PRI is comprised of thirty B-channels and one D-channel (30B+D). As in the American PRI all the channels operate at 64 Kbps. However, the 30B+D PRI operates at the CCITT designated rate of 2048 Kbps.</p>
<p><strong>SAPI</strong><br />
Service Access Point Identifier -the first part of the address of each frame.</p>
<p><strong>TEI</strong><br />
Terminal End Point Identifier &#8211; the second part of the address of each frame.</p>
<p>Original document: http://www.protocols.com/pbook/isdn.htm</p>
]]></content:encoded>
			<wfw:commentRss>http://ictblog.nl/2006/04/24/isdn-protocol/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Wijziging links Startpagina dochters</title>
		<link>http://ictblog.nl/2006/03/14/wijziging-links-startpagina-dochters/</link>
		<comments>http://ictblog.nl/2006/03/14/wijziging-links-startpagina-dochters/#comments</comments>
		<pubDate>Tue, 14 Mar 2006 11:41:36 +0000</pubDate>
		<dc:creator>Johan</dc:creator>
				<category><![CDATA[Startpagina]]></category>

		<guid isPermaLink="false">http://ictblog.nl/?p=15</guid>
		<description><![CDATA[Sinds vorige week zijn de internet adressen van alle startpagina dochterpagina&#039;s gewijzigd. Deze zijn niet langer bereikbaar via paginanaam.pagina.nl, vanaf nu dient het adres te eindigen op .startpagina.nl (dus: paginanaam.startpagina.nl).Hoewel de oude .pagina.nl adressen met behulp van een 301 redirect omgeleid worden naar de nieuwe adressen, is deze overgang helaas niet zonder negatieve effecten op [...]]]></description>
			<content:encoded><![CDATA[<p>Sinds vorige week zijn de internet adressen van alle startpagina dochterpagina&#039;s gewijzigd. Deze zijn niet langer bereikbaar via paginanaam.pagina.nl, vanaf nu dient het adres te eindigen op .startpagina.nl (dus: paginanaam.startpagina.nl).Hoewel de oude .pagina.nl adressen met behulp van een 301 redirect omgeleid worden naar de nieuwe adressen, is deze overgang helaas niet zonder negatieve effecten op de bezoekersaantallen gebleven. Op het Startpagina prikbord wordt hier dan ook zeer druk over gediscussieerd. Omdat hier echter niets meer aan te doen is ben ik maar begonnen met het actief promoten van de nieuwe adressen, te beginnen op dit weblog.</p>
<p>Dit zijn de nieuwe adressen van mijn dochterpagina&#039;s:</p>
<ul>
<li><a href="http://backup.startpagina.nl/">backup.startpagina.nl</a></li>
<li><a href="http://backup-online.startpagina.nl">backup-online.startpagina.nl</a></li>
<li><a href="http://desktopmanagement.startpagina.nl/">desktopmanagement.startpagina.nl</a></li>
<li><a href="http://isdn.startpagina.nl/">isdn.startpagina.nl</a></li>
<li><a href="http://skype.startpagina.nl/">skype.startpagina.nl</a></li>
<li><a href="http://wordpress.startpagina.nl/">wordpress.startpagina.nl</a></li>
</ul>
<p>Ik verzoek een ieder die nog linkt naar de oude .pagina.nl adressen, deze te wijzigen zodat de goede positie in de zoekmachine resultaten spoedig hersteld zal zijn.</p>
]]></content:encoded>
			<wfw:commentRss>http://ictblog.nl/2006/03/14/wijziging-links-startpagina-dochters/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Desktopmanagement.startpagina.nl online</title>
		<link>http://ictblog.nl/2006/01/15/desktopmanagementstartpaginanl-online/</link>
		<comments>http://ictblog.nl/2006/01/15/desktopmanagementstartpaginanl-online/#comments</comments>
		<pubDate>Sun, 15 Jan 2006 07:19:36 +0000</pubDate>
		<dc:creator>Johan</dc:creator>
				<category><![CDATA[Desktop Management]]></category>
		<category><![CDATA[Startpagina]]></category>

		<guid isPermaLink="false">http://ictblog.nl/?p=14</guid>
		<description><![CDATA[Sinds afgelopen vrijdag is mijn nieuwe Startpagina dochterpagina online: desktopmanagement.startpagina.nl Ik hoop dat ik veel (tevreden) bezoekers zal mogen ontvangen! Overigens heb ik vorige week een post geschreven over wat desktop management nu precies inhoudt.]]></description>
			<content:encoded><![CDATA[<p>Sinds afgelopen vrijdag is mijn nieuwe Startpagina dochterpagina online: <a href="http://desktopmanagement.startpagina.nl/">desktopmanagement.startpagina.nl</a></p>
<p>Ik hoop dat ik veel (tevreden) bezoekers zal mogen ontvangen!</p>
<p>Overigens heb ik vorige week een post geschreven <a href="http://ictblog.nl/2006/01/03/wat-is-desktop-management/">over wat desktop management nu precies inhoudt</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://ictblog.nl/2006/01/15/desktopmanagementstartpaginanl-online/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Wat is desktop management?</title>
		<link>http://ictblog.nl/2006/01/03/wat-is-desktop-management/</link>
		<comments>http://ictblog.nl/2006/01/03/wat-is-desktop-management/#comments</comments>
		<pubDate>Tue, 03 Jan 2006 19:04:17 +0000</pubDate>
		<dc:creator>Johan</dc:creator>
				<category><![CDATA[Desktop Management]]></category>
		<category><![CDATA[Startpagina]]></category>

		<guid isPermaLink="false">http://ictblog.nl/?p=13</guid>
		<description><![CDATA[Ja, een goede vraag, nu desktopmanagement.startpagina.nl bijna klaar is vroeg iemand me wat desktop management eigenlijk is? Omdat ik denk dat veel mensen niet weten wat desktop management is heb ik besloten hier een post aan te wijden. Definitie Kortgezegd is desktop management het beheer van alle computers binnen een organisatie. Desktop management omvat overigens [...]]]></description>
			<content:encoded><![CDATA[<p>Ja, een goede vraag, nu <a href="http://desktopmanagement.startpagina.nl/">desktopmanagement.startpagina.nl</a> bijna klaar is vroeg iemand me wat desktop management eigenlijk is? Omdat ik denk dat veel mensen niet weten wat desktop management is heb ik besloten hier een post aan te wijden.</p>
<p><strong>Definitie </strong></p>
<p>Kortgezegd is desktop management het beheer van alle computers binnen een organisatie. Desktop management omvat overigens ook het beheer van laptops en andere mobiele apparaten zoals pda&#039;s en dus niet alleen de klassieke desktop pc&#039;s.</p>
<p>Desktop management is een onderdeel van het systeembeheer, dat het beheer van alle it infrastructuur binnen een organisatie omvat. Andere onderdelen van systeembeheer zijn bijvoorbeeld netwerkbeheer en database beheer.</p>
<p><strong>In het Nederlands?<br />
</strong></p>
<p>Hoewel Engelse termen in de ict branche gemeengoed zijn, kun je ook gewoon de term desktop beheer gebruiken :)</p>
<p><strong>Concrete voorbeelden</strong></p>
<p>Een aantal voorbeelden van desktop management taken:</p>
<ul>
<li>Virus scanning en e-mail filtering</li>
<li>Patch beheer</li>
<li>Helpdesk</li>
<li>Monitoring</li>
<li>Inventarisbeheer van hardware en software</li>
<li>Backup en restore van data</li>
<li>Migratie van data</li>
<li>Password resets</li>
</ul>
<p>Ik hoop dat het nu wat duidelijker is wat desktop management nu precies inhoud!</p>
]]></content:encoded>
			<wfw:commentRss>http://ictblog.nl/2006/01/03/wat-is-desktop-management/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Nieuwe dochterpagina in aantocht?</title>
		<link>http://ictblog.nl/2005/12/29/nieuwe-dochterpagina-in-aantocht/</link>
		<comments>http://ictblog.nl/2005/12/29/nieuwe-dochterpagina-in-aantocht/#comments</comments>
		<pubDate>Thu, 29 Dec 2005 12:38:55 +0000</pubDate>
		<dc:creator>Johan</dc:creator>
				<category><![CDATA[Desktop Management]]></category>
		<category><![CDATA[Startpagina]]></category>

		<guid isPermaLink="false">http://ictblog.nl/?p=12</guid>
		<description><![CDATA[Als lid van de Belangenvereniging Startpaginadochters ontvang ik regelmatig mails waarin melding wordt gemaakt van teruggegeven dochterpagina&#039;s. Af en toe komt er een interessant onderwerp voorbij waar ik me vervolgens op inschrijf. Leden van de BVS genieten namelijk een zekere voorrang bij het verkrijgen van het beheer over teruggegeven pagina&#039;s. Middels de link in de [...]]]></description>
			<content:encoded><![CDATA[<p>Als lid van de Belangenvereniging Startpaginadochters ontvang ik regelmatig mails waarin melding wordt gemaakt van teruggegeven dochterpagina&#039;s. Af en toe komt er een interessant onderwerp voorbij waar ik me vervolgens op inschrijf.</p>
<p>Leden van de BVS genieten namelijk een zekere voorrang bij het verkrijgen van het beheer over teruggegeven pagina&#039;s. Middels de link in de toegezonden mails kun je je interesse in het overnemen van de teruggegeven pagina kenbaar maken. Vervolgens wordt door middel van een loting een kandidaat aangewezen die aan Startpagina wordt voorgedragen.</p>
<p>Tot hoewel ik al een aantal keren heb meegedaan voor de loting heb ik daarmee weinig succes gehad. Tot vandaag. Ik ben namelijk als winnaar uit de loting voor het beheer van de <a href="http://desktopmanagement.startpagina.nl/">desktopmanagement.startpagina.nl</a> gekomen.</p>
<p>Hoewel er slechts twee kandidaten voor de overname van deze pagina waren ben ik erg blij dat ik uiteindelijk ben verkozen. Ik denk dat mijn motivatie een belangrijke factor is geweest in de uiteindelijke keuze. Als ITIL en MCP gecertificeerd ex-servicedeskmedewerker heb ik natuurlijk wel behoorlijk wat kennis van desktopmanagement :)</p>
<p>Hoewel de pagina onder de vorige eigenaar weinig succesvol was qua bezoekersaantallen, verwacht ik dat ik het een stuk beter kan doen. Desktopmanagement is namelijk een hot item, veel bedrijven zijn bezig met het outsourcen van het desktopbeheer en ik denk dat daarom <a href="http://desktopmanagement.startpagina.nl/">desktopmanagement.startpagina.nl</a> een interessante pagina is.</p>
<p>De volgende stap in dit proces is goedkeuring door Startpagina, maar ik verwacht dat dit geen problemen op zal leveren.</p>
<p><em>Update:<br />
Ik heb een mail gehad van de kwaliteitsdesk dat ik mag beginnen met het maken van mijn nieuwe dochterpagina! :) </em></p>
]]></content:encoded>
			<wfw:commentRss>http://ictblog.nl/2005/12/29/nieuwe-dochterpagina-in-aantocht/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Google op bezoek bij skype.startpagina.nl</title>
		<link>http://ictblog.nl/2005/12/20/google-op-bezoek-bij-skypestartpaginanl/</link>
		<comments>http://ictblog.nl/2005/12/20/google-op-bezoek-bij-skypestartpaginanl/#comments</comments>
		<pubDate>Tue, 20 Dec 2005 18:22:51 +0000</pubDate>
		<dc:creator>Johan</dc:creator>
				<category><![CDATA[Startpagina]]></category>

		<guid isPermaLink="false">http://ictblog.nl/?p=11</guid>
		<description><![CDATA[Een tijdje geleden schreef ik over de problemen die ik heb met de vermelding van skype.startpagina.nl in de database van de zoekmachine Google. Het is namelijk zo dat na ruim een jaar ik nog geen enkele bezoeker op skype.pagina.nl heb mogen ontvangen die via Google op mijn Startpagina dochter terecht is gekomen. Vanavond keek ik [...]]]></description>
			<content:encoded><![CDATA[<p>Een tijdje geleden schreef ik over de problemen die ik heb met de vermelding van <a href="http://skype.startpagina.nl/">skype.startpagina.nl</a> in de database van de <a href="http://ictblog.nl/2005/11/27/seo-perikelen-startpagina-dochters/">zoekmachine Google</a>. Het is namelijk zo dat na ruim een jaar ik nog geen enkele bezoeker op skype.pagina.nl heb mogen ontvangen die via Google op mijn Startpagina dochter terecht is gekomen.</p>
<p>Vanavond keek ik toevallig in mijn Nedstat statistieken (ik kan maar niet wennen aan Webstats4u :) ), en zag tot mijn verbazing dat ik iemand van Google op bezoek had gekregen:</p>
<p><img alt="Google op bezoek bij Skype Startpagina" src="http://ictblog.nl/files/2006/03/google-op-bezoek.gif" /></p>
<p>Ik ben onwijs benieuwd of dit betekent dat skype.pagina.nl binnenkort via de Google zoekmachine te vinden is!</p>
]]></content:encoded>
			<wfw:commentRss>http://ictblog.nl/2005/12/20/google-op-bezoek-bij-skypestartpaginanl/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WordPress.startpagina.nl eindelijk online!</title>
		<link>http://ictblog.nl/2005/11/24/wordpressstartpaginanl-eindelijk-online/</link>
		<comments>http://ictblog.nl/2005/11/24/wordpressstartpaginanl-eindelijk-online/#comments</comments>
		<pubDate>Thu, 24 Nov 2005 10:13:38 +0000</pubDate>
		<dc:creator>Johan</dc:creator>
				<category><![CDATA[Startpagina]]></category>
		<category><![CDATA[Wordpress]]></category>

		<guid isPermaLink="false">http://ictblog.nl/?p=8</guid>
		<description><![CDATA[Op 29 September schreef ik al dat ik bezig was met het samenstellen van wordpress.startpagina.nl. Vandaag is deze Startpagina dochter eindelijk online gegaan! Ik hoop dat dit een goede aanvulling is op de reeds bestaande informatie over WordPress, en dan vooral voor de Nederlandstalige WordPress gebruikers. De verwachting is dat met de introductie van de [...]]]></description>
			<content:encoded><![CDATA[<p>Op 29 September <a href="http://pagina.wordpress.com/2005/09/29/het-eerste-berichtje-voor-paginawordpresscom/">schreef ik</a> al dat ik bezig was met het samenstellen van <a href="http://wordpress.startpagina.nl/">wordpress.startpagina.nl</a>. Vandaag is deze <a href="http://www.startpagina.nl/">Startpagina</a> dochter eindelijk online gegaan!</p>
<p>Ik hoop dat dit een goede aanvulling is op de reeds bestaande informatie over WordPress, en dan vooral voor de Nederlandstalige WordPress gebruikers.</p>
<p>De verwachting is dat met de introductie van de nieuwe versie 2.0 van WordPress het aantal gebruikers explosief zal stijgen. Deze nieuwe versie van WordPress is niet alleen veel mooier vormgegeven, maar is ook nog eens veel makkelijker te gebruiken.</p>
<p>Indien je op- of aanmerkingen hebt over <a href="http://wordpress.startpagina.nl/">wordpress.startpagina.nl</a>, dan hoor ik dat graag in de comments.</p>
<p>Nieuwe sites kunnen worden aangemeld in het mailformulier, denk eraan dat alleen WordPress weblogs met een aparte &#039;Wordpress&#039; categorie voor plaatsing in aanmerking komen. De overige weblogs kunnen zich melden bij <a href="http://weblog.startpagina.nl/">weblog.startpagina.nl </a></p>
]]></content:encoded>
			<wfw:commentRss>http://ictblog.nl/2005/11/24/wordpressstartpaginanl-eindelijk-online/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WordPress.startpagina.nl bijna gereed</title>
		<link>http://ictblog.nl/2005/11/03/wordpressstartpaginanl-bijna-gereed/</link>
		<comments>http://ictblog.nl/2005/11/03/wordpressstartpaginanl-bijna-gereed/#comments</comments>
		<pubDate>Thu, 03 Nov 2005 15:31:00 +0000</pubDate>
		<dc:creator>Johan</dc:creator>
				<category><![CDATA[Startpagina]]></category>
		<category><![CDATA[Wordpress]]></category>

		<guid isPermaLink="false">http://ictblog.nl/?p=7</guid>
		<description><![CDATA[Ik ben inmiddels al een heel eind gevorderd met mijn linkverzameling voor wordpress.startpagina.nl. Het Startpagina beheerderscontract heb ik al ondertekend en retourgestuurd, en hiermee zijn alle formaliteiten afgerond. Op dit moment heb ik zo&#039;n 120 links verzameld, veel links verwijzen naar handige WordPress plugins en mooie WordPress templates. Ik heb lang nagedacht of ik ook [...]]]></description>
			<content:encoded><![CDATA[<p>Ik ben inmiddels al een heel eind gevorderd met mijn linkverzameling voor <a href="http://wordpress.startpagina.nl/">wordpress.startpagina.nl</a>. Het Startpagina beheerderscontract heb ik al ondertekend en retourgestuurd, en hiermee zijn alle formaliteiten afgerond.</p>
<p>Op dit moment heb ik zo&#039;n 120 links verzameld, veel links verwijzen naar handige WordPress plugins en mooie WordPress templates.</p>
<p>Ik heb lang nagedacht of ik ook een rubriek WordPress weblogs zou maken, en uiteindelijk heb ik besloten om dit wel te doen.<br />
Aangezien ik niet wil worden overstroomd met linkaanmeldingen heb ik wel een zÃ©Ã©r strikte voorwaarde voor links naar weblogs op <a href="http://wordpress.startpagina.nl/">wordpress.startpagina.nl</a>. De weblogs dienen namelijk een categorie &#039;Wordpress&#039; te hebben (Ã©n uiteraard hierin relevante posts hebben).<br />
Ik denk dat ik zo de grote stroom weblog aanmelders wat kan dammen en tegelijkertijd toch weblogs met handige WordPress informatie kan opnemen op mijn pagina.</p>
<p>De overige weblogs kunnen uiteraard terecht op <a href="http://weblog.startpagina.nl/">weblog.startpagina.nl</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://ictblog.nl/2005/11/03/wordpressstartpaginanl-bijna-gereed/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

