Hi,

I'm sorry if a thread already exists about this particular issue. I searched the forum before posting this but couldn't find answers to this specific problem.

We are receiving an exception when we try to launch a RegisterTerminal command on extension 32129.

Step to reproduce:
- Launch the Softphone and register to extension 32129
- Launch the Dashboard
- From the Dashboard:
- Start a session
- GetDeviceId for 32129
- RegisterTerminal on 32129, with media control = Client Mode and dependency mode = Dependent

At this point, an exception is displayed in the Dashboard output window (see below).
Everything works fine if I'm using Server Mode instead of Client Mode.

We are using IPCoDE release 4.00.0005 with IP Softphone R5.2 SP5.

Thanks,

Frederic

- - - - - - - - - - - - - - - - - - - - - - -
<?xml version="1.0" encoding="UTF-8"?>
<RegisterTerminalResponse xmlns="http://www.avaya.com/csta">
<device>
<deviceIdentifier xmlns:ns1="http://www.ecma-international.org/standards/ecma-323/csta/ed3" typeOfNumber="other" mediaClass="voice" bitRate="constant">32129:cmsim:192.168.20.204:0</deviceIdentifier>
</device>
<code>-3</code>
<reason>CM Connection lost - sockets closed due to Exception:Failure encoding com.avaya.mvcs.h323.Q931Msg:
Q.931 Message
{
Call Reference Value: 1
Message Type: SETUP
h323_uu_pdu:
{
h323_message_body:
{
setup:
{
protocolIdentifier:
{ 0.0.8.2250.0.5 }
sourceInfo:
{
terminal:
{
}

mc: false
undefinedNode: false
}

activeMC: false
conferenceID: 00000000-0000-1000-0000-0000FE800000
conferenceGoal: independentSupplementaryService
callType: pointToPoint
callIdentifier: 00000000-0000-0000-0000-0000FE800000
fastStart:
[{
forwardLogicalChannelNumber: 1
forwardLogicalChannelParameters:
{
dataType:
{
audioData:
{
g711Ulaw64k: 30
}

}

multiplexParameters:
{
h2250LogicalChannelParameters:
{
sessionID: 1
}

}

}

}
, {
forwardLogicalChannelNumber: 2
forwardLogicalChannelParameters:
{
dataType:
{
nullData:
{
}
}

multiplexParameters:
{
none:
}

}

reverseLogicalChannelParameters:
{
dataType:
{
audioData:
{
g711Ulaw64k: 256
}

}

multiplexParameters:
{
h2250LogicalChannelParameters:
{
sessionID: 1
mediaChannel:
{
ip: fe80:0:0:0:f87a:fda4:23a3:9816%11
port: 4725
}

mediaGuaranteedDelivery: false
mediaControlChannel:
{
ip: fe80:0:0:0:f87a:fda4:23a3:9816%11
port: 4726
}

mediaControlGuaranteedDelivery: false
silenceSuppression: false
}

}

}

}
]
mediaWaitForConnect: true
canOverlapSend: true
}

}

h245Tunneling: false
}

}
</reason>
</RegisterTerminalResponse>
- - - - - - - - - - - - - - - - - - - - - - -

Looks like you are passing IPV6 addresses with your registerTerminal request. AE Services only supports IPV4 at the moment. Double check what is in the dashboard for the RTP IP and RTCP IP. They are collected by the tool from the PC and I have noticed instances where even though the PC is configured for a IPV4 IP, windows is returning IPV6 IPs from some of the IP address discovery methods used in .NET.

ip: fe80:0:0:0:f87a:fda4:23a3:9816%11

Yep, that was it!

Thanks again,

Frederic