locked
Communicator Drops Call When Put On Hold RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hey,

    This questions relates to OCS 2007 R2.

    We have been using a Dialogic Media Gateway to route PSTN calls to our legacy PBX. This has been working perfectly for over a year now without any problems.

    We have just installed a Cisco 2800 (Cisco Unified Border Element) to connect us directly to SIP trunks from our Telephone provider. I have migrated a number of test users to the new Gateway. Everything seems to work correctly but one thing. When I put a call on hold I get the following message - 

    "Call cannot be placed on hold.  Your speaker and microphone have been muted."

    While the call still appears active when I un-mute the call the line is dead - I cannot here the caller and they cannot hear me. The call does not disconnect until the caller hangs up the phone.

    My first thought is that is must be the Cisco Gateway causing the issue as there was no problem using the Dialogic Gateway. My telephone provider thinks that the issue is with mediation server.

    Have you got any fixes or ideas on how I can troubleshoot this?

     

    Thanks,

    Andrew

    Sunday, July 25, 2010 10:54 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    This is not an uncommon situation when the service provider has not gone to the trouble to certify in the OIP program. I would be surprised if you said they had and were stilling having this issue.

    http://technet.microsoft.com/en-us/office/ocs/bb735838.aspx

    In saying that this document may help with the configuraiton with the CUBE. Although this is for CUCM it may be a good guide to helping you with your setup. Also take note of the IOS version in this docuement as you may be running into a bug on the CUBE.

    http://www.cisco.com/en/US/solutions/collateral/ns340/ns414/ns728/ns784/8464511.pdf

    Also you may want to run "debug ccsip message" on the CUBE to see what your SP sends back when you try to place the call on hold. Using the CUBE for interop to a SP is pretty common and a couple of SP's are using this configuration, so unless you have a buggy IOS or a misconfiguration on the CUBE it may be likely that if your SP hasnt qualified through the OIP that they are the issue. You also might want to ensure you have the latest updates on OCS if you decide to open a ticket with PS.

    Cheers

    Chris

     

    http://voipnorm.blogspot.com/
    Monday, July 26, 2010 6:21 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Can I email someone log files from the Cisco CUBE and OCS for analysis? 

    Cisco CUBE has been setup accroding to the guidelines and is running the latest IOS.

     

    Thanks,

    Andrew

    Monday, July 26, 2010 10:39 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    CISCO CUBE LOG:

    Call Placed on Hold - this is midcall just before placing on hold
=================================================================
[User Presses the HOLD Button]


Jul 26 14:31:31.521: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
 INVITE sip:049786583@192.168.100.70:5060;transport=tcp SIP/2.0
  From: <sip:099053000@ONZOCSMED3A.onzdom1.DOMAIN.COM;user=phone>;epid=6D20EF131D;tag=aed3c332a
  To: <sip:049786583@192.168.100.70;user=phone>;tag=F04A364-0
	CSEQ: 17 INVITE
	CALL-ID: 25d502be-8094-47b2-99c3-bde618f9d0bb
	MAX-FORWARDS: 70
  Via: SIP/2.0/TCP 192.168.100.71:49482;branch=z9hG4bK11a8e0b5
	CONTACT: <sip:ONZOCSMED3A.onzdom1.DOMAIN.COM:5060;transport=Tcp;maddr=192.168.100.71;ms-opaque=7677bec3aed90f28>
	CONTENT-LENGTH: 272
	SUPPORTED: timer
	SUPPORTED: 100rel
	USER-AGENT: RTCC/3.5.0.0 MediationServer
	CONTENT-TYPE: application/sdp; charset=utf-8
	Session-Expires: 1800
	Min-SE: 90

	v=0
	o=- 28 2 IN IP4 192.168.100.71
	s=session
	c=IN IP4 192.168.100.71
	b=CT:1000
	t=0 0
	m=audio 61006 RTP/AVP 0 101
	c=IN IP4 192.168.100.71
	a=rtcp:61007
	a=inactive
	a=label:Audio
	a=rtpmap:0 PCMU/8000
	a=rtpmap:101 telephone-event/8000
	a=fmtp:101 0-16
	a=ptime:20



