CUCM, VCS-Core and Edge, B2B Calling

I have CUCM ver 9.1(2) and VCS 8.1.1 in my environment, the VCS-C and VCS-E are currently setup to do MRA which is working fine for the vpn-less Jabber.
We also have a number of SX series Telepresence codecs dotted about which are registered to the CUCM and used for internal video conferencing, now the company is wanting the ability for outside video conferencing so need to setup the B2B capability (licencing has been sorted out already for Rich Media Sessions)
I've been ploughing through a number of docs on this, I have not found one yet specifically for CUCM registered devices and VCS doing nothing but firewall traversal, so the guides I've been working from are for enabling CUCM registered devices to talk to VCS registered devices and just taking relevant bits such as Neighbour zones and SIP trunks from it.
Does anyone know of a guide specifically for the direction Cisco appear to want us to go, which is Telepresence devices registered to CUCM and the VCS just doing firewall traversal.
Or a guide on the firewall traversal part only and I can tack it on to my notes from the other adapted guides.
My current notes have the following tasks I think I need to do to get this working
- setup partition and CSS on the CUCM for Telepresence calls
- setup SIP trunk on CUCM pointing to Expressway-C (have subnotes on requirments for SIP Trunk Security profile and the SIP Profile)
- SIP route pattern(s) on the CUCM pointing to the SIP trunk
- Enterprise parameters on the CUCM such as Cluster FQDN, Organization Top Level Domain and URI Lookup Policy
- On the VCS-C a neighbour zone pointing to the CUCM
- Search rule to route inbound calls to CUCM neighbour zone
Is this looking correct so far? If so then what else will I need to in relation to traversal zones and VCS-E call routing to get calls in and out the business?
thanks in advance
Tigre

Was checking the logs on the SX10 itself, appears to be reporting the same thing about 503 Service Unavailable, I had the logging on it set to "Extended Logging"
(NB - the address 10.1.99.198 in this case is not the SX10, it is my laptop as I was using the SX10's webgui to remotely control the device and make the call)
Currently discussing this issue with Cisco TAC, will update as and when more info comes
Line 1113: Sep 10 15:24:56.367 a9 appl[1529]: 6097.58 CuilApp   User admin(1001) about to execute command '/Phonebook/Search ContactType: any Limit: 100 Offset: 0 PhonebookType: local SearchString: [email protected]' from 10.1.99.198.
Line 1114: Sep 10 15:24:56.375 a9 appl[1529]: 6097.58 CuilApp   User admin(1001) about to execute command '/CallHistory/Recents DetailLevel: Full Limit: 100 Offset: 0 SearchString: [email protected]' from 10.1.99.198.
Line 1115: Sep 10 15:24:56.384 a9 appl[1529]: 6097.59 CuilApp   User admin(1001) about to execute command '/Phonebook/Search ContactType: any Limit: 100 Offset: 0 PhonebookType: corporate SearchString: [email protected]' from 10.1.99.198.
Line 1117: Sep 10 15:24:58.634 a9 appl[1529]: 6099.84 CuilApp   User admin(1001) about to execute command '/Dial callType: Video number: [email protected]' from 10.1.99.198.
Line 1125: Sep 10 15:24:59.154 a9 appl[1529]: 6100.36 MainEvents I: OutgoingCallInvoked(p=3) remoteURI='sip:[email protected]' localURI='sip:[email protected]' bookingID=''
Line 1164: Sep 10 15:24:59.859 a9 appl[1529]: 6101.07 MC I: CallParticipant: calledUri: sip:[email protected]
Line 1190: Sep 10 15:24:59.890 a9 appl[1529]: 6101.10 SipPacket   INVITE sip:[email protected] SIP/2.0
Line 1196: Sep 10 15:24:59.892 a9 appl[1529]: 6101.10 SipPacket   To: <sip:[email protected]>
Line 1295: Sep 10 15:24:59.960 a9 appl[1529]: 6101.17 SipPacket   To: <sip:[email protected]>
Line 1306: Sep 10 15:24:59.967 a9 appl[1529]: 6101.18 SipPacket   To: <sip:[email protected]>;tag=1393374~8642d04e-70cd-49a5-b73c-5ca5fe21b218-48171693
Line 1313: Sep 10 15:24:59.970 a9 appl[1529]: 6101.18 SipPacket   ACK sip:[email protected] SIP/2.0
Line 1318: Sep 10 15:24:59.972 a9 appl[1529]: 6101.18 SipPacket   To: <sip:[email protected]>;tag=1393374~8642d04e-70cd-49a5-b73c-5ca5fe21b218-48171693
Line 1328: Sep 10 15:24:59.979 a9 appl[1529]: 6101.19 MainEvents I: CallDisconnectRequested(p=3) remoteURI='sip:[email protected]' cause=[normal('') 'LocalDisconnect']
Line 1333: Sep 10 15:24:59.986 a9 appl[1529]: 6101.19 MainEvents I: CallDisconnected(p=3) remoteURI='sip:[email protected]' causeToLocal=[disconnected('Service Unavailable') 'RemoteDisconnect'] causeToRemote=[normal('') 'LocalDisconnect']

Similar Messages

Is WebEx Enabled TelePresence supported with Expressway Core and Edge?

Is WebEx Enabled TelePresence supported with the Expressway Core and Edge instead of using a VCS Control and Expressway? This is one thing I'm not sure of, as the scheduled conferences will have to register to the Expressway Core and wasn't sure if this was possible.

Hi,
It is supported, see the following release notes here:
http://www.cisco.com/c/en/us/td/docs/telepresence/infrastructure/tms/release_note/cmr_hybrid_RNs_14_4.html#pgfId-164481
Expressway-E/C use is also covered in the deployment guide:
http://www.cisco.com/c/dam/en/us/td/docs/telepresence/infrastructure/tms/config_guide/cmr_hybrid_config_guide_tms_14_4.pdf
-Jonathan
Edit - links

CUCM 9.0 and SX20 video call - inter region

Hi Guys,
I am having an issue establishing a inter region video call between 2 SX-20 endpoints.
Call works fine when I move them to same region
I have made the CAC to unlimited for video on the Locations
I have played with the Video Bandwidth in the regions.
I have changed the defaults under the Service Parameters for Inter and Intra Region
I have tried to adjust MAX and MIN under Conference 1 on the SX20s
I have tried changing the default video call bandwidth to both 384 and 768
In every case, Call works fine when both endpoints are in same region and just and audio call when interregion (G711Ulaw) .
For some reason its not presenting the right codec.
Also in CUCM 9.0, I am not able to collect the SDI traces on the endpoints. it says "Trace not found for Service Call Manager, trace type 'sdi' " which is a reported bug in older releases but was fixed. I guess it has returned too ...
Any suggestions ?

Hello Varungulati,
I'm having the same issue, did you manage to solve this problem ?
Thanks,
Nadjia

Cisco BE6k and VCS Core/edge

Dear all,
There is a new Be6k High density in the testing environment.
However, we don't have clear picture on the deploying VCS Core/edge with the CUCM in the BE6k.
Do we install the VCS core and edge in the same BE6k server? After that, the VCS edge assign with a DMZ ip address?Or install other VCS edge from the appliance?
How is configuration between CUCM and VCS? Since I can't any related document from the Cisco.com.
Best Regards,
Ben Lai

1 Either works, you just need to make sure to properly design and configure the underlying network and the ports to which each VM will connect
2 There´s PLENTY of information on that
http://www.cisco.com/c/en/us/support/unified-communications/telepresence-video-communication-server-vcs/tsd-products-support-series-home.html

Help me to choose Right Core switches and Edge switches as per my Spec

Dear All
Please help me to choose Core and Edge switches and all required hard ware and software.
the spec details as per below
Core Switches
1. High performance, highly scalable core switch to provide multi-10GE connectivity to various segments in the network.
2. Switch should have redundant switch fabric and routing engines or management / supervisor modules
3.should have separate control and forwarding planes
4.Each switch should have redundant power supplies in N+N or N+1 fashion
5. Must allow for two spare slots once services, management, processing modules and line cards populated
6. Easy to manage firmware- i.e. single code type enterprise/service provider) or train, and robust operating system
7. Supports for the VRRP, NSR, GRES, BFD, STP, MSTP, RSTP, VSTP, LACP redundancy protocols
8. Hot plugging and removal
9. The switch should have native switching architecture with up to sufficient performance such that the loss of one switching fabric should not lead to degraded performance
10. Switch should support switching at least 400Mpps
11. Switch should be able to support 40 10Gig line rate ports in a fully redundant configuration
12. Chassis that can scale to 700 Gbps
13. The proposed Backbone switch should support, but not be limited to the following Layer 3 features:
Static ip routing
Routing information protocol (RIP) and RIP2
Open shortest path first (OSPF)
IGMP v1, v2 and v3
IGMP Snooping
IP multicast routing protocol
14. The switch should support the following features at a minimum:
Spanning Tree 802.1D, 802.1S, 802.1W
GVRP
802.1x single and multi-supplicant: VLAN and ACL assignment
Dynamic ARP Inspection (DAI), DHCP snooping, IP Source gurard
LLDP, LLDP-MED
802.3X, 802.3ad
Redundant Trunk Group (RTG)
IGMP snooping
Unicast static, OSPF v1/v2, RIP v1/v2
Multicast IGMPv1/v2, PIM
Graceful Route Engine Switchover

