Hi John,

I got it. Thank you for your confirmation.

Best regards,

Thank you for your advise.
However as far as we checked, we were unable to find CallOptions, makeCall() above in JTAPI API.
Don't you talk about a different API instead of JTAPI?
Best regards,

Thank you very much for your quick response and information.

Best regards,

Hi John,

Thank you for your information.
Regarding the issue above may I ask you to add a feature and/or to change a feature so that we can identify terminals?
Or is there any REQUEST FORM to ask something for DevConnect?

Best regards,

Dear Sir,

Regarding the subject above I would like to ask you something.
In the previous message on Jul 7, 2021, I learned that AES based CTI services did not support "Multiple Device Access".
And I know that the last logged-in terminal is valid.
Is there any way to identify one of the 2 terminals?
If each terminal can be set a directory name independently, we can get a directory name by LucentTerminal.getDirectoryName().
For instance :
A-terminal with 5011 (=extention number) getDirectoryName() = "A-Term"
B-terminal with 5011 (=extention number) getDirectoryName() = "B-Term".
Is there any information to set to an each terminal and to get from an each terminal independently?

Best regards,

Hi John,
Thank you very much for your quick response and help.
Your answer is what i really wanted.
Best regards,

Dear Sir,

Regarding multi cluster configuration we assume each cluster need each Communication Manager.
Does every cluster need its own AES server as well as CM?

Thank you for your help in advance.
Best regards,

Hi John,

Thank you for your quick response and help.

1) I got it.
2) Can we register devices from AES/ACM console without using SDK API?
3) We are currently proceeding with the procedure for the paid support contract.

Best regards,

Dear Sir,

Attached, please find a file named ExtensionType_J179.png which is a diagram of VDN-Ringer structure.
Currently all of extenion number are set to type J179 and add CallListener to ringer, 5196 and 5197 without any problems.
Below is log for 09065693055-->05030331162(Topic number)-->5708(VDN)-->5198-->5196(ringer)-->5004(pickedup by Team button).
Though telephone system works correctly and log below is almost good, we would like to confirm several things as follows:
1) We are monitoring ringer, 5196 and 5197, but there is NO connectionAlerting event of 5196 and 5197. In addtion ringer number, 5196 and 5197 are never showed in this log. Why?
2) As you can see in the log, DistributingAddress is null instead of 05030331162. Why?

2023/01/12 15:20:30.270 - -------- connectionEstablished( CallControlConnectionEvent.CALLCTL_CONNECTION_ESTABLISHED )
2023/01/12 15:20:30.271 - Digit = null
2023/01/12 15:20:30.316 - eventConnectionAddress= 09065693055 1
2023/01/12 15:20:30.317 - ------ 100 ------
2023/01/12 15:20:30.317 - Event.CAUSE_SNAPSHOT (110)
2023/01/12 15:20:30.375 - UCID = 00001134361673472127, TsapiCallID = 13436
2023/01/12 15:20:30.381 - callingAddress = 09065693055 1
2023/01/12 15:20:30.382 - calledAddress = null
2023/01/12 15:20:30.382 - lastRedirectedAddress = null
2023/01/12 15:20:30.383 - V7CallInfo UCID = 00001134361673472127
2023/01/12 15:20:30.383 - DistributingAddress = null
2023/01/12 15:20:30.421 - DistributingVDNAddress= 5708 1
2023/01/12 15:20:30.473 - UCID = 00001134361673472127, TsapiCallID = 13436
2023/01/12 15:20:30.477 - Link CallingAddress = 09065693055 1
2023/01/12 15:20:30.481 - Link CalledAddress = 05030331162 null
2023/01/12 15:20:30.482 - Link redirectedAddress= null
2023/01/12 15:20:30.487 - -------- connectionAlerting( CallControlConnectionEvent.CALLCTL_CONNECTION_ALERTING )
2023/01/12 15:20:30.487 - Digit = null
2023/01/12 15:20:30.524 - eventConnectionAddress= 5708 1
2023/01/12 15:20:30.525 - ------ 100 ------
2023/01/12 15:20:30.525 - Event.CAUSE_SNAPSHOT (110)
2023/01/12 15:20:30.526 - UCID = 00001134361673472127, TsapiCallID = 13436
2023/01/12 15:20:30.530 - callingAddress = 09065693055 1
2023/01/12 15:20:30.538 - calledAddress = 05030331162 null
2023/01/12 15:20:30.543 - lastRedirectedAddress = null
2023/01/12 15:20:30.544 - V7CallInfo UCID = 00001134361673472127
2023/01/12 15:20:30.544 - DistributingAddress = null
2023/01/12 15:20:30.576 - DistributingVDNAddress= 5708 1
2023/01/12 15:20:30.628 - UCID = 00001134361673472127, TsapiCallID = 13436
2023/01/12 15:20:30.632 - Link CallingAddress = 09065693055 1
2023/01/12 15:20:30.635 - Link CalledAddress = 05030331162 null
2023/01/12 15:20:30.636 - Link redirectedAddress= null
2023/01/12 15:20:30.639 - -------- connectionEstablished( CallControlConnectionEvent.CALLCTL_CONNECTION_ESTABLISHED )
2023/01/12 15:20:30.640 - Digit = null
2023/01/12 15:20:30.643 - eventConnectionAddress= 09065693055 1
2023/01/12 15:20:30.643 - ------ 100 ------
2023/01/12 15:20:30.643 - Event.CAUSE_SNAPSHOT (110)
2023/01/12 15:20:30.644 - UCID = 00001134361673472127, TsapiCallID = 13436
2023/01/12 15:20:30.646 - callingAddress = 09065693055 1
2023/01/12 15:20:30.653 - calledAddress = 05030331162 null
2023/01/12 15:20:30.656 - lastRedirectedAddress = null
2023/01/12 15:20:30.656 - V7CallInfo UCID = 00001134361673472127
2023/01/12 15:20:30.656 - DistributingAddress = null
2023/01/12 15:20:30.678 - DistributingVDNAddress= 5708 1
2023/01/12 15:20:30.730 - UCID = 00001134361673472127, TsapiCallID = 13436
2023/01/12 15:20:30.735 - Link CallingAddress = 09065693055 1
2023/01/12 15:20:30.738 - Link CalledAddress = 05030331162 null
2023/01/12 15:20:30.740 - Link redirectedAddress= null