Jul 26 14:31:31.545: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
 INVITE sip:218.101.55.1:5060 SIP/2.0
  Via: SIP/2.0/UDP 203.167.180.196:5060;branch=z9hG4bK1C62123
	P-Asserted-Identity: <sip:099053000@203.167.180.196>
  From: <sip:099053000@as.sip.softswitch.SIP_PROVIDER.net>;tag=F049FD0-83A
  To: <sip:049786583@as.sip.softswitch.SIP_PROVIDER.net>;tag=673899589-1280111451357
	Date: Mon, 26 Jul 2010 02:31:31 GMT
	Call-ID: A3DDD8B6-979411DF-81B5F60B-745C00D9@203.167.180.196
	Supported: 100rel,timer,resource-priority,replaces,histinfo,sdp-anat
	Min-SE: 90
	Cisco-Guid: 2749025262-2543063519-2175792651-1952186585
	User-Agent: Cisco-SIPGateway/IOS-12.x
	Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
	CSeq: 104 INVITE
	Max-Forwards: 70
	Timestamp: 1280111491
	Contact: <sip:099053000@203.167.180.196:5060>
	Expires: 180
	Allow-Events: telephone-event
	Authorization: Digest username="099053000",realm="SIP_PROVIDER.net",uri="sip:218.101.55.1:5060",response="515ca6c680ecec78e9b5d6bb89afe220",nonce="BroadWorksXgc2pb0pwTm6ctlnBW",cnonce="691EDDE8",qop=auth,algorithm=MD5,nc=00000003
	Session-Expires: 1800
	Content-Type: application/sdp
	Content-Disposition: session;handling=required
	Content-Length: 212

	v=0
	o=CiscoSystemsSIP-GW-UserAgent 7897 9933 IN IP4 203.167.180.196
	s=SIP Call
	c=IN IP4 203.167.180.196
	t=0 0
	m=audio 18948 RTP/AVP 0
	c=IN IP4 203.167.180.196
	a=sendrecv
	a=rtpmap:0 PCMU/8000
	a=ptime:20



Jul 26 14:31:31.545: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
 SIP/2.0 100 Trying
  Via: SIP/2.0/TCP 192.168.100.71:49482;branch=z9hG4bK11a8e0b5
  From: <sip:099053000@ONZOCSMED3A.onzdom1.DOMAIN.COM;user=phone>;epid=6D20EF131D;tag=aed3c332a
  To: <sip:049786583@192.168.100.70;user=phone>;tag=F04A364-0
	Date: Mon, 26 Jul 2010 02:31:31 GMT
	Call-ID: 25d502be-8094-47b2-99c3-bde618f9d0bb
	CSeq: 17 INVITE
	Allow-Events: telephone-event
	Server: Cisco-SIPGateway/IOS-12.x
	Content-Length: 0



Jul 26 14:31:31.549: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
 SIP/2.0 100 Trying
   Via:SIP/2.0/UDP 203.167.180.196:5060;branch=z9hG4bK1C62123
  From:<sip:099053000@as.sip.softswitch.SIP_PROVIDER.net>;tag=F049FD0-83A
  To:<sip:049786583@as.sip.softswitch.SIP_PROVIDER.net>;tag=673899589-1280111451357
	Call-ID:A3DDD8B6-979411DF-81B5F60B-745C00D9@203.167.180.196
	CSeq:104 INVITE
	Content-Length:0