I have gone through your document and I am surprised to see MORE information in the document than what you've posted. I am so mildly suspicious about the authenticity of the document and spreadsheet you've attached.
So far, based on this document, the client wants a chassis that can support up to 700 Gbps backplane. The only candidate, other than a full-blown Nexus solution, is the 6807-X.
Next, the document also states dual supervisor card with two spare slots. Good luck trying to get that much empty space on a 6807-X. This means 6509E. You can't use a 6513E because of line-card-to-slot limitation.
If you look under the heading "Edge Switching", the first sentence already makes references to 6800ia switch.
There's also a reference stating that the product should have a 100 Gbps backplane. You can take the 6509E chassis out of the equation.
So you see, I am suspicious about the authenticity of the document. I agree with mali's and devil's recommendation that if you are serious, you would be engaging Cisco SE/AM in your region. There are only three reasons, that I can think of, why you've posted this here. One of them is the intended purpose of this document (and the audience).

Two EX90 devices can make video calls over Internet with No VCS-C and VCS-E

Dear Experts;
I have just started TelePresence and VCS 2 weeks before by going through cisco docs and videos and I had taken a risk of implementing the infrastructure elements.
We are now implementing Cisco Tele presence with VCS-C, VCS-E TMS,TCS,MCU and End points with Jabber in One setup.
and in another setup CUCM 10.5,UCCX 10.5 IM&P,Jabber with some 10 agents.
Now the question is In our same building in 2nd floor we have one EX90 and in 5th Floor one EX90 and over LAN we can make video calls using IP address.
In the same way is it possible to make a video call between 2 EX90 devices present in different location in the same city over Internet without the involvement of VCS-C and VCS-E.
Appreciate your valuable reply.
Regards
Debashis

The simple answer to that is NO! Where is the EX90 registered to at the moment? Is it on the VCS? or CUCM

CUCM-VCS Integration VCS B2BUA Encryption Call Failures

All,
I have the following scenario:
CUCM 9.1.2SU1
VCS X8.1.1
MX300 endpoints (CUCM registered)
We are not running in mixed mode on CUCM
We want media streams with external call parties to be encrypted. We do have TLS end-to-end but I don't believe we can support SRTP to the MX300s registered to UCM w/o provisioning mixed mode (based on Cisco docs). So, we are attempting to use Media encryption policy on the VCS. Specifically, we set one of the traversal client zone to use "Best effort". This works for most calls but we have seen a couple of calls fail.
From end user perspective, failures manifest as a call that gets connected and is immediately torn down.
On the VCS, we will see the following when looking at the call history:
The B2BUA Encryption component is disconnected after ~3 seconds. The disconnect reason is: B2BUA disconnected call on the ingress saying "mismatched transport type in answer".
Based on context clues, this points to TLS negotiation. The thing is, if I set the media policy back to "auto" then the call connects fine and the transport is TLS. At least, it reports TLS on my VCS-C and VCS-E.
Any pointers that someone is willing to toss my way?
Thanks in advance,
Bill (@ucguerrilla)

Won't help but I have a very similar but slightly different scenario with:
CUCM 9.1
VCS 8.2.2
Jabber 10 or CUCM registered TC endpoint
As for settings:
CUCM-VCS SIP trunk is TCP not encrypted (never got it to work following the doc step by step....)
VCS-C to VCS-E is TLS as setup on the doc.
On the VCS-C, the DNSZone Media Encrytion mode is set to "Auto"
Some SIP calls work perfectly (i.e. the Cisco test endpoints) but some users have issues. Dialing partners' cloud service video-conference, the call connects and gets dropped immediately. I created myself a trial account on that service to test and can reproduce it all the time. I can see the call coming in my cloud service client and when I accept it it just drops.
On the VCS-C,
I see a SIP 200 OK
an then a call component status=disconnected type=B2BUA
State
Inactive
Start time
2014-11-11 16:51:22
Duration
5 seconds
Disconnect reason summary
disconnected
Disconnect reason details
B2BUA disconnected call on the Egress saying "Received 'Request Timeout' to mid-dialog request"
But on the VCS-E in the call history, I only see and "408 request timeout".
When I call my Jabber account from that service it works well. But in that case the second call component with type B2BUA shows:
State
Inactive
Start time
2014-11-11 17:14:02
Duration
40 seconds
Disconnect reason summary
BYE
Disconnect reason details
Egress disconnected call
Tag
3d14cee5-01ad-4468-9e3b-e0925dde15d4
Box call serial number
1bc2473f-2a09-4dea-8ffd-a7e88a3ef05b
Have also no clue of what is happening

Unable to place call on calls on hold - SIP Trunk from CUCM to CUBE and from CUBE to ISTP

