Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Cisco Community
- Technology and Support
- DevNet
- DevNet Collaboration
- Collaboration Knowledge Base
- JTAPI Terminal(Address) object not getting updated when partition changes
Options
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
1251
Views
0
Helpful
0
Comments
Options
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 01-24-2014 09:53 AM
This document was generated from CDN thread
Created by: Gitansh Chadha on 29-01-2009 06:48:05 PM
We are seeing another strange behavior with JTAPI (3.1(2.7)) in CUCM 5.1.2.
Setup:
Cluster with two Call manager server.
Pub: xx,xx,xx,xx
Sub: yy.yy.yy.yy
CUCM Group:
Primary: yy.yy.yy.yy
Secondary: xx,xx,xx,xx
Device: SEP00075027B3FA
Directory Number: 3955
Partition: Local_PT
Now I changed the partition on the DN to a new partition Internal_PT and made a call using makecall tool available with JTAPITools. If you look at the logs from that tool, it shows that terminal connection with this device is still using old partition Local_PT. Shouldn’t it reflect new partition Internal_PT in this terminal connection?
I tried few things to get the updated terminal connection.
1. Reset the device,didn’t work
2. Restart CTI Manager on both the nodes and tried connecting provider with both,didn’t work
3. Registered the phone to secondary CUCM in the CUCM group.,WORKED.
Now even if I move it back to the primary CUCM it works. It almost seems like that this new partition didn’t get updated in the CUCM memory till we registered the device to a new Call manager server.
Is this a known issue? Please find the jatpi logs in attachment.
Logs from call made using MakeCall utility from JTAPITools.
Adding Call observer to address 3953
Adding Adddress Observer to address 3953
Received CiscoAddrOutOfServiceEvfor 3953
Received CiscoTermInServiceEvfor SEP0006281B854C
Received CiscoAddrInServiceEvfor 3953
Adding Call observer to address 3953
Adding Adddress Observer to address 3953
Received CiscoAddrOutOfServiceEvfor 3953
Adding Terminal Observer to TerminalSEP0006281B854C
Adding Call observer to address 3955
Adding Adddress Observer to address 3955
Adding Terminal Observer to TerminalSEP00075027B3FA
Adding Call observer to address 3955
Adding Adddress Observer to address 3955
Adding Terminal Observer to TerminalSEP00075027B3FA
Received CiscoAddrOutOfServiceEvfor 3955
Received CiscoTermOutOfServiceEvfor SEP00075027B3FA
Received CiscoTermInServiceEvfor SEP00075027B3FA
Received CiscoAddrInServiceEvfor 3955
Received CiscoAddrInServiceEvfor 3955
Pausing 1000 milliseconds before making call
Making call #1 from 3953 to 3955 ActionThread
Done making call
Done making callDone making callPausing 1000 milliseconds before answering
Answering TerminalConnection [SEP00075027B3FA/3955:Local_PT/(P1-clarustestuser) GCID=(1,220168)->ACTIVE]->ALERTING->RINGING
Pausing 1000 milliseconds before disconnecting
Edited by: Gitansh Chadha on Jan 29, 2009 1:55 PM
Subject: Re: JTAPI Terminal(Address) object not getting updated when partition chang
Replied by: David Staudt on 29-01-2009 08:54:28 PM
This looks like unintended behaviour - i.e. a bug. I'm not aware that there is a known issue in this area.
As 5.1(2) is no longer receiving software updates, please try and reproduce this on the latest 5.1(3) update version of CM/JTAPI. If the problem persists, we can open a bug with the following info:
Subject: Re: JTAPI Terminal(Address) object not getting updated when partition chang
Replied by: Gitansh Chadha on 29-01-2009 09:30:58 PM
Hi David,
We have seen this issue with CUCM 6.1.2 as well.
We will try to work with our customer to collect the required logs.
Thanks.
Subject: Re: JTAPI Terminal(Address) object not getting updated when partition chang
Replied by: Gitansh Chadha on 30-01-2009 08:01:03 PM
Also, Would you be aware of any workaround we can use to force it return the right partition?
Subject: Re: JTAPI Terminal(Address) object not getting updated when partition chang
Replied by: David Staudt on 30-01-2009 08:21:32 PM
A workaround would depend somewhat on what the root cause turns out to be, but based on the things you've tried listed above, I'm not too hopeful there will be an easy one.
Subject: RE: Re: JTAPI Terminal(Address) object not getting updated when partition c
Replied by: Mourad Karoui on 04-04-2013 02:39:13 PM
hi,
I have another problem that resembles your
when I execute this command here is what appears to me (attached file)
please i really need an answear, thanks.
Subject: RE: Re: JTAPI Terminal(Address) object not getting updated when partition c
Replied by: David Staudt on 04-04-2013 05:01:21 PM
Can you describe the nature of the problem? Perhaps the app hangs here..?
If so it may be helpful to have the JTAPI logs (detailed level, all types). Also ensure the JVM is a supported version.
Subject: RE: Re: JTAPI Terminal(Address) object not getting updated when partition c
Replied by: Mourad Karoui on 04-04-2013 05:35:01 PM
my goal is to place a phone call from 2100 to 2010 but when i execute the makecall class as indicated in the attached file here's what appears :
Subject: RE: Re: JTAPI Terminal(Address) object not getting updated when partition c
Replied by: David Staudt on 04-04-2013 06:56:40 PM
Without looking at the JTAPI logs, it appears from your trace window that one of the devices may be a CTI port. CTI ports require additional steps to initialize (i.e. media type registration), which aren't present in the makecall sample app. Probably the sample code is stalled waiting for the CTI port in-service event to come.
Please give this a try using two phones or IP Communicator soft phone.
Subject: RE: Re: JTAPI Terminal(Address) object not getting updated when partition c
Replied by: Mourad Karoui on 04-04-2013 07:08:02 PM
yes i have already tried it with two cisco phones and it works, but it doesn't with the CTI Port
i think that i must modify the makcall class, but i don't know how
Subject: RE: Re: JTAPI Terminal(Address) object not getting updated when partition c
Replied by: David Staudt on 05-04-2013 03:35:52 PM
Apologies for not being able to go into more detail, but you should be able to learn the extra operations required in the section of the JTAPI Dev Guide which discusses CTI ports - the main step is to register media capabilities.
Note that if the app/CTI port does not actively send audio to a phone endpoint (i.e. if you don't implement an RTP audio stack), the phone will automatically end the call after awhile...
Subject: RE: Re: JTAPI Terminal(Address) object not getting updated when partition c
Replied by: Mourad Karoui on 20-04-2013 09:46:08 AM
hi david,
thanks a lot for your answers
I finally made a call from my computer "2100" to a cisco phone "2010" , but i don't know why it rings for only a second
so i tried to implement an "rtp audio stack" like you said, but i didn't know how.
so if you can give me a code example of that. it will help me so much
thank you again
Subject: RE: Re: JTAPI Terminal(Address) object not getting updated when partition c
Replied by: David Staudt on 23-04-2013 04:08:48 PM
Unfortunately we don't have sample code for RTP media termination, as that tends to be fairly OS/implementation specific. Some discussion around using JMF to send RTP media here: https://developer.cisco.com/web/jtapi/forums/-/message_boards/view_message/5198988
Subject: RE: Re: JTAPI Terminal(Address) object not getting updated when partition c
Replied by: Alexander Anikin on 24-04-2013 03:17:25 AM
As far as I remember your call automatically hangs up after 10 seconds of absence of RTP stream, so single ring is not the case. It should be something else like absence of media registering. In my project where CTI Ports send calls here and there I has more than enough time to put calls on hold yet not implementing rtp streams.
You have to register your CTI Port media capabilities though. I do it like this:
CiscoMediaCapability [] caps = new CiscoMediaCapability [1];
caps[0] = CiscoMediaCapability.G711_64K_30_MILLISECONDS;
((CiscoMediaTerminal)phone_term).register(myAddress, startPort, caps);
You will receive two events for each media stream in connected call: CiscoRTPInputStartedEv, CiscoRTPOutputStartedEv
You will receive two events for each disconnected media stream: CiscoRTPOutputStoppedEv, CiscoRTPInputStoppedEv
To get them your observer should implement CiscoTerminalObserver interface along with other observing interfaces.
Please make sure you get them at/after Established event occures to proceed with RTP streaming.
Here is the sample I used in testing of output medai stream. It plays raw wav file (G711 raw stream) repeatedly in portions of 20 milliseconds (it works with previously mentioned registration parameters). Receiver just eats everything coming to UDP port.
Subject: RE: Re: JTAPI Terminal(Address) object not getting updated when partition c
Replied by: Mourad Karoui on 25-04-2013 07:01:29 PM
Yes it works, the phone rings but never stop and when i pick up i can't hear anything
Created by: Gitansh Chadha on 29-01-2009 06:48:05 PM
We are seeing another strange behavior with JTAPI (3.1(2.7)) in CUCM 5.1.2.
Setup:
Cluster with two Call manager server.
Pub: xx,xx,xx,xx
Sub: yy.yy.yy.yy
CUCM Group:
Primary: yy.yy.yy.yy
Secondary: xx,xx,xx,xx
Device: SEP00075027B3FA
Directory Number: 3955
Partition: Local_PT
Now I changed the partition on the DN to a new partition Internal_PT and made a call using makecall tool available with JTAPITools. If you look at the logs from that tool, it shows that terminal connection with this device is still using old partition Local_PT. Shouldn’t it reflect new partition Internal_PT in this terminal connection?
I tried few things to get the updated terminal connection.
1. Reset the device,didn’t work
2. Restart CTI Manager on both the nodes and tried connecting provider with both,didn’t work
3. Registered the phone to secondary CUCM in the CUCM group.,WORKED.
Now even if I move it back to the primary CUCM it works. It almost seems like that this new partition didn’t get updated in the CUCM memory till we registered the device to a new Call manager server.
Is this a known issue? Please find the jatpi logs in attachment.
Logs from call made using MakeCall utility from JTAPITools.
Adding Call observer to address 3953
Adding Adddress Observer to address 3953
Received CiscoAddrOutOfServiceEvfor 3953
Received CiscoTermInServiceEvfor SEP0006281B854C
Received CiscoAddrInServiceEvfor 3953
Adding Call observer to address 3953
Adding Adddress Observer to address 3953
Received CiscoAddrOutOfServiceEvfor 3953
Adding Terminal Observer to TerminalSEP0006281B854C
Adding Call observer to address 3955
Adding Adddress Observer to address 3955
Adding Terminal Observer to TerminalSEP00075027B3FA
Adding Call observer to address 3955
Adding Adddress Observer to address 3955
Adding Terminal Observer to TerminalSEP00075027B3FA
Received CiscoAddrOutOfServiceEvfor 3955
Received CiscoTermOutOfServiceEvfor SEP00075027B3FA
Received CiscoTermInServiceEvfor SEP00075027B3FA
Received CiscoAddrInServiceEvfor 3955
Received CiscoAddrInServiceEvfor 3955
Pausing 1000 milliseconds before making call
Making call #1 from 3953 to 3955 ActionThread
Done making call
Done making callDone making callPausing 1000 milliseconds before answering
Answering TerminalConnection [SEP00075027B3FA/3955:Local_PT/(P1-clarustestuser) GCID=(1,220168)->ACTIVE]->ALERTING->RINGING
Pausing 1000 milliseconds before disconnecting
Edited by: Gitansh Chadha on Jan 29, 2009 1:55 PM
Subject: Re: JTAPI Terminal(Address) object not getting updated when partition chang
Replied by: David Staudt on 29-01-2009 08:54:28 PM
This looks like unintended behaviour - i.e. a bug. I'm not aware that there is a known issue in this area.
As 5.1(2) is no longer receiving software updates, please try and reproduce this on the latest 5.1(3) update version of CM/JTAPI. If the problem persists, we can open a bug with the following info:
- Detailed info of the test scenario: as you provided, including device names/DNs involved, timestamps
- JTAPI logs - detailed/all-types
- CTI Manager logs
- CallManager logs
Subject: Re: JTAPI Terminal(Address) object not getting updated when partition chang
Replied by: Gitansh Chadha on 29-01-2009 09:30:58 PM
Hi David,
We have seen this issue with CUCM 6.1.2 as well.
We will try to work with our customer to collect the required logs.
Thanks.
Subject: Re: JTAPI Terminal(Address) object not getting updated when partition chang
Replied by: Gitansh Chadha on 30-01-2009 08:01:03 PM
Also, Would you be aware of any workaround we can use to force it return the right partition?
Subject: Re: JTAPI Terminal(Address) object not getting updated when partition chang
Replied by: David Staudt on 30-01-2009 08:21:32 PM
A workaround would depend somewhat on what the root cause turns out to be, but based on the things you've tried listed above, I'm not too hopeful there will be an easy one.
Subject: RE: Re: JTAPI Terminal(Address) object not getting updated when partition c
Replied by: Mourad Karoui on 04-04-2013 02:39:13 PM
hi,
I have another problem that resembles your
when I execute this command here is what appears to me (attached file)
please i really need an answear, thanks.
Subject: RE: Re: JTAPI Terminal(Address) object not getting updated when partition c
Replied by: David Staudt on 04-04-2013 05:01:21 PM
Can you describe the nature of the problem? Perhaps the app hangs here..?
If so it may be helpful to have the JTAPI logs (detailed level, all types). Also ensure the JVM is a supported version.
Subject: RE: Re: JTAPI Terminal(Address) object not getting updated when partition c
Replied by: Mourad Karoui on 04-04-2013 05:35:01 PM
my goal is to place a phone call from 2100 to 2010 but when i execute the makecall class as indicated in the attached file here's what appears :
Subject: RE: Re: JTAPI Terminal(Address) object not getting updated when partition c
Replied by: David Staudt on 04-04-2013 06:56:40 PM
Without looking at the JTAPI logs, it appears from your trace window that one of the devices may be a CTI port. CTI ports require additional steps to initialize (i.e. media type registration), which aren't present in the makecall sample app. Probably the sample code is stalled waiting for the CTI port in-service event to come.
Please give this a try using two phones or IP Communicator soft phone.
Subject: RE: Re: JTAPI Terminal(Address) object not getting updated when partition c
Replied by: Mourad Karoui on 04-04-2013 07:08:02 PM
yes i have already tried it with two cisco phones and it works, but it doesn't with the CTI Port
i think that i must modify the makcall class, but i don't know how
Subject: RE: Re: JTAPI Terminal(Address) object not getting updated when partition c
Replied by: David Staudt on 05-04-2013 03:35:52 PM
Apologies for not being able to go into more detail, but you should be able to learn the extra operations required in the section of the JTAPI Dev Guide which discusses CTI ports - the main step is to register media capabilities.
Note that if the app/CTI port does not actively send audio to a phone endpoint (i.e. if you don't implement an RTP audio stack), the phone will automatically end the call after awhile...
Subject: RE: Re: JTAPI Terminal(Address) object not getting updated when partition c
Replied by: Mourad Karoui on 20-04-2013 09:46:08 AM
hi david,
thanks a lot for your answers
I finally made a call from my computer "2100" to a cisco phone "2010" , but i don't know why it rings for only a second
so i tried to implement an "rtp audio stack" like you said, but i didn't know how.
so if you can give me a code example of that. it will help me so much
thank you again
Subject: RE: Re: JTAPI Terminal(Address) object not getting updated when partition c
Replied by: David Staudt on 23-04-2013 04:08:48 PM
Unfortunately we don't have sample code for RTP media termination, as that tends to be fairly OS/implementation specific. Some discussion around using JMF to send RTP media here: https://developer.cisco.com/web/jtapi/forums/-/message_boards/view_message/5198988
Subject: RE: Re: JTAPI Terminal(Address) object not getting updated when partition c
Replied by: Alexander Anikin on 24-04-2013 03:17:25 AM
Mourad Karoui:so i tried to implement an "rtp audio stack" like you said, but i didn't know how.
As far as I remember your call automatically hangs up after 10 seconds of absence of RTP stream, so single ring is not the case. It should be something else like absence of media registering. In my project where CTI Ports send calls here and there I has more than enough time to put calls on hold yet not implementing rtp streams.
You have to register your CTI Port media capabilities though. I do it like this:
CiscoMediaCapability [] caps = new CiscoMediaCapability [1];
caps[0] = CiscoMediaCapability.G711_64K_30_MILLISECONDS;
((CiscoMediaTerminal)phone_term).register(myAddress, startPort, caps);
You will receive two events for each media stream in connected call: CiscoRTPInputStartedEv, CiscoRTPOutputStartedEv
You will receive two events for each disconnected media stream: CiscoRTPOutputStoppedEv, CiscoRTPInputStoppedEv
To get them your observer should implement CiscoTerminalObserver interface along with other observing interfaces.
Please make sure you get them at/after Established event occures to proceed with RTP streaming.
Here is the sample I used in testing of output medai stream. It plays raw wav file (G711 raw stream) repeatedly in portions of 20 milliseconds (it works with previously mentioned registration parameters). Receiver just eats everything coming to UDP port.
Subject: RE: Re: JTAPI Terminal(Address) object not getting updated when partition c
Replied by: Mourad Karoui on 25-04-2013 07:01:29 PM
Yes it works, the phone rings but never stop and when i pick up i can't hear anything
Labels:
Getting Started
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:
Customers Also Viewed These Support Documents