Section 16: Data Transfer & Using 3
rd
Party Devices
T
ieline
T E C H N O L O G Y
Page 146
Remember, if you try to connect to a
T
ieline
codec with session data disabled,
you will have to ensure that the connection settings on both codecs are
identical because the dialing codec’s session data normally provides this
information to the remote codec. To avoid this problem, simple re-enable
session data.
Please note:
This is a global setting and will affect all connections on the codec.
16.7.4.
Checking Session Data is not Corrupted
It is possible to check the current state of session data being sent between two
codecs. To check this press the
ENTER/DIAL
button or the
MENU
SELECTOR
on the codec once connected. Scroll until you see the screen as
displayed in the following image.
Figure 32: Session Data Status Display
Some of the other messages you may see in the
Session Xfer
session include:
Timeout: If session data times-out this message will appear. This may
occur if attempting to connect to a non-
T
ieline
codec or if you
are attempting to connect using GSM.
Wait:
This will appear when session data transfer is being
negotiated.
Error:
This will appear when a software error has occurred. If you see
this message attempt to connect again. If repeated attempts to
connect fail, please contact [email protected] in order to
troubleshoot the problem.
16.7.5.
Limitations of Session Data Configuration
In most situations session data can be sent successfully over different
connections. Please take note of the following limitations in relation to
session data use.
1
2 3
4
----Cxn Details-<<--
Session Xfer:OK
Jit Buf (ms):480
IP Ver Loc:3 Rem:3