Hi Cisco Community,
I have a SIP Trunk setup between the CUCM and CUBE and another SIP Dial Peers from the CUBE to the ITSP. All incoming/outgoing calls, DTMF-Relay works well except one thing which is the ability to hold the call.
On the SIP Trunk from the CUCM to the CUBE, I did not select “MTP” because when I do so, I am forced to select my preferred MTP codec which when selected G.729/G.729a, all my outgoing calls goes out using G.729r8. This codec works well for most of the calls until the ITSP replies back with G.729br8. When this condition occur, my call simply fails (this is very intermittent and only some random numbers).
That said, I have some issues with DTMF Relay when I select MTP on the SIP Trunk. DTMF Relay only works if the call is G.729r8 all the way from the CUCM to the ITSP. If the ITSP replies back with G.729br8, the call might established but will simply be “voice-only”.
The current setup is no MTP is selected and everything is working perfectly. I am happy with that until I place a call on hold, which when I do so, the call immediately terminate. Could you please help me understand why?
I have all media resources configured such as G.729r8 MTP, G.729br8 MTP, G.711u MTP, Transcoding with all codecs, etc. All MRG and MRGL are configured on all devices and SIP Trunks.
Below is an example of a call that is connected with the current setup:
Note:
IP: 10.18.81.2 (CUBE)
IP: 10.18.81.11 (CUCM SUB)
IP: 10.111.111.254 (ITSP SBC)
PM-HO-VG-01#
PM-HO-VG-01#
Nov 30 11:44:29.938: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 10.18.81.11:5060;branch=z9hG4bK2e72063a5aba5d
From: "Bianca Africa" <sip:[email protected]>;tag=9082578~cdf4c5a6-dd2b-4c71-bca0-b262ad997720-44517224
To: <sip:[email protected]>
Date: Sun, 30 Nov 2014 11:44:29 GMT
Call-ID: [email protected]
Supported: timer,resource-priority,replaces
Min-SE: 1800
User-Agent: Cisco-CUCM9.1
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
CSeq: 101 INVITE
Expires: 180
Allow-Events: presence, kpml
Supported: X-cisco-srtp-fallback,X-cisco-original-called
Call-Info: <sip:10.18.81.11:5060>;method="NOTIFY;Event=telephone-event;Duration=500"
Cisco-Guid: 1020645888-0000065536-0000124117-0189862410
Session-Expires: 1800
Contact: <sip:[email protected]:5060>
Max-Forwards: 70
Content-Length: 0
Nov 30 11:44:29.942: //64510/3CD5D2000001/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 10.18.81.11:5060;branch=z9hG4bK2e72063a5aba5d
From: "Bianca Africa" <sip:[email protected]>;tag=9082578~cdf4c5a6-dd2b-4c71-bca0-b262ad997720-44517224
To: <sip:[email protected]>
Date: Sun, 30 Nov 2014 11:44:29 GMT
Call-ID: [email protected]
CSeq: 101 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-15.2.4.M5
Content-Length: 0
Nov 30 11:44:29.946: //64511/3CD5D2000001/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 10.18.81.2:5060;branch=z9hG4bK3EC72218
From: "Bianca Africa" <sip:[email protected]>;tag=3C364D44-9E2
To: <sip:[email protected]>
Date: Sun, 30 Nov 2014 11:44:29 GMT
Call-ID: [email protected]
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Min-SE: 1800
Cisco-Guid: 1020645888-0000065536-0000124117-0189862410
User-Agent: Cisco-SIPGateway/IOS-15.2.4.M5
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Timestamp: 1417347869
Contact: <sip:[email protected]:5060>
Call-Info: <sip:10.18.81.2:5060>;method="NOTIFY;Event=telephone-event;Duration=2000"
Expires: 180
Allow-Events: telephone-event
Max-Forwards: 69
Session-Expires: 1800
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 301
v=0
o=CiscoSystemsSIP-GW-UserAgent 7676 6958 IN IP4 10.18.81.2
s=SIP Call
c=I
PM-HO-VG-01#N IP4 10.18.81.2
t=0 0
m=audio 22256 RTP/AVP 18 0 8 101
c=IN IP4 10.18.81.2
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=yes
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
Nov 30 11:44:29.950: //64511/3CD5D2000001/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 10.18.81.2:5060;branch=z9hG4bK3EC72218
From: "Bianca Africa" <sip:[email protected]>;tag=3C364D44-9E2
To: <sip:[email protected]>
Call-ID: [email protected]
CSeq: 101 INVITE
Timestamp: 1417347869
Nov 30 11:44:30.658: //64511/3CD5D2000001/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 180 Session Progress
Via: SIP/2.0/UDP 10.18.81.2:5060;branch=z9hG4bK3EC72218
From: "Bianca Africa" <sip:[email protected]>;tag=3C364D44-9E2
To: <sip:[email protected]>;tag=71913148-1417348035284
Call-ID: [email protected]
CSeq: 101 INVITE
Timestamp: 1417347869
Supported:
Contact: <sip:[email protected]:5060;transport=udp>
Session: Media
Allow: ACK,BYE,CANCEL,INFO,INVITE,OPTIONS,PRACK,REFER,NOTIFY,UPDATE
X-BroadWorks-Correlation-Info: bbf94839-a234-4237-95e6-a7037322f0f4
Content-Type: application/sdp
Content-Length: 355
v=0
o=BroadWorks 316169737 1 IN IP4 10.111.111.254
s=-
c=IN IP4 10.111.111.254
t=0 0
m=audio 20074 RTP/AVP 18 101 100
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=rtpmap:100 X-NSE/8000
a=fmtp:100 200-202
a=X-sqn:0
a=X-cap: 1 audio RTP/AVP 100
a=X-cpar: a=rtpmap:100 X-NSE/8000
a=X-cpar: a=fmtp:100 200-202
a=X-cap: 2 image udptl t38
Nov 30 11:44:30.662: //64510/3CD5D2000001/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 183 Session Progress
Via: SIP/2.0/UDP 10.18.81.11:5060;branch=z9hG4bK2e72063a5aba5d
From: "Bianca Africa" <sip:[email protected]>;tag=9082578~cdf4c5a6-dd2b-4c71-bca0-b262ad997720-44517224
To: <sip:[email protected]>;tag=3C365010-1E42
Date: Sun, 30 Nov 2014 11:44:29 GMT
Call-ID: [email protected]
CSeq: 101 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Contact: <sip:[email protected]:5060>
Supported: sdp-anat
Server: Cisco-SIPGateway/IOS-15.2.4.M5
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 289
v=0
o=CiscoSystemsSIP-GW-UserAgent 7965 2747 IN IP4 10.18.81.2
s=SIP Call
c=IN IP4 10.18.81.2
t=0 0
m=audio 22350 RTP/AVP 18 101 19
c=IN IP4 10.18.81.2
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=yes
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=rtpmap:19 CN/8000
a=ptime:20
Nov 30 11:44:31.226: //64511/3CD5D2000001/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 180 Session Progress
Via: SIP/2.0/UDP 10.18.81.2:5060;branch=z9hG4bK3EC72218
From: "Bianca Africa" <sip:[email protected]>;tag=3C364D44-9E2
To: <sip:[email protected]>;tag=71913148-1417348035284
Call-ID: [email protected]
CSeq: 101 INVITE
Timestamp: 1417347869
Supported:
Contact: <sip:[email protected]:5060;transport=udp>
Session: Media
Allow: ACK,BYE,CANCEL,INFO,INVITE,OPTIONS,PRACK,REFER,NOTIFY,UPDATE
X-BroadWorks-Correlation-Info: bbf9
PM-HO-VG-01#4839-a234-4237-95e6-a7037322f0f4
Content-Type: application/sdp
Content-Length: 355
v=0
o=BroadWorks 316169737 1 IN IP4 10.111.111.254
s=-
c=IN IP4 10.111.111.254
t=0 0
m=audio 20074 RTP/AVP 18 101 100
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=rtpmap:100 X-NSE/8000
a=fmtp:100 200-202
a=X-sqn:0
a=X-cap: 1 audio RTP/AVP 100
a=X-cpar: a=rtpmap:100 X-NSE/8000
a=X-cpar: a=fmtp:100 200-202
a=X-cap: 2 image udptl t38
Nov 30 11:44:31.630: //64511/3CD5D2000001/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.18.81.2:5060;branch=z9hG4bK3EC72218
From: "Bianca Africa" <sip:[email protected]>;tag=3C364D44-9E2
To: <sip:[email protected]>;tag=71913148-1417348035284
Call-ID: [email protected]
CSeq: 101 INVITE
Timestamp: 1417347869
Supported:
Contact: <sip:[email protected]:5060;transport=udp>
Allow: ACK,BYE,CANCEL,INFO,INVITE,OPTIONS,PRACK,REFER,NOTIFY,UPDATE
Accept: application/media_control+xml,application/sdp,application/xml
X-BroadWorks-Correlation-Info: bbf94839-a234-4237-95e6-a7037322f0f4
Content-Type: application/sdp
Content-Length: 355
v=0
o=BroadWorks 316169737 1 IN IP4 10.111.111.254
s=-
c=IN IP4 10.111.111.254
t=0 0
m=audio 20074 RTP/AVP 18 101 100
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=rtpmap:100 X-NSE/8000
a=fmtp:100 200-202
a=X-sqn:0
a=X-cap: 1 audio RTP/AVP 100
a=X-cpar: a=rtpmap:100 X-NSE/8000
a=X-cpar: a=fmtp:100 200-202
a=X-cap: 2 image udptl t38
Nov 30 11:44:31.630: //64511/3CD5D2000001/SIP/Call/sipSPICallInfo:
The Call Setup Information is:
Call Control Block (CCB) : 0x0x3D7B1458
State of The Call : STATE_ACTIVE
TCP Sockets Used : NO
Calling Number : 27218091323
Called Number : 0862000000
Source IP Address (Sig ): 10.18.81.2
Destn SIP Req Addr:Port : 10.111.111.254:5060
Destn SIP Resp Addr:Port : 10.111.111.254:5060
Destination Name : 10.111.111.254
Nov 30 11:44:31.630: //64511/3CD5D2000001/SIP/Call/sipSPIMediaCallInfo:
Number of Media Streams: 1
Media Stream : 1
Negotiated Codec : g729br8
Negotiated Codec Bytes : 20
Nego. Codec payload : 18 (tx), 18 (rx)
Negotiated Dtmf-relay : 6
Dtmf-relay Payload : 101 (tx), 101 (rx)
Source IP Address (Media): 10.18.81.2
Source IP Port (Media): 22256
Destn IP Address (Media): 10.111.111.254
Destn IP Port (Media): 20074
Orig Destn IP Address:Port (Media): [ - ]:0
Nov 30 11:44:31.630: //64511/3CD5D2000001/SIP/Msg/ccsipDisplayMsg:
Sent:
ACK sip:[email protected]:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 10.18.81.2:5060;branch=z9hG4bK3EC81D00
From: "Bianca Africa" <sip:[email protected]>;tag=3C364D44-9E2
To: <sip:[email protected]>;tag=71913148-1417348035284
Date: Sun, 30 Nov 2014 11:44:29 GMT
Call-ID: [email protected]
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: telephone-event
Content-Length: 0
Nov 30 11:44:31.634: //64510/3CD5D2000001/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.18.81.11:5060;branch=z9hG4bK2e72063a5aba5d
From: "Bianca Africa" <sip:[email protected]>;tag=9082578~cdf4c5a6-dd2b-4c71-bca0-b262ad997720-44517224
To: <sip:[email protected]>;tag=3C365010-1E42
Date: Sun, 30 Nov 2014 11:44:29 GMT
Call-ID: [email protected]
CSeq: 101 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Contact: <sip:[email protected]:5060>
Supported: replaces
Supported: sdp-anat
Server: Cisco-SIPGateway/IOS-15.2.4.M5
Supported: timer
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 289
v=0
o=CiscoSystemsSIP-GW-UserAgent 7965 2747 IN IP4 10.18.81.2
s=SIP Call
c=IN IP4 10.18.81.2
t=0 0
m=audio 22350 RTP/AVP 18 101 19
c=IN IP4 10.18.81.2
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=yes
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=rtpmap:19 CN/8000
a=ptime:20
Nov 30 11:44:31.726: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 10.18.81.11:5060;branch=z9hG4bK2e72075e3a02c1
From: "Bianca Africa" <sip:[email protected]>;tag=9082578~cdf4c5a6-dd2b-4c71-bca0-b262ad997720-44517224
To: <sip:[email protected]>;tag=3C365010-1E42
Date: Sun, 30 Nov 2014 11:44:29 GMT
Call-ID: [email protected]
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: presence, kpml
Content-Type: application/sdp
Content-Length: 236
v=0
o=CiscoSystemsCCM-SIP 9082578 1 IN IP4 10.18.81.11
s=SIP Call
c=IN IP4 10.18.80.40
b=TIAS:8000
b=AS:8
t=0 0
m=audio 21928 RTP/AVP 18 101
a=rtpmap:18 G729/8000
a=ptime:20
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
Nov 30 11:44:31.730: //64510/3CD5D2000001/SIP/Call/sipSPICallInfo:
The Call Setup Information is:
Call Control Block (CCB) : 0x0x3D816D70
State of The Call : STATE_ACTIVE
TCP Sockets Used : NO
Calling Number : 0218091323
Called Number : 0862000000
Source IP Address (Sig ): 10.18.81.2
Destn SIP Req Addr:Port : 10.18.81.11:5060
Destn SIP Resp Addr:Port : 10.18.81.11:5060
Destination Name : 10.18.81.11
Nov 30 11:44:31.730: //64510/3CD5D2000001/SIP/Call/sipSPIMediaCallInfo:
Number of Media Streams: 1
Media Stream : 1
Negotiated Codec : g729br8
Negotiated Codec Bytes : 20
Nego. Codec payload : 18 (tx), 18 (rx)
Negotiated Dtmf-relay : 6
Dtmf-relay Payload : 101 (tx), 101 (rx)
Source IP Address (Media): 10.18.81.2
Source IP Port (Media): 22350
Destn IP Address (Media): 10.18.80.40
Destn IP Port (Media): 21928
Orig Destn IP Address:Port (Media): [ - ]:0
Nov 30 11:44:31.730: //64510/3CD5D2000001/SIP/Call/sipSPICallInfo:
The Call Setup Information is:
Call Control Block (CCB) : 0x0x3D816D70
State of The Call : STATE_ACTIVE
TCP Sockets Used : NO
Calling Number : 0218091323
Called Number : 0862000000
Source IP Address (Sig ): 10.18.81.2
Destn SIP Req Addr:Port : 10.18.81.11:5060
Destn SIP Resp Addr:Port : 10.18.81.11:5060
Destination Name : 10.18.81.11
PM-HO-VG-01#
Nov 30 11:44:31.730: //64510/3CD5D2000001/SIP/Call/sipSPIMediaCallInfo:
Number of Media Streams: 1
Media Stream : 1
Negotiated Codec : g729br8
Negotiated Codec Bytes : 20
Nego. Codec payload : 18 (tx), 18 (rx)
Negotiated Dtmf-relay : 6
Dtmf-relay Payload : 101 (tx), 101 (rx)
Source IP Address (Media): 10.18.81.2
Source IP Port (Media): 22350
Destn IP Address (Media): 10.18.80.40
Destn IP Port (Media): 21928
Orig Destn IP Address:Port (Media): [ - ]:0
PM-HO-VG-01#sh sip
PM-HO-VG-01#sh sip-ua call
PM-HO-VG-01#sh sip-ua calls
Total SIP call legs:2, User Agent Client:1, User Agent Server:1
SIP UAC CALL INFO
Call 1
SIP Call ID : [email protected]
State of the call : STATE_ACTIVE (7)
Substate of the call : SUBSTATE_NONE (0)
Calling Number : 27218091323
Called Number : 0862000000
Bit Flags : 0xC04018 0x10000100 0x0
CC Call ID : 64511
Source IP Address (Sig ): 10.18.81.2
Destn SIP Req Addr:Port : [10.111.111.254]:5060
Destn SIP Resp Addr:Port: [10.111.111.254]:5060
Destination Name : 10.111.111.254
Number of Media Streams : 1
Number of Active Streams: 1
RTP Fork Object : 0x0
Media Mode : flow-through
Media Stream 1
State of the stream : STREAM_ACTIVE
Stream Call ID : 64511
Stream Type : voice+dtmf (0)
Stream Media Addr Type : 1
Negotiated Codec : g729br8 (20 bytes)
Codec Payload Type : 18
Negotiated Dtmf-relay : rtp-nte
Dtmf-relay Payload Type : 101
QoS ID : -1
Local QoS Strength : BestEffort
Negotiated QoS Strength : BestEffort
Negotiated QoS Direction : None
Local QoS Status : None
Media Source IP Addr:Port: [10.18.81.2]:22256
Media Dest IP Addr:Port : [10.111.111.254]:20074
Options-Ping ENABLED:NO ACTIVE:NO
Number of SIP User Agent Client(UAC) calls: 1
SIP UAS CALL INFO
Call 1
SIP Call ID : [email protected]
State of the call : STATE_ACTIVE (7)
Substate of the call : SUBSTATE_NONE (0)
Calling Number : 0218091323
Called Number : 0862000000
Bit Flags : 0xC0401E 0x10000100 0x80004
CC Call ID : 64510
Source IP Address (Sig ): 10.18.81.2
Destn SIP Req Addr:Port : [10.18.81.11]:5060
Destn SIP Resp Addr:Port: [10.18.81.11]:5060
Destination Name : 10.18.81.11
Number of Media Streams : 1
Number of Active Streams: 1
RTP Fork Object : 0x0
Media Mode : flow-through
Media Stream 1
State of the stream : STREAM_ACTIVE
Stream Call ID : 64510
Stream Type : voice+dtmf (1)
Stream Media Addr Type : 1
Negotiated Codec : g729br8 (20 bytes)
Codec Payload Type : 18
Negotiated Dtmf-relay : rtp-nte
Dtmf-relay Payload Type : 101
QoS ID : -1
Local QoS Strength : BestEffort
Negotiated QoS Strength : BestEffort
Negotiated QoS Direction : None
Local QoS Status : None
Media Source IP Addr:Port: [10.18.81.2]:22350
Media Dest IP Addr:Port : [10.18.80.40]:21928
Options-Ping ENABLED:NO ACTIVE:NO
Number of SIP User Agent Server(UAS) calls: 1
PM-HO-VG-01#
PM-HO-VG-01#
PM-HO-VG-01#
As you can see, the call is connected and everything is working perfectly. When I press the hold button, here is what I get:
NOTE: I have # debug ccsip messages and #debug ccsip calls (running)
PM-HO-VG-01#
PM-HO-VG-01#
Nov 30 11:44:49.210: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 10.18.81.11:5060;branch=z9hG4bK2e720852ab8b92
From: "Bianca Africa" <sip:[email protected]>;tag=9082578~cdf4c5a6-dd2b-4c71-bca0-b262ad997720-44517224
To: <sip:[email protected]>;tag=3C365010-1E42
Date: Sun, 30 Nov 2014 11:44:49 GMT
Call-ID: [email protected]
Supported: timer,resource-priority,replaces
Min-SE: 1800
User-Agent: Cisco-CUCM9.1
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
CSeq: 102 INVITE
Max-Forwards: 70
Expires: 180
Allow-Events: presence
Supported: X-cisco-srtp-fallback
Supported: Geolocation
Contact: <sip:[email protected]:5060>
Content-Type: application/sdp
Content-Length: 244
v=0
o=CiscoSystemsCCM-SIP 9082578 2 IN IP4 10.18.81.11
s=SIP Call
c=IN IP4 0.0.0.0
b=TIAS:8000
b=AS:8
t=0 0
m=audio 21928 RTP/AVP 18 101
a=rtpmap:18 G729/8000
a=ptime:20
a=inactive
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
Nov 30 11:44:49.218: //64510/3CD5D2000001/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 10.18.81.11:5060;branch=z9hG4bK2e720852ab8b92
From: "Bianca Africa" <sip:[email protected]>;tag=9082578~cdf4c5a6-dd2b-4c71-bca0-b262ad997720-44517224
To: <sip:[email protected]>;tag=3C365010-1E42
Date: Sun, 30 Nov 2014 11:44:49 GMT
Call-ID: [email protected]
CSeq: 102 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-15.2.4.M5
Content-Length: 0
Nov 30 11:44:49.218: //64511/3CD5D2000001/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:[email protected]:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 10.18.81.2:5060;branch=z9hG4bK3EC9241
From: "Bianca Africa" <sip:[email protected]>;tag=3C364D44-9E2
To: <sip:[email protected]>;tag=71913148-1417348035284
Date: Sun, 30 Nov 2014 11:44:49 GMT
Call-ID: [email protected]
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Min-SE: 1800
Cisco-Guid: 1020645888-0000065536-0000124117-0189862410
User-Agent: Cisco-SIPGateway/IOS-15.2.4.M5
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 102 INVITE
Max-Forwards: 70
Timestamp: 1417347889
Contact: <sip:[email protected]:5060>
Call-Info: <sip:10.18.81.2:5060>;method="NOTIFY;Event=telephone-event;Duration=2000"
Expires: 180
Allow-Events: telephone-event
Content-Type: application/sdp
Content-Length: 271
v=0
o=CiscoSystemsSIP-GW-UserAgent 7676 6959 IN IP4 10.18.81.2
s=SIP Call
c=IN IP4 0.0.0.0
t=0 0
m=audio 22256 RTP/AVP 18 101
c=IN IP4 0.0.0.0
a=inactive
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=yes
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20
Nov 30 11:44:49.278: //64511/3CD5D2000001/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.18.81.2:5060;branch=z9hG4bK3EC9241
From: "Bianca Africa" <sip:[email protected]>;tag=3C364D44-9E2
To: <sip:[email protected]>;tag=71913148-1417348035284
Call-ID: [email protected]
CSeq: 102 INVITE
Timestamp: 1417347889
Allow: ACK,BYE,CANCEL,INFO,INVITE,OPTIONS,PRACK,REFER,NOTIFY,UPDATE
Supported:
Accept: application/media_control+xml,application/sdp,application/xml
Contact: <sip:[email protected]:5060;transport=udp>
X-BroadWorks-Correlation-Info: bbf94839-a234-4237-95e6-a7037322f0f4
Content-Type: application/sdp
Content-Length: 360
v=0
o=BroadWorks 316169737 2 IN IP4 10.111.111.254
s=-
c=IN IP4 0.0.0.0
t=0 0
m=audio 20074 RTP/AVP 18 101 100
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=rtpmap:100 X-NSE/8000
a=fmtp:100 200-202
a=X-sqn:0
a=X-cap: 1 audio RTP/AVP 100
a=X-cpar: a=rtpmap:100 X-NSE/8000
a=X-cpar: a=fmtp:100 200-202
a=X-cap: 2 image udptl t38
a=inactive
Nov 30 11:44:49.278: //64511/3CD5D2000001/SIP/Call/sipSPICallInfo:
The Call Setup Information is:
Call Control Block (CCB) : 0x0x3D7B1458
State of The Call : STATE_ACTIVE
TCP Sockets Used : NO
Calling Number : 27218091323
Called Number : 0862000000
Source IP Address (Sig ): 10.18.81.2
Destn SIP Req Addr:Port : 10.111.111.254:5060
Destn SIP Resp Addr:Port : 10.111.111.254:5060
Destination Name : 10.111.111.254
Nov 30 11:44:49.278: //64511/3CD5D2000001/SIP/Call/sipSPIMediaCallInfo:
Number of Media Streams: 1
Media Stream : 1
Negotiated Codec : g729br8
Negotiated Codec Bytes : 20
Nego. Codec payload : 18 (tx), 18 (rx)
Negotiated Dtmf-relay : 6
Dtmf-relay Payload : 101 (tx), 101 (rx)
Source IP Address (Media): 10.18.81.2
Source IP Port (Media): 22256
Destn IP Address (Media): 0.0.0.0
Destn IP Port (Media): 20074
Orig Destn IP Address:Port (Media): [ - ]:0
Nov 30 11:44:49.282: //64511/3CD5D2000001/SIP/Msg/ccsipDisplayMsg:
Sent:
ACK sip:[email protected]:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 10.18.81.2:5060;branch=z9hG4bK3ECA2633
From: "Bianca Africa" <sip:[email protected]>;tag=3C364D44-9E2
To: <sip:[email protected]>;tag=71913148-1417348035284
Date: Sun, 30 Nov 2014 11:44:49 GMT
Call-ID: [email protected]
Max-Forwards: 70
CSeq: 102 ACK
Allow-Events: telephone-event
Content-Length: 0
Nov 30 11:44:49.282: //64510/3CD5D2000001/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.18.81.11:5060;branch=z9hG4bK2e720852ab8b92
From: "Bianca Africa" <sip:[email protected]>;tag=9082578~cdf4c5a6-dd2b-4c71-bca0-b262ad997720-44517224
To: <sip:[email protected]>;tag=3C365010-1E42
Date: Sun, 30 Nov 2014 11:44:49 GMT
Call-ID: [email protected]
CSeq: 102 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Contact: <sip:[email protected]:5060>
Supported: replaces
Supported: sdp-anat
Server: Cisco-SIPGateway/IOS-15.2.4.M5
Supported: timer
Content-Type: application/sdp
Content-Length: 271
v=0
o=CiscoSystemsSIP-GW-UserAgent 7965 2748 IN IP4 10.18.81.2
s=SIP Call
c=IN IP4 0.0.0.0
t=0 0
m=audio 22350 RTP/AVP 18 101
c=IN IP4 0.0.0.0
a=inactive
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=yes
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20
Nov 30 11:44:49.282: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 10.18.81.11:5060;branch=z9hG4bK2e72094953dfea
From: "Bianca Africa" <sip:[email protected]>;tag=9082578~cdf4c5a6-dd2b-4c71-bca0-b262ad997720-44517224
To: <sip:[email protected]>;tag=3C365010-1E42
Date: Sun, 30 Nov 2014 11:44:49 GMT
Call-ID: [email protected]
Max-Forwards: 70
CSeq: 102 ACK
Allow-Events: presence
Content-Length: 0
Nov 30 11:44:49.290: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 10.18.81.11:5060;branch=z9hG4bK2e720a6918040f
From: "Bianca Africa" <sip:[email protected]>;tag=9082578~cdf4c5a6-dd2b-4c71-bca0-b262ad997720-44517224
To: <sip:[email protected]>;tag=3C365010-1E42
Date: Sun, 30 Nov 2014 11:44:49 GMT
Call-ID: [email protected]
Supported: timer,resource-priority,replaces
Min-SE: 1800
User-Agent: Cisco-CUCM9.1
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
CSeq: 103 INVITE
Max-Forwards: 70
Expires: 180
Allow-Events: presence
Supported: X-cisco-srtp-fallback
Supported: Geolocation
Contact: <sip:[email protected]:5060>
Content-Length: 0
Nov 30 11:44:49.294: //64510/3CD5D2000001/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 10.18.81.11:5060;branch=z9hG4bK2e720a6918040f
From: "Bianca Africa" <sip:[email protected]>;tag=9082578~cdf4c5a6-dd2b-4c71-bca0-b262ad997720-44517224
To: <sip:[email protected]>;tag=3C365010-1E42
Date: Sun, 30 Nov 2014 11:44:49 GMT
Call-ID: [email protected]
CSeq: 103 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-15.2.4.M5
Content-Length: 0
Nov 30 11:44:49.294: //64511/3CD5D2000001/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:[email protected]:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 10.18.81.2:5060;branch=z9hG4bK3ECB16F3
From: "Bianca Africa" <sip:[email protected]>;tag=3C364D44-9E2
To: <sip:[email protected]>;tag=71913148-1417348035284
Date: Sun, 30 Nov 2014 11:44:49 GMT
Call-ID: [email protected]
Supported: timer,resource-priority,replaces,sdp-anat
Min-SE: 1800
Cisco-Guid: 1020645888-0000065536-0000124117-0189862410
User-Agent: Cisco-SIPGateway/IOS-15.2.4.M5
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 103 INVITE
Max-Forwards: 70
Timestamp: 1417347889
Contact: <sip:[email protected]:5060>
Expires: 180
Allow-Events: telephone-event
Content-Length: 0
Nov 30 11:44:49.338: //64511/3CD5D2000001/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.18.81.2:5060;branch=z9hG4bK3ECB16F3
From: "Bianca Africa" <sip:[email protected]>;tag=3C364D44-9E2
To: <sip:[email protected]>;tag=71913148-1417348035284
Call-ID: [email protected]
CSeq: 103 INVITE
Timestamp: 1417347889
Allow: ACK,BYE,CANCEL,INFO,INVITE,OPTIONS,PRACK,REFER,NOTIFY,UPDATE
Supported:
Accept: application/media_control+xml,application/sdp,application/xml
Contact: <sip:[email protected]:5060;transport=udp>
Content-Type: application/sdp
Content-Length: 306
v=0
o=BroadWorks 316169737 3 IN IP4 10.111.111.254
s=-
c=IN IP4 10.111.111.254
t=0 0
m=audio 20074 RTP/AVP 18 101
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=X-sqn:0
a=X-cap: 1 audio RTP/AVP 100
a=X-cpar: a=rtpmap:100 X-NSE/8000
a=X-cpar: a=fmtp:100 200-202
a=X-cap: 2 image udptl t38
Nov 30 11:44:49.342: //64510/3CD5D2000001/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 2
PM-HO-VG-01#00 OK
Via: SIP/2.0/UDP 10.18.81.11:5060;branch=z9hG4bK2e720a6918040f
From: "Bianca Africa" <sip:[email protected]>;tag=9082578~cdf4c5a6-dd2b-4c71-bca0-b262ad997720-44517224
To: <sip:[email protected]>;tag=3C365010-1E42
Date: Sun, 30 Nov 2014 11:44:49 GMT
Call-ID: [email protected]
CSeq: 103 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Contact: <sip:[email protected]:5060>
Supported: replaces
Supported: sdp-anat
Server: Cisco-SIPGateway/IOS-15.2.4.M5
Supported: timer
Content-Type: application/sdp
Content-Length: 289
v=0
o=CiscoSystemsSIP-GW-UserAgent 7965 2749 IN IP4 10.18.81.2
s=SIP Call
c=IN IP4 10.18.81.2
t=0 0
m=audio 22350 RTP/AVP 18 101 19
c=IN IP4 10.18.81.2
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=yes
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=rtpmap:19 CN/8000
a=ptime:20
Nov 30 11:44:49.350: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 10.18.81.11:5060;branch=z9hG4bK2e720b594cd517
From: "Bianca Africa" <sip:[email protected]>;tag=9082578~cdf4c5a6-dd2b-4c71-bca0-b262ad997720-44517224
To: <sip:[email protected]>;tag=3C365010-1E42
Date: Sun, 30 Nov 2014 11:44:49 GMT
Call-ID: [email protected]
Max-Forwards: 70
CSeq: 103 ACK
Allow-Events: presence
Content-Type: application/sdp
Content-Length: 213
v=0
o=CiscoSystemsCCM-SIP 9082578 3 IN IP4 10.18.81.11
s=SIP Call
c=IN IP4 10.18.81.10
t=0 0
m=audio 4000 RTP/AVP 18
a=X-cisco-media:umoh
a=rtpmap:18 G729/8000
a=ptime:20
a=fmtp:18 annexb=no
a=sendonly
Nov 30 11:44:49.354: //64510/3CD5D2000001/SIP/Msg/ccsipDisplayMsg:
Sent:
BYE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 10.18.81.2:5060;branch=z9hG4bK3ECC55
From: <sip:[email protected]>;tag=3C365010-1E42
To: "Bianca Africa" <sip:[email protected]>;tag=9082578~cdf4c5a6-dd2b-4c71-bca0-b262ad997720-44517224
Date: Sun, 30 Nov 2014 11:44:49 GMT
Call-ID: [email protected]
User-Agent: Cisco-SIPGateway/IOS-15.2.4.M5
Max-Forwards: 70
Timestamp: 1417347889
CSeq: 101 BYE
Reason: Q.850;cause=86
P-RTP-Stat: PS=874,OS=17480,PR=872,OR=17440,PL=0,JI=0,LA=0,DU=17
Content-Length: 0
Nov 30 11:44:49.354: //64511/3CD5D2000001/SIP/Msg/ccsipDisplayMsg:
Sent:
BYE sip:[email protected]:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 10.18.81.2:5060;branch=z9hG4bK3ECD1ECD
From: "Bianca Africa" <sip:[email protected]>;tag=3C364D44-9E2
To: <sip:[email protected]>;tag=71913148-1417348035284
Date: Sun, 30 Nov 2014 11:44:49 GMT
Call-ID: [email protected]
User-Agent: Cisco-SIPGateway/IOS-15.2.4.M5
Max-Forwards: 70
Timestamp: 1417347889
CSeq: 104 BYE
Reason: Q.850;cause=65
P-RTP-Stat: PS=872,OS=17440,PR=952,OR=19040,PL=0,JI=0,LA=0,DU=17
Content-Length: 0
Nov 30 11:44:49.374: //64511/3CD5D2000001/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 Race Condition
Via: SIP/2.0/UDP 10.18.81.2:5060;branch=z9hG4bK3ECD1ECD
From: "Bianca Africa" <sip:[email protected]>;tag=3C364D44-9E2
To: <sip:[email protected]>;tag=71913148-1417348035284
Call-ID: [email protected]
Timestamp: 1417347889
CSeq: 104 BYE
Content-Length: 0
Nov 30 11:44:49.374: //64511/3CD5D2000001/SIP/Call/sipSPICallInfo:
The Call Setup Information is:
Call Control Block (CCB) : 0x0x3D7B1458
State of The Call : STATE_DEAD
TCP Sockets Used : NO
Calling Number : 27218091323
Called Number : 0862000000
Source IP Address (Sig ): 10.18.81.2
Destn SIP Req Addr:Port : 10.111.111.254:5060
Destn SIP Resp Addr:Port : 10.111.111.254:5060
Destination Name : 10.111.111.254
Nov 30 11:44:49.374: //64511/3CD5D2000001/SIP/Call/sipSPIMediaCallInfo:
Number of Media Streams: 1
Media Stream : 1
Negotiated Codec : g729br8
Negotiated Codec Bytes : 20
Nego. Codec payload : 18 (tx), 18 (rx)
Negotiated Dtmf-relay : 6
Dtmf-relay Payload : 101 (tx), 101 (rx)
Source IP Address (Media): 10.18.81.2
Source IP Port (Media): 22256
Destn IP Address (Media): 10.111.111.254
Destn IP Port (Media): 20074
Orig Destn IP Address:Port (Media): [ - ]:0
Nov 30 11:44:49.374: //64511/3CD5D2000001/SIP/Call/sipSPICallInfo:
Disconnect Cause (CC) : 65
Disconnect Cause (SIP) : 200
Nov 30 11:44:49.406: //64510/3CD5D2000001/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.18.81.2:5060;branch=z9hG4bK3ECC55
From: <sip:[email protected]>;tag=3C365010-1E42
To: "Bianca Africa" <sip:[email protected]>;tag=9082578~cdf4c5a6-dd2b-4c71-bca0-b262ad997720-44517224
Date: Sun, 30 Nov 2014 11:44:49 GMT
Call-ID: [email protected]
CSeq: 101 BYE
Content-Length: 0
Nov 30 11:44:49.406: //64510/3CD5D2000001/SIP/Call/sipSPICallInfo:
The Call Setup Information is:
Call Control Block (CCB) : 0x0x3D816D70
State of The Call : STATE_DEAD
TCP Sockets Used : NO
Calling Number : 0218091323
Called Number : 0862000000
Source IP Address (Sig ): 10.18.81.2
Destn SIP Req Addr:Port : 10.18.81.11:5060
Destn SIP Resp Addr:Port : 10.18.81.11:5060
Destination Name : 10.18.81.11
Nov 30 11:44:49.406: //64510/3CD5D2000001/SIP/Call/sipSPIMediaCallInfo:
Number of Media Streams: 1
Media Stream : 1
Negotiated Codec : g729br8
Negotiated Codec Bytes : 20
Nego. Codec payload : 18 (tx), 18 (rx)
Negotiated Dtmf-relay : 6
Dtmf-relay Payload : 101 (tx), 101 (rx)
Source IP Address (Media): 10.18.81.2
Source IP Port (Media): 22350
Destn IP Address (Media): 0.0.0.0
Destn IP Port (Media): 21928
Orig Destn IP Address:Port (Media): [ - ]:0
Nov 30 11:44:49.406: //64510/3CD5D2000001/SIP/Call/sipSPICallInfo:
Disconnect Cause (CC) : 86
Disconnect Cause (SIP) : 200
PM-HO-VG-01#

