Log In
Developer Network
Technologies
Join the Network
Member Services
Events & Community
JTAPI (JTAPI) Developer Center
Overview
Documentation
Community
Wiki
Testing
Everything
This Site
Blogs
9.1 JTAPI Documentation Now Available
Prem Bejjam
09 Jan 2013
Unified Communications 9.0 Partner Bundle Offer Now Available to Order
Amanda Whaley
21 Sep 2012
Developer Partner 2012 US Update Presentations Available
George Gary
29 Jun 2012
Developer Partner 2012 London Update Presentations Available
George Gary
10 Feb 2012
Unified Communication 8.6 NFR Bundle Now Orderable
George Gary
22 Aug 2011
Showing 1 - 5 of 30 results.
Items per Page 5
Page
(Changing the value of this field will reload the page.)
1
2
3
4
5
6
of 6
First
Previous
Next
Last
Forums
Message Boards Home
Recent Posts
Statistics
Answer
(
Unmark
)
Mark as an Answer
« Back to Cisco JTAPI Questions
Network/Provider out of service.
Threads [
Previous
| Next ]
Michael Lemen
Posts:
2
Join Date:
11/20/08
Recent Posts
Network/Provider out of service.
Answer
12/13/08 1:08 AM
Mark as an Answer
Submit
Reply with Quote
Quick Reply
When an app looses network connection (ie, network cable pulled) JTAPI detects the loss of network and reports Provider and Terminals are out of service. (which seems correct).
JTAPI also reports that any active calls/connections are disconnected (ConnDisconnected, CallCtlConnDisconnected).
This seems odd since the calls/connections are not disconnected.
Basically I want to handle the case where the network interface has changed (ie, wired to wireless). From the apps perspective it looks like the calls are disconnected then seconds later they are back (ie, disconnect from first NI then connects on second NI).
Is there a way for an app to detect a call disconnect from a "outOfService"?
Sign in to vote.
Flag
Please sign in to flag this as inappropriate.
Top
David Staudt
Posts:
246
Join Date:
6/4/08
Recent Posts
Re: Network/Provider out of service.
Answer
12/13/08 2:11 AM as a reply to Michael Lemen.
Mark as an Answer
Submit
Reply with Quote
Quick Reply
Pls check CiscoCallChangedEv.getCiscoCause. You should receive a distinctive cause (don't recall exactly which one) when the cause is CTI disconnect/OOS.
Sign in to vote.
Flag
Please sign in to flag this as inappropriate.
Top
Collateral
No files available