1.2. DIAL Connection Profile
The following values must be programmed:
remote-address:
The remote-address value is always the same (*99***1#) and is the number providing access
to the UMTS network. You do not need to program this as on programming a 3gpp-apn value,
the remote address is automatically generated.
3gpp-apn:
This is the UMTS node through which the connection is carried out. This value depends on
the carrier.
3gpp-pdp-type:
Programs the type of Protocol Data Packet to be used in the connection. This depends on the
service provided by the carrier. Normally this is the IP which coincides with the default value.
3gpp-accessibility-control:
Permits you to enable connectivity control over the profile. This also permits different
accessibility controls for different profiles. This is explained in more detail further on in this
manual.
3gpp-bearer-service:
Permits programs for CSD connections (i.e. connections for a number, not connections for an
APN) to have a series of characteristics, allowing you to program type of norm, speed, etc.,
provided the inserted module supports this. This is explained in more detail further on in this
manual.
idle-time:
Indicates the time period where disconnection is carried out due to absence of data.
A 0 idle time value means the device will immediately execute the UMTS connection. Any
other value programs the disconnection without data period.
Example:
Config>global-profiles dial
-- DIAL PROFILE Configuration --
DIALPROF config>
DIALPROF config>profile UMTS default
DIALPROF config>profile UMTS dialout
DIALPROF config>profile UMTS 3gpp-apn movistar.es
DIALPROF config>profile UMTS 3gpp-accessibility-control traffic 6 all
DIALPROF config>profile UMTS idle-time 60
DIALPROF config>
DIALPROF config>exit
Config>
a)
3GPP-ACCESSIBILITY-CONTROL
One of the drawbacks to UMTS connections is verifying UMTS availability.
As already mentioned, the mechanism the PPP protocol has for point-to-point connection control
(Echo-request/Echo-reply) is ineffective in these connections as it is only significant at a “local” level
i.e. between the router and the connected module.
Various mechanisms have been implemented to verify the connection status. These can be grouped
into two types, intrusive (originating data traffic on line and therefore billable) and non-intrusive (does
not originate data traffic).
Each of the described mechanisms can be independently configured over each profile configured in
the interface.
TELDAT ROUTER– UMTS Configuration
II - 6
Doc.DM757-I
Rev.10.60