Hi Manish,
Again, excellent feedback. Much appreciated.
I will try the commands suggested above and see if I can get DTMF to work correctly while interworking H.323 and SIP.
But my ultimate goal is to have SIP all way from the CUCM to the CUBE and from the CUBE to the ITSP.
If I enable SIP Early Offer with MTP on the CUCM going to the CUBE, all SIP Invite sent from the CUCM to the CUBE uses G.729r8 as the codec and once the call is established using G.729r8 should the ITSP reply with that codec, the call succeed and I am able to see an active MTP session using G.729 when I issue the command # show sccp connections.
One thing that I saw is that my ITSP love so much sending G.729br8 most of the times, so even if using SIP EO with MTP on the SIP Trunk to the CUBE, when I sent my INVITE out from the CUCM to the CUBE using G.729r8, specially on call center numbers such as 0800 numbers, you will see that the call established but the codec being negotiated is G.729br8 which is voice only (missing DTMF).
I will be doing some intensive test again later on this week and will send the logs.
Here is my question to both of you:
Which is the best way of having a proper SIP to SIP setup all the way that will not pose any problem?
Do I have to enable Early Offer on the SIP Profile used by the CUBE SIP Trunk or should I use the normal Standard SIP Profile? Do I need to enable MTP on my CUBE SIP Trunk or not?
From the CUBE point of view, I have a voice class codec that support G.729r8 or G.729br8 and the DTMF Relay method supported by the ITSP is RFC 2833.
I will send more logs for each scenario. I think that we are getting close to the resolution of this problem.
Thanks again for your support fellows.

