[cisco-voip] cisco route point conference.

Pedro Albuquerque pedroalb at gmail.com
Wed Apr 2 18:30:16 EDT 2008


Hi!



I'm developing a project in which there is a route point to conference with
some calls in IP Phones.

Suppose there are only 3 phones (ext. 1021, 1145 and 2116) in the network
and the route point (9900).



Firstly, 1145 calls 1021 and the call is established (call1). Then, 1021
calls the route point and another call is established (call2). Finally, this
last call conferences with the first call.  (call2.conference(call1))
(call2 and call1 are CallControlCall of each calls).



Then, 2116 calls 1021(call3). this call is accepted and the conference in
1021 is held.    1021 calls the route point and another call is
establiched(call4).

When I try to conference call4 with call3, I receive
CiscoConferenceStartedEv only and call3 is dropped.



-----------------



If instead 3 phones and 3 extensions, there are 3 phones and 4 extensions
(1021 and 9010 belong to terminal SEPXXXXXXXXXX)

Firstly, 1145 calls 1021 and the call is established (call1). Then, 1021
calls the route point and another call is established (call2). Finally, this
last call conferences with the first call.  (call2.conference(call1))
(call2 and call1 are CallControlCall of each calls).



Then, 2116 calls 9010(call3). this call is accepted and the conference in
9010 is held.    9010 calls the route point and another call is
establiched(call4).

If I try to conference these two calls, it works fine.

Why the call in the first environment drops? What are the limitations for
Cisco Route Point with conferencing issues?

These are the logs!!!!!!


Phone 1021 –    (line 1) conference in talking (1021, 1145 and 9900)

                        (line 2) 9900 in hold

"invalid conference particip…"

Phone 2116 – screen as it was in conference



Java console:  (notice that conference ended event does not appear when
trying to conference in the second enviroment)


CallCtlConnDialingEv - SEP0014A9BEC93C  // 1021 terminal
CallActiveEv on Address: 1021
Connection to address: 1021 is ConnCreatedEv
Connection to address: 1021 is ConnConnectedEv
Connection to address: 1021 is CallCtlConnInitiatedEv
Connection to terminal: 1021 is TermConnCreatedEv
Connection to terminal: 1021 is TermConnActiveEv
Connection to terminal: SEP0014A9BEC93C is CallCtlTermConnTalkingEv
Connection to address: 1021 is CallCtlConnDialingEv
Connection to address: 1021 is CallCtlConnEstablishedEv
calledAddress: 9900
callingAddress: 1021
terminal: SEP0014A9BEC93C
Connection to address: 9900 is ConnCreatedEv
Connection to address: 9900 is ConnInProgressEv
Connection to address: 9900 is CallCtlConnOfferedEv
[Ljavax.telephony.TerminalConnection;@1be1041
Connection to address: 1021 is ConnCreatedEv
Connection to address: 1021 is ConnConnectedEv
Connection to address: 1021 is CallCtlConnEstablishedEv
CALLING ADDRESS FOR RESERVE: 1021
port: 15002
Connection to terminal: SEP0014A9BEC93C is TermConnCreatedEv
Connection to terminal: SEP0014A9BEC93C is TermConnActiveEv
Connection to terminal: SEP0014A9BEC93C is CallCtlTermConnTalkingEv
Calling Address: 1021
Called Address: 9900
Connection to address: 9900 is ConnCreatedEv
Connection to address: 9900 is ConnInProgressEv
Connection to address: 9900 is CallCtlConnOfferedEv
conferenceController: [SEP0014A9BEC93C/[1021/(P1-palbuquerque)
GCID=(1,10448)->ACTIVE]->ESTABLISHED]->TALKING
Connection to address: 9900 is ConnAlertingEv
Connection to address: 9900 is CallCtlConnAlertingEv
Connection to address: 9900 is ConnAlertingEv
Connection to terminal: 1021 is TermConnCreatedEv
Connection to address: 9900 is CallCtlConnAlertingEv
Connection to terminal: PhoneRecord is TermConnCreatedEv
Connection to terminal: PhoneRecord is TermConnRingingEv
Connection to terminal: 1021 is TermConnRingingEv
Connection to terminal: PhoneRecord is CallCtlTermConnRingingEv
Connection to terminal: PhoneRecord is CallCtlTermConnRingingEv
Connection to address: 9900 is ConnConnectedEv
Connection to address: 9900 is CallCtlConnEstablishedEv
Connection to terminal: PhoneRecord is TermConnActiveEv
Connection to terminal: PhoneRecord is CallCtlTermConnTalkingEv
Calling Address: 1021
Called Address: 9900
TERMINAL PhoneRecord CiscoMediaOpenLogialChannelEv
PORT FOR CISCO PARAMETERS: 15002
Connection to address: 9900 is ConnConnectedEv
Connection to address: 9900 is CallCtlConnEstablishedEv
calledAddress: 9900
callingAddress: 1021
terminal: SEP0014A9BEC93C
Connection to terminal: 1021 is TermConnActiveEv
Connection to terminal: PhoneRecord is CallCtlTermConnTalkingEv
TERMINAL PhoneRecord CiscoRTPOutputStartedEv
TERMINAL PhoneRecord CiscoRTPInputStartedEv
CONFERENCE STARTED on Address: 1021
Connection to terminal: SEP0014A9BEC93C is CallCtlTermConnHeldEv
TERMINAL PhoneRecord CiscoRTPInputStoppedEv
TERMINAL PhoneRecord CiscoRTPOutputStoppedEv
Connection to terminal: SEP0014A9BEC93C is CallCtlTermConnHeldEv
Connection to terminal: SEP0014A9BEC93C is CallCtlTermConnTalkingEv
Connection to terminal: SEP0014A9BEC93C is CallCtlTermConnTalkingEv
Calling Address: 1021
Called Address: 9900
TERMINAL PhoneRecord CiscoMediaOpenLogialChannelEv
PORT FOR CISCO PARAMETERS: 15002
Connection to address: 2116 is ConnCreatedEv
Connection to address: 2116 is ConnConnectedEv
Connection to address: 2116 is CallCtlConnEstablishedEv
calledAddress: 9900
callingAddress: 1021
terminal: SEP0014A9BEC93C
Connection to address: 2116 is ConnCreatedEv
Connection to address: 2116 is ConnConnectedEv
Connection to address: 2116 is CallCtlConnEstablishedEv
CALLING ADDRESS FOR RESERVE: 1021
port: 15002
TERMINAL PhoneRecord CiscoRTPInputStartedEv
LocalPort: 15002
LocalAddress: /172.17.0.135
Codec G711ULAW64K used!

Thank you!!!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20080402/25be8d65/attachment.html 


More information about the cisco-voip mailing list