Jul 26 14:31:31.577: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
 SIP/2.0 200 OK
   Via:SIP/2.0/UDP 203.167.180.196:5060;branch=z9hG4bK1C62123
  From:<sip:099053000@as.sip.softswitch.SIP_PROVIDER.net>;tag=F049FD0-83A
  To:<sip:049786583@as.sip.softswitch.SIP_PROVIDER.net>;tag=673899589-1280111451357
	Call-ID:A3DDD8B6-979411DF-81B5F60B-745C00D9@203.167.180.196
	CSeq:104 INVITE
	Allow:ACK,BYE,CANCEL,INFO,INVITE,OPTIONS,PRACK,REFER,NOTIFY
	Supported:
	Accept:multipart/mixed,application/media_control+xml,application/sdp
	Contact:<sip:218.101.55.1:5060>
	Content-Type:application/sdp
	Content-Length:220

	v=0
	o=BroadWorks 631536 1 IN IP4 218.101.55.225
	s=-
	c=IN IP4 218.101.55.225
	t=0 0
	m=audio 18758 RTP/AVP 0 100
	c=IN IP4 218.101.55.225
	a=rtpmap:0 PCMU/8000
	a=rtpmap:100 X-NSE/8000
	a=fmtp:100 192-194
	a=ptime:20



Jul 26 14:31:31.593: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
 SIP/2.0 200 OK
  Via: SIP/2.0/TCP 192.168.100.71:49482;branch=z9hG4bK11a8e0b5
  From: <sip:099053000@ONZOCSMED3A.onzdom1.DOMAIN.COM;user=phone>;epid=6D20EF131D;tag=aed3c332a
  To: <sip:049786583@192.168.100.70;user=phone>;tag=F04A364-0
	Date: Mon, 26 Jul 2010 02:31:31 GMT
	Call-ID: 25d502be-8094-47b2-99c3-bde618f9d0bb
	CSeq: 17 INVITE
	Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
	Allow-Events: telephone-event
	Contact: <sip:049786583@192.168.100.70:5060;transport=tcp>
	Supported: replaces
	Supported: sdp-anat
	Server: Cisco-SIPGateway/IOS-12.x
	Content-Type: application/sdp
	Content-Length: 253

	v=0
	o=CiscoSystemsSIP-GW-UserAgent 5995 3956 IN IP4 192.168.100.70
	s=SIP Call
	c=IN IP4 192.168.100.70
	t=0 0
	m=audio 19498 RTP/AVP 0 101
	c=IN IP4 192.168.100.70
	a=rtpmap:0 PCMU/8000
	a=rtpmap:101 telephone-event/8000
	a=fmtp:101 0-16
	a=ptime:20



Jul 26 14:31:31.593: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
 ACK sip:218.101.55.1:5060 SIP/2.0
  Via: SIP/2.0/UDP 203.167.180.196:5060;branch=z9hG4bK1C715AB
  From: <sip:099053000@as.sip.softswitch.SIP_PROVIDER.net>;tag=F049FD0-83A
  To: <sip:049786583@as.sip.softswitch.SIP_PROVIDER.net>;tag=673899589-1280111451357
	Date: Mon, 26 Jul 2010 02:31:31 GMT
	Call-ID: A3DDD8B6-979411DF-81B5F60B-745C00D9@203.167.180.196
	Max-Forwards: 70
	CSeq: 104 ACK
	Authorization: Digest username="099053000",realm="SIP_PROVIDER.net",uri="sip:218.101.55.1:5060",response="515ca6c680ecec78e9b5d6bb89afe220",nonce="BroadWorksXgc2pb0pwTm6ctlnBW",cnonce="691EDDE8",qop=auth,algorithm=MD5,nc=00000003
	Allow-Events: telephone-event
	Content-Length: 0



Jul 26 14:31:31.605: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
 ACK sip:049786583@192.168.100.70:5060;transport=tcp SIP/2.0
  From: <sip:099053000@ONZOCSMED3A.onzdom1.DOMAIN.COM;user=phone>;epid=6D20EF131D;tag=aed3c332a
  To: <sip:049786583@192.168.100.70;user=phone>;tag=F04A364-0
	CSEQ: 17 ACK
	CALL-ID: 25d502be-8094-47b2-99c3-bde618f9d0bb
	MAX-FORWARDS: 70
  Via: SIP/2.0/TCP 192.168.100.71:49482;branch=z9hG4bK14c05c4f
	CONTENT-LENGTH: 0
	USER-AGENT: RTCC/3.5.0.0 MediationServer