Silent monitoring calls with CUCM 6.0 and UCCX 5.0

Dear all,
We have just integrated a 3rd party recording solution in our VoIP system, which consists of CUCM 6.0 and UCCX 5.0.
Until now we used the recording and monitoring solution of the UCCX for the agents. This worked ok.
But, as we wanted to record other people's calls and also the outgoing calls of the agents, we have created for them a Recording profile in the CCM and assign it to the agents phone.
We have also mantained the recording and monitoring active for them in the UCCX.
What is happenning now is the following:
- The 3rd party recordings works perfectly.
- The recording in the UCCX gets only one way audio.
- The silent monitoring gets only one way audio.
- If the 3rd party recording server is stopped, but the recording profile is stil active in the phones, the silent monitoring in the UCCX works.
Could any of you confirm if using a 3rd party recording solution the monitoring still works?
Is there any 3rd party silent monitoring software?
Thanks in advcance.
Best regards,
Amaia

We've got to delimit the problem.
When we use 3rd party recording solution there are 4 RTP flows: 1 incoming to monitored/recorded phone and 3 flows outgoing.
1 incoming RTP flows
- voice of remote phone
3 outgoing RTP flows
- voice of monitored/recorded phone
- voice of monitored/recorded phone sent to 3d party recording server
- voice of remote phone sent to 3rd party recording server
When we use a network analyzer we see that the agent running in the PC (UCCX 5.0) establishes two RTP flows for the monitoring session. But we can see that one of these flows sends 3 packet RTP per 1 packet RTP sent in the other RTP flow (in the same time).
We think agent sends to monitoring device all the outoing RTP packets of the phone (that belong to three different RTP flows), instead of sending only the RTP packets belonging to voice of monitored/recorded phone.
The other flow, voice of remote phone, sounds fine.
Is there a solution to avoid this problem when we monitor with UCCX 5.0 and record with a 3rd party software at the same time?
Thanks,
Christian

