ISCC Call Data Transfer Service

Question 1

ISCCEventCallDataXferService

Answer 1

Destination T-Server response to routing request. It will contain the access number to reach the resouce.

Question 2

ISCCDataXferResouce

Answer 2

Contains the Access Number the call needs to reach. Attribute of ISCCEventCallDataXferService.

Question 3

ISCC Determines Access Number

Answer 3

Access Number specified in the Attribute Extension, Association Field on DN, The DN number, Access Code on original switch, and the default access code on destination switch. Selected DN.

Question 4

ISCCEventCallDataXferSucceeded

Answer 4

Destination T-Server sends to Origination T-Server that the call has routed successfully

Question 5

EventRemoteConnectionSuccess

Answer 5

Message that the Origination T-server sends to the client that the call was routed successfully to the remote switch

Question 6

External Route Point

Answer 6

Used and registered only by the ISCC and with only route transaction type where the call arrives at a route point in which the ISCC will request to route call (RequestRouteCall) to destination. Call Matching is also performed on the route point by ISCC.

Question 7

request-tout

Answer 7

Config option that tells ISCC how long to wait for response from request sent.

Question 8

ISCCRequestGetCallDataXferService

Answer 8

ISCC request for resource to route call to and will contain the TrackingID(Token), ReferenceID(transaction number), Dest DN, DataXferType(transaction type) and UserData

Question 9

Direct Transaction Types

Answer 9

Access Resource is the DN and when the call arrives at Destination the ISCC will check if it has the correct attribute (except direct-notoken) during call matching. Call data and transaction detail is saved against the DN for preparation of call arrival.

Question 10

route-uui

Answer 10

ISCC Verifies the arrived call has the expected token. Required Destination Switch to have this configured.

Question 11

DNIS pool transaction type

Answer 11

DNIS type Access Resource that is configured on switch of destination.

Question 12

What happen when resources are available for Call Data Transfer?

Answer 12

ISCC stores the transaction detail for the access resources and determine the access number the PBX need to reach the resource.

Question 13

notoken(route and direct-notoken)

Answer 13

Calls arriving at the DN is expected while T-Server need to verify call parameters such as ani, call-id, network-callid, dnis.

Question 14

transaction type that are only supported in specific switches of the same type

Answer 14

callid, networkid, uui

Question 15

ISCCAttributeReferenceID

Answer 15

Reference the transaction number to trace the transaction in both T-server. Replaces the AttributeReferenceID when destination T-server receives the information to route call to.

Question 16

ISCCAttributeTrackingID

Answer 16

TrackingID and Token