[RESUMED]




















Jul 26 14:36:22.836: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
 BYE sip:049786583@192.168.100.70:5060;transport=tcp SIP/2.0
  From: <sip:099053000@ONZOCSMED3A.onzdom1.DOMAIN.COM;user=phone>;epid=6D20EF131D;tag=aed3c332a
  To: <sip:049786583@192.168.100.70;user=phone>;tag=F04A364-0
	CSEQ: 18 BYE
	CALL-ID: 25d502be-8094-47b2-99c3-bde618f9d0bb
	MAX-FORWARDS: 70
  Via: SIP/2.0/TCP 192.168.100.71:49482;branch=z9hG4bKb0d9a11e
	CONTENT-LENGTH: 0
	USER-AGENT: RTCC/3.5.0.0 MediationServer



Jul 26 14:36:22.848: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
 SIP/2.0 200 OK
  Via: SIP/2.0/TCP 192.168.100.71:49482;branch=z9hG4bKb0d9a11e
  From: <sip:099053000@ONZOCSMED3A.onzdom1.DOMAIN.COM;user=phone>;epid=6D20EF131D;tag=aed3c332a
  To: <sip:049786583@192.168.100.70;user=phone>;tag=F04A364-0
	Date: Mon, 26 Jul 2010 02:36:22 GMT
	Call-ID: 25d502be-8094-47b2-99c3-bde618f9d0bb
	Server: Cisco-SIPGateway/IOS-12.x
	CSeq: 18 BYE
	Reason: Q.850;cause=16
	Content-Length: 0



Jul 26 14:36:22.852: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
 BYE sip:218.101.55.1:5060 SIP/2.0
  Via: SIP/2.0/UDP 203.167.180.196:5060;branch=z9hG4bK1C80
  From: <sip:099053000@as.sip.softswitch.SIP_PROVIDER.net>;tag=F049FD0-83A
  To: <sip:049786583@as.sip.softswitch.SIP_PROVIDER.net>;tag=673899589-1280111451357
	Date: Mon, 26 Jul 2010 02:31:31 GMT
	Call-ID: A3DDD8B6-979411DF-81B5F60B-745C00D9@203.167.180.196
	User-Agent: Cisco-SIPGateway/IOS-12.x
	P-Asserted-Identity: <sip:099053000@203.167.180.196>
	Timestamp: 1280111782
	CSeq: 105 BYE
	Authorization: Digest username="099053000",realm="SIP_PROVIDER.net",uri="sip:218.101.55.1:5060",response="db5fd91a3aefe23bf046c4f272799ed1",nonce="BroadWorksXgc2pb0pwTm6ctlnBW",cnonce="95FB6A62",qop=auth,algorithm=MD5,nc=00000004
	MAX-FORWARDS: 70
	Content-Length: 0



Jul 26 14:36:22.856: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
 SIP/2.0 200 OK
   Via:SIP/2.0/UDP 203.167.180.196:5060;branch=z9hG4bK1C80
  From:<sip:099053000@as.sip.softswitch.SIP_PROVIDER.net>;tag=F049FD0-83A
  To:<sip:049786583@as.sip.softswitch.SIP_PROVIDER.net>;tag=673899589-1280111451357
	Call-ID:A3DDD8B6-979411DF-81B5F60B-745C00D9@203.167.180.196
	CSeq:105 BYE
	Content-Length:0

    I also have logs in etl format so cannot post here. If you can provide an email address I can send them to you.

     

    Cheers,

    Andrew

    Tuesday, July 27, 2010 5:35 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hey,

    Can anyone help here?

    Thanks,

    Andrew

    Wednesday, July 28, 2010 9:03 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Andrew,

    Did you find the solution?

    Thanks,
    Ali

    Thursday, February 9, 2012 10:52 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I'd say CUBE is acting not as quite expected, because the invite from mediation server has a SDP with a=inactive, yet the invite sent by cube has a=sendreceive.  
    Friday, February 10, 2012 2:10 AM