[SOLVED ]SX10 TC7.3 no audio and Video when calling

Hi,
I have very wierd issue with one sx10(TC7.3.0) endpoint. When I make a call to another sx10 (TC7.1.4) then signalling works fine and call is connected but there is no audio and video.It is not working even when I call to some external different type video endpoint. I noticed that there is no receiving info about audio and video but transmit codecs and other info looks correct.
Hope someone can help me to troubleshoot the problem.
More info about my solution:
I use CUCM with VCS-c and VCS-E. All endpoints are registered to CUCM. I have 16 SX10 endpoint with TC7.1.4 and one TC7,3,0. I think upgrading all endpoint to TC7.3.0 is not the solution because there are problems also with all other types enpoints.

Yes, Actually the problem was firewall rule!
The main problem was that these two endpoints didnt saw each other. ( Ping - Packet loss )
Signalling was working fine because both of them got ping CUCM but not each other :)
So problem is solved.
Thanks.

Cisco Jabber for Windows in Extend and Connect mode and making outbound calls

Hi guys,
I've set up Cisco Jabber for Windows to use Extend and Connect to control a remote PBX endpoint. I've configured the required CTI-RD device, remote destinations, associated the users to the line and added the devices to end-user controlled device. The extend and connect part is working flawlessly without any issues. I'm able to receive inbound calls on the remote PBX endpoint and control the call (hold, resume, transfer etc.) using the Jabber call window that pops up.
However, I'm unable to make any outbound calls via the Jabber client when in extend and Connect mode. Reading the Extend and Connect guide, I need to configure Dial Via Office (DVO) Reverse. So when the user initiates a Dial-Via-Office reverse call, CUCM calls and connect to the Extend and Connect device (CTI-RD). CUCM then calls and connects to the number the user dialled and finally connects the two call legs.
After attempting to configure DVO-R for Jabber for Windows in Extend and Connect mode following the CUCM feature services guide, i'm unable to get any outbound calls working. From RTMT, i am receiving the following Termination Cause Code: (27) Destination out of order. What i also notice is that there is no calling number for that trace either. I would've thought that the calling party would've been the Enterprise Feature Access (EFA) number.
Has anyone got this working or can provide some guidance?
Thanks.