This is an EVENT when ringer 5196 is pickuped by Team button of 5004
2023/01/12 15:20:39.933 - -------- connectionEstablished( CallControlConnectionEvent.CALLCTL_CONNECTION_ESTABLISHED )
2023/01/12 15:20:39.934 - Digit = null
2023/01/12 15:20:40.026 - eventConnectionAddress= 5004 1, TALKING (98)
2023/01/12 15:20:40.026 - event Terminal Name = 5004
2023/01/12 15:20:40.027 - ------ 100 ------
2023/01/12 15:20:40.027 - Event.CAUSE_NORMAL (100)
2023/01/12 15:20:40.028 - UCID = 00001134361673472127, TsapiCallID = 13436
2023/01/12 15:20:40.031 - callingAddress = 09065693055 1
2023/01/12 15:20:40.034 - calledAddress = 5198 null
2023/01/12 15:20:40.035 - lastRedirectedAddress = 5198 null
2023/01/12 15:20:40.035 - V7CallInfo UCID = 00001134361673472127
2023/01/12 15:20:40.035 - DistributingAddress = null
2023/01/12 15:20:40.077 - DistributingVDNAddress= 5708 1
2023/01/12 15:20:40.129 - UCID = 00001134361673472127, TsapiCallID = 13436
2023/01/12 15:20:40.133 - Link CallingAddress = 09065693055 1
2023/01/12 15:20:40.133 - Link CalledAddress = 5198 null
2023/01/12 15:20:40.134 - Link redirectedAddress= 5198 null
2023/01/12 15:20:40.134 - OCI UUI type = null
2023/01/12 15:20:40.135 - OCI reason = OR_NEW_CALL (4)
2023/01/12 15:20:40.137 - OCI callingDevice = 09065693055 1
2023/01/12 15:20:40.139 - OCI calledDevice = 05030331162 null
2023/01/12 15:20:40.153 - Old CallID 0 = 13436, DeviceIDType = 0
2023/01/12 15:20:40.154 - Old DeviceID = 5198 null, Cause = EC_CALL_FORWARD (9)

Best regards,

In the previous attached diagram 5196 and 5197 are virtual ringer and 5198 is virtual extension.
According to your advice we tried station type 9611 and others for virtual ringer.
As a result this setting works as telephone system, i.e. virtual ringer is ringing and an incoming call is picked up by Teams button.
However we did not get correct log since we were unable to add listener to 5196, 5197 and 5198 due to TsapiResourceUnavailableException.
Do you have any suggestion to avoid this exception? Or is there any specific setting on the station type list to avoid this exception?
Don't you have the same problem before?

Best regards,

Attached, please find a file, named StationType.xlsx for your reference.
In your previous message you mentioned that H.323 is better for 5196 and 5197.
From the attached file which station type should we apply to 5196 and 5197?

Attached, please find a file, named StationType.xlsx for your reference.
In your previous message you mentioned that H.323 is better for 5196 and 5197.
From the attached file which station type should we apply to 5196 and 5197?

Attached, please find a file, named StationType.xlsx for your reference.
In your previous message you mentioned that H.323 is better for 5196 and 5197.
From the attached file which station type should we apply to 5196 and 5197?

Best regards,

5155 in the previous log is old and 5196, 5197 and 5198 have the same problem as 5155.

Thank you for your help.

Best regards,