Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

MOH weird annoucement

Hi,

 

I know the answer is going something really simple and staring me right in the face, but...

 

I have a new CUCM setup, when I get put on hold, I hear a announcement "music ..... music" then the music plays. Then after a minute or so the same announcement repeats.

 

I'm really stumped, what haven't I done or am I doing wrong?

 

5 REPLIES

Have you uploaded any

Have you uploaded any customized MoH.. then only some other announcement will come.. choose the default MoH audio under MoH audio source and you will hear only MoH audio and not some announcements.

New Member

Nothing was added, it does

Nothing was added, it does play the default moh on hold. Its just the strange announcement before it starts playing and every 60 seconds or though after.

New Member

Ok, its only calls from or

Ok, its only calls from or too a SIP provider, when this call is placed on hold or resumed it plays this announcement.

Any chance its something the sending me that gets played when the call is initially placed on hold or resumed? Would CUCM allow something like this is there a way to block it?

New Member

I fixed this using MTP.I'd

I fixed this using MTP.

I'd love to know what is happening. Without MTP, there is a delay when pressing hold or resume. With MTP hold/resume is as it is at other installations I have.

The strange "music" announcement or whatever it is, is also gone now.

 

 

*May 19 16:55:55.084: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:4070@192.168.1.6:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.1:5060;branch=z9hG4bK5a3c077eefcf3
From: <sip:4070@192.168.1.1>;tag=89873~bf9a41df-6029-44be-b043-7003542f5a25-27455939
To: <sip:0808080111@192.168.1.6>;tag=5CD344D8-1B6A
Date: Mon, 19 May 2014 16:57:27 GMT
Call-ID: 22540229-DEAD11E3-917F80E2-4F4972E1@192.168.1.6
Supported: timer,resource-priority,replaces
Min-SE:  1800
Cisco-Guid: 0575850969-3735884259-2440659170-1330213601
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
Session-Expires:  1800;refresher=uac
P-Asserted-Identity: "PA Manager" <sip:4070@192.168.1.1>
Remote-Party-ID: "PA Manager" <sip:4070@192.168.1.1>;party=calling;screen=yes;privacy=off
Contact: <sip:4070@192.168.1.1:5060>
Content-Type: application/sdp
Content-Length: 186

v=0
o=CiscoSystemsCCM-SIP 89873 4 IN IP4 192.168.1.1
s=SIP Call
c=IN IP4 0.0.0.0
t=0 0
m=audio 4000 RTP/AVP 0
a=X-cisco-media:umoh
a=rtpmap:0 PCMU/8000
a=ptime:20
a=inactive

*May 19 16:55:55.088: //75019/2252C9D99179/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.1.1:5060;branch=z9hG4bK5a3c077eefcf3
From: <sip:4070@192.168.1.1>;tag=89873~bf9a41df-6029-44be-b043-7003542f5a25-27455939
To: <sip:0808080111
0808080111#2@192.168.1.6>;tag=5CD344D8-1B6A
Date: Mon, 19 May 2014 16:55:55 GMT
Call-ID: 22540229-DEAD11E3-917F80E2-4F4972E1@192.168.1.6
CSeq: 103 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-15.2.4.M5
Content-Length: 0


*May 19 16:55:55.088: //75018/2252C9D99179/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:0808080111@10.0.0.1:5060;user=phone;transport=udp SIP/2.0
Via: SIP/2.0/UDP 10.20.0.84:5060;branch=z9hG4bK91FC1B78
From: <sip:0111222334@172.29.2.38;user=phone>;tag=5CD344E8-B84
To: <sip:0808080111@172.24.0.4;user=phone>;tag=f2cft78c-CC-27
Date: Mon, 19 May 2014 16:55:55 GMT
Call-ID: 9l89tllfvfld2fatetgb7fg6789albtb@SoftX3000
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Min-SE:  1800
Cisco-Guid: 0575850969-3735884259-2440659170-1330213601
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: 1400518555
Contact: <sip:0111222334@10.20.0.84:5060>
Expires: 180
Allow-Events: telephone-event
Content-Type: application/sdp
Content-Length: 267

v=0
o=CiscoSystemsSIP-GW-UserAgent 1660 842 IN IP4 10.20.0.84
s=SIP Call
c=IN IP4 0.0.0.0
t=0 0
m=audio 27910 RTP/AVP 0 97 19
c=IN IP4 0.0.0.0
a=inactive
a=rtpmap:0 PCMU/8000
a=rtpmap:97 telephone-event/8000
a=fmtp:97 0-15
a=rtpmap:19 CN/8000
a=ptime:20

*May 19 16:55:55.588: //75018/2252C9D99179/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:0808080111@10.0.0.1:5060;user=phone;transport=udp SIP/2.0
Via: SIP/2.0/UDP 10.20.0.84:5060;branch=z9hG4bK91FC1B78
From: <sip:0111222334@172.29.2.38;user=phone>;tag=5CD344E8-B84
To: <sip:0808080111@172.24.0.4;user=phone>;tag=f2cft78c-CC-27
Date: Mon, 19 May 2014 16:55:55 GMT
Call-ID: 9l89tllfvfld2fatetgb7fg6789albtb@SoftX3000
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Min-SE:  1800
Cisco-Guid: 0575850969-3735884259-2440659170-1330213601
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: 1400518555
Contact: <sip:0111222334@10.20.0.84:5060>
Expires: 180
Allow-Events: telephone-event
Content-Type: application/sdp
Content-Length: 267

v=0
o=CiscoSystemsSIP-GW-UserAgent 1660 842 IN IP4 10.20.0.84
s=SIP Call
c=IN IP4 0.0.0.0
t=0 0
m=audio 27910 RTP/AVP 0 97 19
c=IN IP4 0.0.0.0
a=inactive
a=rtpmap:0 PCMU/8000
a=rtpmap:97 telephone-event/8000
a=fmtp:97

CUCM will send an inactive

CUCM will send an inactive invite out and then sends a sendonly invite out with MOH information.  It could be the SIP carrier was replacing the SDP information to use their own music on hold source when sending a sendonly invite out.  Using an MTP allows the call to remain active the entire time as far as the SIP provider knows.

91
Views
0
Helpful
5
Replies