Hi guys,
I've set up Cisco Jabber for Windows to use Extend and Connect to control a remote PBX endpoint. I've configured the required CTI-RD device, remote destinations, associated the users to the line and added the devices to end-user controlled device. The extend and connect part is working flawlessly without any issues. I'm able to receive inbound calls on the remote PBX endpoint and control the call (hold, resume, transfer etc.) using the Jabber call window that pops up.
However, I'm unable to make any outbound calls via the Jabber client when in extend and Connect mode. Reading the Extend and Connect guide, I need to configure Dial Via Office (DVO) Reverse. So when the user initiates a Dial-Via-Office reverse call, CUCM calls and connect to the Extend and Connect device (CTI-RD). CUCM then calls and connects to the number the user dialled and finally connects the two call legs.
After attempting to configure DVO-R for Jabber for Windows in Extend and Connect mode following the CUCM feature services guide, i'm unable to get any outbound calls working. From RTMT, i am receiving the following Termination Cause Code: (27) Destination out of order. What i also notice is that there is no calling number for that trace either. I would've thought that the calling party would've been the Enterprise Feature Access (EFA) number.
Has anyone got this working or can provide some guidance?
Thanks.

Major diff. b/w CUCM v7,v8 and v9

Hi All,What are the major differences between CUCM v7, v8 and v9 ?
Thanks

Hi,
you can also visit the link and refer word DOC by Rob.
https://supportforums.cisco.com/discussion/11073566/differences-between-versions-cisco-call-manager
CUCM 8 supports virtualization and version 9 supports centralised ELM along with virtualisation while call manager 7 does not support both.
regds,
aman

[svn] 2622: TextBox and TextGraphic now call applyDisplayObjectProperties() at the end of their draw() method, like all other GraphicElements.

Revision: 2622
Author: [email protected]
Date: 2008-07-24 16:13:32 -0700 (Thu, 24 Jul 2008)
Log Message:
TextBox and TextGraphic now call applyDisplayObjectProperties() at the end of their draw() method, like all other GraphicElements. This method handles setting the visibiliy of the GraphicElement's DisplayObject, among other things.
Note: We should make it unnecessary for each GraphicElement subclass to have to call applyDisplayObjectProperties() at the end of draw(). The GraphicElement base class should ensure that this gets called at the appropriate time.
Group now calls draw() on graphic elements even if they are invisible, because otherwise applyDisplayObjectProperties() never gets called and the TextLines stay visible. Group was assuming that the only visible stuff in a GraphicElement is drawn with Graphics calls, which isn't the case.
This change is OK for now because every GraphicElement currently has its own DisplayObject, but it will need to be rethought when GraphicElements share DisplayObjects.
Reviewer: Chet
Bug: MXMLG-206 ("Setting visible property on TextGraphic does nothing")
QA: Peter, please add a Mustella test case for the 'visible property of TextBox and TextGraphic
Doc: No
Ticket Links:
http://bugs.adobe.com/jira/browse/MXMLG-206
Modified Paths:
flex/sdk/trunk/frameworks/projects/flex4/src/flex/core/Group.as
flex/sdk/trunk/frameworks/projects/flex4/src/flex/graphics/TextBox.as
flex/sdk/trunk/frameworks/projects/flex4/src/flex/graphics/TextGraphic.as

