Specifications

MC55 AT Command Set
s
MC55_ATC_V03.03 Page 219 of 459 9/9/05
Confidential / Released
may result in a blocking of one of these service profiles.
• GPRS connections established over the Dial-Up Network do not use the embedded TCP/IP stack of MC55
and can be active at the same time. This allows the user to have two parallel GPRS connections: for example
for sending or receiving emails over a GPRS connection enabled by the TCP/IP stack while, at the same time,
surfing the Internet over a Dial-Up Network GPRS connection.
Using Internet Service AT commands on several interfaces (ASC0, ASC1 or Multiplex mode on ASC0):
• A connection profile can be created on one interface and then viewed or changed on all other interfaces.
• A service profile can be used only on one interface at a time:
- Changes to a service profile are allowed only on the same interface where it was created, trying to change
it on another interface is denied with "+CME ERROR: Invalid index". If queried with the read command
AT^SISS the entire profile is returned on the interface where the service profile was created, while on all
other interfaces only the service type of the profile is stated.
- If a service profile is active (after opening it with AT^SISO) on one interface, any attempt to open or close
the same service profile on another interface is denied with "+CME ERROR: Operation temporary not
allowed".
- To free a service profile for use on another interface, use the AT^SISS command and select service type
= "none". This action deletes the entire profile and restores all parameters of the profile to their initial
power-up state (all values are empty). For example, to remove the service profile 3, set AT^SISS=3,svr-
type,none. After this, a new profile 3 can be created on any other interface.
Address notation
Server addresses must be provided as IP addresses in standard dot-format (e.g. "192.168.1.2") or as server
address names resolvable by a DNS server (e.g. "smtp.myserver.de" or "pop3.myserver.de").
Inactivity timeouts
Inactivity timeouts are not part of the Internet AT command functionality implemented in MC55 and, if desired,
are the responsibility of the host application. It is recommended that the host application validates URCs and AT
command responses and reacts adequately, for example by sending a close message or starting a timer.