McDewey

TAPI structures TAPI messages Action Conference Call model on CTI Remote Device : [C ' A1]-[ Original Call1]-[ state = Conference] [A1 ' Conference]-[ Conference Parent Call]-[State = CONNECTED] [A1 ' A1(EP)]-[Consult Call]-[state -CONFERENCE] Call Model on Enterprise Phone: Active Conference Calls: [C ' A1(CTIRD)]-[ Original Call1]-[ state = Conference] [A1(EP) ' Conference]-[ Conference Parent Call]-[State = CONNECTED] [A1(EP) ' A1(CTIRD)]-[Consult Call]-[state -CONFERENCE] RIU Conference Calls: [C ' A1]-[ Original Call1]-[ state = Conference] [A1 ' Conference]-[ Conference Parent Call]-[State = CONNECTED] [A1 ' A1(EP)]-[Consult Call]-[state -CONFERENCE] cBarge from CTI Remote Device is not supported as CTI Remote Device is a Static virtual Device. cBarge from EP [Enterprise phone] *** cBarge will be successful and CTIRemote Device, EP and Caller will be in Conference. *** as CTI Remote Device doesn't report RIU calls, there won't be RIU Conference created on CTI Remote Device reflecting Active Conference Call on EP Barge Operation will fail as CTI Remote Devices doesn't have BIB. Variation: Barge Operation on Enterprise Phone Expected result would be same as observed on CTI Remote Device Variation : Test the same with CSF Device in Extend Mode URI Dialing -Basic Incoming Call to CTI Remote Device Precondition: InAddition to configuration from previous usecases CTI Remote Device: Line: Line-A (DN -2000) (URI Configured -drajesh@cisco.com) C (IP Phone -Name: SEPxxxxxxxx) Line: Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 627 Message Sequence Charts Message Sequence Charts