Changes for spine–aligned head:
public class StickManTool extends JPanel
    public StickManTool ()
        limbs [16] = new Limb (lankle, lfoot, 1);
        head = new Head2D (limbs[0]);
    protected void paintComponent (Graphics g)
        head.draw(graphics);
    private void updateLimbs (Point start, Point end)
        head.setPosition();
class Head2D extends Ellipse2D.Double
    public static double width = 30;   // width of head
    public static double height = 40; //height of head
    Point atlas;
    Point pelvis;
    private AffineTransform xform = new AffineTransform();
    public Head2D(Limb spine)
        super ();
        atlas = spine.movingJoint;
        pelvis = spine.fixedJoint;
        setPosition();
    public void setPosition()
        // Find angle of spine.
        double dy = atlas.y - pelvis.y;
        double dx = atlas.x - pelvis.x;
        double theta = Math.atan2(dy, dx);
        //System.out.printf("theta = %.1f%n", Math.toDegrees(theta));
        // Find center of head as extension along spine from atlas.
        double cx = atlas.x + (height/2)*Math.cos(theta);
        double cy = atlas.y + (height/2)*Math.sin(theta);
        // Move to origin of head.
        xform.setToTranslation(cx-width/2, cy-height/2);
        // Rotate head about its center.
        xform.rotate(theta+Math.PI/2, width/2, height/2);
    public void draw(Graphics2D g2)
        g2.draw(xform.createTransformedShape(this));
    public double getWidth () { return width; }
    public double getHeight () { return height; }
    public void setWidth (double widthIn) { width = widthIn; }
    public void setHeight (double heightIn) { height = heightIn; }
}

Assertion failed: poll() is a blocking call and cannot be called on the Service thread

Hi
We are getting a strange issue, the application successfully joins the cluster but after start failing with following exception.
The cluster have three nodes storage disabled web-logic and two standalone coherence JVM's, we are using distributed cache with Local scheme
<Error> (thread=DistributedCache, member=4): Assertion failed: poll() is a blocking call and cannot be called on the Service thread
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.poll(Grid.CDB:5)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.poll(Grid.CDB:11)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.partitionedService.PartitionedCache$BinaryMap.get(PartitionedCache.CDB:26)
at com.tangosol.util.ConverterCollections$ConverterMap.get(ConverterCollections.java:1655)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.partitionedService.PartitionedCache$ViewMap.get(PartitionedCache.CDB:1)
at com.tangosol.coherence.component.util.SafeNamedCache.get(SafeNamedCache.CDB:1)
at com.thehartford.pi.core.referencedata.dao.cachedaoimpl.ReferenceCacheDAOImpl.getReferenceData(Unknown Source)
at com.thehartford.pi.core.caching.cachestore.ReferenceCacheStore.load(Unknown Source)
at com.tangosol.net.cache.ReadWriteBackingMap$CacheLoaderCacheStore.load(ReadWriteBackingMap.java:6132)
at com.tangosol.net.cache.ReadWriteBackingMap$CacheStoreWrapper.loadInternal(ReadWriteBackingMap.java:5616)
at com.tangosol.net.cache.ReadWriteBackingMap$StoreWrapper.load(ReadWriteBackingMap.java:4698)
at com.tangosol.net.cache.ReadWriteBackingMap.get(ReadWriteBackingMap.java:717)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.partitionedService.PartitionedCache$Storage.get(PartitionedCache.CDB:10)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.partitionedService.PartitionedCache.onGetRequest(PartitionedCache.CDB:23)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.partitionedService.PartitionedCache$GetRequest.run(PartitionedCache.CDB:1)
at com.tangosol.coherence.component.net.message.requestMessage.DistributedCacheKeyRequest.onReceived(DistributedCacheKeyRequest.CDB:12)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.onMessage(Grid.CDB:34)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.onNotify(Grid.CDB:33)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.PartitionedService.onNotify(PartitionedService.CDB:3)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.partitionedService.PartitionedCache.onNotify(PartitionedCache.CDB:3)
at com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:42)
at java.lang.Thread.run(Thread.java:722)
ERROR 2013-09-20 09:06:42,515 : [2013-09-20 09:06:42.515/8740.228 Oracle Coherence GE 3.7.1.0 <Error> (thread=DistributedCache, member=4): Assertion failed: poll() is a blocking call and cannot be called on the Service thread
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.poll(Grid.CDB:5)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.poll(Grid.CDB:11)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.partitionedService.PartitionedCache$BinaryMap.get(PartitionedCache.CDB:26)
at com.tangosol.util.ConverterCollections$ConverterMap.get(ConverterCollections.java:1655)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.partitionedService.PartitionedCache$ViewMap.get(PartitionedCache.CDB:1)
at com.tangosol.coherence.component.util.SafeNamedCache.get(SafeNamedCache.CDB:1)
at com.thehartford.pi.core.referencedata.dao.cachedaoimpl.ReferenceCacheDAOImpl.getReferenceData(Unknown Source)
at com.thehartford.pi.core.caching.cachestore.ReferenceCacheStore.load(Unknown Source)
at com.tangosol.net.cache.ReadWriteBackingMap$CacheLoaderCacheStore.load(ReadWriteBackingMap.java:6132)
at com.tangosol.net.cache.ReadWriteBackingMap$CacheStoreWrapper.loadInternal(ReadWriteBackingMap.java:5616)
at com.tangosol.net.cache.ReadWriteBackingMap$StoreWrapper.load(ReadWriteBackingMap.java:4698)
at com.tangosol.net.cache.ReadWriteBackingMap.get(ReadWriteBackingMap.java:717)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.partitionedService.PartitionedCache$Storage.get(PartitionedCache.CDB:10)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.partitionedService.PartitionedCache.onGetRequest(PartitionedCache.CDB:23)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.partitionedService.PartitionedCache$GetRequest.run(PartitionedCache.CDB:1)
at com.tangosol.coherence.component.net.message.requestMessage.DistributedCacheKeyRequest.onReceived(DistributedCacheKeyRequest.CDB:12)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.onMessage(Grid.CDB:34)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.onNotify(Grid.CDB:33)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.PartitionedService.onNotify(PartitionedService.CDB:3)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.partitionedService.PartitionedCache.onNotify(PartitionedCache.CDB:3)
at com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:42)

Hi
The problem is that you are making a re-entrant call back into a cache service from the service thread or worker thread of a cache service. This is a bad thing to do as you risk deadlocking your cluster by consuming all of the threads in the service. From the stack trace it looks like you are doing a get on a cache which is calling through to a cache store which is then doing a get on another cache.
For example, you have done a "get" on a cache, that has now consumed a worker thread (call it Thread-1), that thread is calling the cache store which is doing a get on another cache in the same cache service so will now consume another thread (call it Thread-2) so you now have two threads in use, Thread-1 will not return until Thread-2 completes. Now say you had 2 worker threads on your cache service and two "get" calls came in at the same time, Get-1 and Get-2. Both worker threads are now in use so when Get-1 calls the cache store to do a get on the other cache then it has to wait for a worker thread to become free to process the get. The same applies to Get-2, it is calling the cache store and waiting for a thread to become free. The problem is no threads will become free as they are all waiting. Hopefully that is a clear enough explanation of why you get the warning.
Read this Constraints on Re-entrant Calls - 12c (12.1.2) This is for 12.1.2 but the same applies for any Coherence version.
JK

Info QUAD-CORE and Oracle 9i

If we purchase a machine with a quad-core cpu, will the database be able to take advantage of it? Or are we better of with multiple dual-core processors? Or one dual-core processor?
upgrade oracle 9.2.0.1 to 9.2.0.8?
Tanks

Well, assuming that you are going to use the Windows 64-bit version of Oracle 9i (9.2.0.2), then I'd go with the 64-bit processors. And, if you can get quad cores, then I would go for them and I'm pretty sure that the database will use them all, having seen it use dual core processors in the past.
Oracle don't seem to worry about the number of processor cores for their licensing (at least for enterprise edition) as they license in other ways but you should watch for other products you might install on the server that do. I once worked with an ETL tool called AbInitio, which does licence per core and they charged an absolute fortune becuase we were using dual core processors!
I'm assuming that you are going with Oracle 9i due to a need to run an older version? Otherwise, I'd recommend an upgrade to either 10g or 11g.
cheers,
R

CUCM, VCS-Core and Edge, B2B Calling

Similar Messages

Maybe you are looking for