Message notification not working

Answered Question
Jul 28th, 2009
User Badges:

We have a UC520 with 4 FXO port (we are waiting for the PRI). I have enabled message notification to Cell.

I had it working last Friday, came in on Monday and it has stopped working. I tried message notification to a different extention, to email. none of them work.



I have it turned on system wide for notification. I turned it off did a system sync. I restarted teh system. Still nothing.

I did a restore to a week earlier still nothing.


Any Ideas were I can start looking would be apreciated.

Correct Answer by Marcos Hernandez about 7 years 10 months ago

OK. Can you try to point your CUE to an external NTP server, instead of the UC500 IP? There is a known issue with clock synchronization that will be fix in the next SBCS release.


1) Log into the CUE CLI

2) Type "conf t"

3) Configure "ntp server". You can do "?" for command syntax.

4) Exit out of config mode

5) Type "write mem" to save.


Let me know if this helps,


Marcos

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Marcos Hernandez Tue, 07/28/2009 - 12:20
User Badges:
  • Blue, 1500 points or more

First thing to check is that you have the right SIP gateway hostname under "Configure > Call manager Express" if you are using the CUE GUI. Typically, this hostname is the IP 10.1.10.2.


Let me know,


Marcos

r-mcconnell Tue, 07/28/2009 - 14:10
User Badges:

what are some debug comands I could try, and see if it showa me if it is even trying?

r-mcconnell Wed, 07/29/2009 - 09:56
User Badges:

I guess this might be the problem.

Not sure why it was set and now its not.

I am not sure how to configure this.


CUCME.jpg

Marcos Hernandez Wed, 07/29/2009 - 10:11
User Badges:
  • Blue, 1500 points or more

This is not it. MWI is different. I am reviewing your config and will provide comments today. IF I can't find anythign abvious, we will get TAC involved.


Thanks,


Marcos

stacy.thompson Wed, 07/29/2009 - 10:36
User Badges:
  • Bronze, 100 points or more

Marcos,

Our TAC case on cell notification failing was 610502775 - if that helps you find the answers or at least rule out our scenario here.

Marcos Hernandez Wed, 07/29/2009 - 11:34
User Badges:
  • Blue, 1500 points or more

I reviewed your configuration and it seems you do not have an SMTP server configured. Without this email notifications and text pager notifications won't work. Connect to the CUE GUI and navigate to "System >> SMTP Settings".


FYI, the following document details all the required steps to make notifications work:


http://www.cisco.com/en/US/docs/voice_ip_comm/sbcs/uc500/gui/user/guide/uc500_office_admin_guide_v2.pdf


Thanks,


Marcos

r-mcconnell Thu, 07/30/2009 - 06:59
User Badges:

how can I run a trace to see if it is even trying to make teh call?

Marcos Hernandez Thu, 07/30/2009 - 07:06
User Badges:
  • Blue, 1500 points or more

Are your using ISDN to connect to the PSTN?


For now, please provide a "debug ccsip message" for the entire call flow and email me the IOS config (telnet into the UC500 and do a "show run"). Notice this is not the CUE config (which I have already).


Thanks,


Marcos

r-mcconnell Thu, 07/30/2009 - 07:09
User Badges:

We are not using ISDN yet we are only using PSTN


I will get that info to you asap.

r-mcconnell Thu, 07/30/2009 - 13:52
User Badges:

I would apear that none of the message notification options work.

I have setup the SMTP settings and I have full access to the email server. there is no attempt to conect to the pop3 email server.

Marcos Hernandez Thu, 07/30/2009 - 13:55
User Badges:
  • Blue, 1500 points or more

Rick,


At this point I would kindly ask you to log a case with TAC and ask them to investigate further. Once you get it resolved, it would be great if you could share the resolution summary with us, or I can do that if you send me the case number privately.


Sorry we could not figure it out.


Marcos

r-mcconnell Fri, 07/31/2009 - 07:42
User Badges:

Hello Marco's


I am working on a TAC request, they say I don't have a service contract.


I just wanted to post this so you could have a quick look and maybe see something.


.

Unity#terminal monit
Unity#
003935: Jul 31 14:40:51.228: %SEC-6-IPACCESSLOGP: list 104 denied tcp 208.180          .70.176(61195) -> 192.168.1.115(24519), 1 packet
003936: Jul 31 14:40:51.228: %SEC-6-IPACCESSLOGP: list 104 denied tcp 208.180          .70.176(61196) -> 192.168.1.115(24519), 2 packets
003937: Jul 31 14:42:08.380: %VOIPAAA-5-VOIP_CALL_HISTORY: CallLegType 1, ConnectionId 23BF6BA17D1711DE82B5EDBDDF41E2E2, SetupTime 09:42:00.520 CDT Fri Jul 31 2009, PeerAddress 411, PeerSubAddress , DisconnectCause 10  , DisconnectText normal call clearing (16), ConnectTime 09:42:07.000 CDT Fri Jul 31 2009, DisconnectTime 09:42:08.380 CDT Fri Jul 31 2009, CallOrigin 2, ChargedUnits 0, InfoType 2, TransmitPackets 0, TransmitBytes 0, ReceivePackets 60, ReceiveBytes 9600
003938: Jul 31 14:42:08.380: %VOIPAAA-5-VOIP_FEAT_HISTORY: FEAT_VSA=fn:TWC,ft:07/31/2009 09:42:00.516,cgn:411,cdn:,frs:0,fid:362,fcid:23BF6BA17D1711DE82B5EDBDDF41E2E2,legID:112,bguid:23BF6BA17D1711DE82B5EDBDDF41E2E2
003939: Jul 31 14:42:08.400: %VOIPAAA-5-VOIP_CALL_HISTORY: CallLegType 1, ConnectionId 23BF6BA17D1711DE82B5EDBDDF41E2E2, SetupTime 09:42:03.160 CDT Fri Jul 31 2009, PeerAddress 19059522475, PeerSubAddress , DisconnectCause 10  , DisconnectText normal call clearing (16), ConnectTime 09:42:06.990 CDT Fri Jul 31 2009, DisconnectTime 09:42:08.400 CDT Fri Jul 31 2009, CallOrigin 1, ChargedUnits 0, InfoType 2, TransmitPackets 60, TransmitBytes 10080, ReceivePackets 68, ReceiveBytes 10880
003940: Jul 31 14:42:08.400: %VOIPAAA-5-VOIP_FEAT_HISTORY: FEAT_VSA=fn:TWC,ft:07/31/2009 09:42:03.152,cgn:2048325486,cdn:19059522475,frs:0,fid:363,fcid:23BF6BA17D1711DE82B5EDBDDF41E2E2,legID:113,bguid:23BF6BA17D1711DE82B5EDBDDF41E2E2
003941: Jul 31 14:42:52.016: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:[email protected]:5060;user=phone SIP/2.0
Via: SIP/2.0/UDP 10.1.10.1:5060;branch=z9hG4bK2m4bzZlUcfPW8q.8cRY9AA~~11
Max-Forwards: 70
To:
From: ;tag=cue9cf2c256
Call-ID: [email protected]
CSeq: 1 INVITE
Content-Length: 170
Contact:
Content-Type: application/sdp
Cisco-Gcid: 90A63087-0122-1000-4000-001125CUCE68
Call-Info: ;method="NOTIFY;Event=telephone-event;Duration=2000"
Allow-Events: telephone-event

v=0
o=CiscoSystemsSIP-Workflow-App-UserAgent 142 142 IN IP4 10.1.10.1
s=SIP Call
c=IN IP4 10.1.10.1
t=0 0
m=audio 16898 RTP/AVP 0
a=rtpmap:0 pcmu/8000
a=ptime:20

003942: Jul 31 14:42:52.040: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 100 Trying
Date: Fri, 31 Jul 2009 14:42:52 GMT
From: ;tag=cue9cf2c256
Allow-Events: telephone-event
Content-Length: 0
To:
Call-ID: [email protected]
Via: SIP/2.0/UDP 10.1.10.1:5060;branch=z9hG4bK2m4bzZlUcfPW8q.8cRY9AA~~11
CSeq: 1 INVITE
Server: Cisco-SIPGateway/IOS-12.x


003943: Jul 31 14:42:52.048: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 180 Ringing
Date: Fri, 31 Jul 2009 14:42:52 GMT
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
From: ;tag=cue9cf2c256
Allow-Events: telephone-event
Remote-Party-ID: ;party=called;screen=no;privacy=off
Content-Length: 0
To: ;tag=6D17064-4C3
Contact:
Call-ID: [email protected]
Via: SIP/2.0/UDP 10.1.10.1:5060;branch=z9hG4bK2m4bzZlUcfPW8q.8cRY9AA~~11
CSeq: 1 INVITE
Server: Cisco-SIPGateway/IOS-12.x


003944: Jul 31 14:42:57.000: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
CANCEL sip:[email protected]:5060;user=phone SIP/2.0
Via: SIP/2.0/UDP 10.1.10.1:5060;branch=z9hG4bK2m4bzZlUcfPW8q.8cRY9AA~~11
Max-Forwards: 70
To:
From: ;tag=cue9cf2c256
Call-ID: [email protected]
CSeq: 1 CANCEL
Content-Length: 0


003945: Jul 31 14:42:57.008: %VOIPAAA-5-VOIP_CALL_HISTORY: CallLegType 1, ConnectionId 4271B3647D1711DE82BAEDBDDF41E2E2, SetupTime 09:42:52.038 CDT Fri Jul 31 2009, PeerAddress A801409, PeerSubAddress , DisconnectCause 10  , DisconnectText normal call clearing (16), ConnectTime 09:42:57.008 CDT Fri Jul 31 2009, DisconnectTime 09:42:57.008 CDT Fri Jul 31 2009, CallOrigin 1, ChargedUnits 0, InfoType 2, TransmitPackets 0, TransmitBytes 0, ReceivePackets 0, ReceiveBytes 0
003946: Jul 31 14:42:57.008: %VOIPAAA-5-VOIP_FEAT_HISTORY: FEAT_VSA=fn:TWC,ft:07/31/2009 09:42:52.028,cgn:500,cdn:A801409,frs:0,fid:365,fcid:4271B3647D1711DE82BAEDBDDF41E2E2,legID:115,bguid:4271B3647D1711DE82BAEDBDDF41E2E2
003947: Jul 31 14:42:57.008: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Date: Fri, 31 Jul 2009 14:42:57 GMT
From: ;tag=cue9cf2c256
Content-Length: 0
To:
Call-ID: [email protected]
Via: SIP/2.0/UDP 10.1.10.1:5060;branch=z9hG4bK2m4bzZlUcfPW8q.8cRY9AA~~11
CSeq: 1 CANCEL


003948: Jul 31 14:42:57.016: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 487 Request Cancelled
Reason: Q.850;cause=16
Date: Fri, 31 Jul 2009 14:42:57 GMT
From: ;tag=cue9cf2c256
Allow-Events: telephone-event
Content-Length: 0
To: ;tag=6D17064-4C3
Call-ID: [email protected]
Via: SIP/2.0/UDP 10.1.10.1:5060;branch=z9hG4bK2m4bzZlUcfPW8q.8cRY9AA~~11
CSeq: 1 INVITE
Server: Cisco-SIPGateway/IOS-12.x


003949: Jul 31 14:42:57.024: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:[email protected]:5060;user=phone SIP/2.0
Via: SIP/2.0/UDP 10.1.10.1:5060;branch=z9hG4bK2m4bzZlUcfPW8q.8cRY9AA~~11
Max-Forwards: 70
To: ;tag=6D17064-4C3
From: ;tag=cue9cf2c256
Call-ID: [email protected]
CSeq: 1 ACK
Content-Length: 0


003950: Jul 31 14:42:57.028: %VOIPAAA-5-VOIP_CALL_HISTORY: CallLegType 2, ConnectionId 4271B3647D1711DE82BAEDBDDF41E2E2, SetupTime 09:42:52.028 CDT Fri Jul 31 2009, PeerAddress 500, PeerSubAddress , DisconnectCause 10  , DisconnectText normal call clearing (16), ConnectTime 09:42:57.028 CDT Fri Jul 31 2009, DisconnectTime 09:42:57.028 CDT Fri Jul 31 2009, CallOrigin 2, ChargedUnits 0, InfoType 2, TransmitPackets 0, TransmitBytes 0, ReceivePackets 0, ReceiveBytes 0
003951: Jul 31 14:42:57.028: %VOIPAAA-5-VOIP_FEAT_HISTORY: FEAT_VSA=fn:TWC,ft:07/31/2009 09:42:52.020,cgn:500,cdn:A801409,frs:0,fid:364,fcid:4271B3647D1711DE82BAEDBDDF41E2E2,legID:114,bguid:4271B3647D1711DE82BAEDBDDF41E2E2
003952: Jul 31 14:43:38.556: %SEC-6-IPACCESSLOGP: list 104 denied udp 67.80.204.28(1049) -> 192.168.1.115(1434), 1 packet

Steven Smith Fri, 07/31/2009 - 07:49
User Badges:
  • Gold, 750 points or more

The message that you have there looks to be setting MWI (on or off).  Unfortunately, nothing there about other message notifications from what I can see.

r-mcconnell Fri, 07/31/2009 - 08:01
User Badges:

OK thank you.

Just getting frustrated and thought it was worth somebody having a look again.

Marcos Hernandez Fri, 07/31/2009 - 10:00
User Badges:
  • Blue, 1500 points or more

Rick,


I will be posting shortly the steps I followed to make this work with screen shots. We will help you resolve this.


Marcos

Marcos Hernandez Fri, 07/31/2009 - 11:12
User Badges:
  • Blue, 1500 points or more

Rick,


I did exactly this and it worked. Follow the story board below and let me know. Notice that my notification confguration for numeric paging, I tested with an internal extension (201) to verify that CUE was trying to ring that number:


not1.png

not3.png

not2.png

not5.png


Let me know how it goes.


Thanks,


Marcos

r-mcconnell Fri, 07/31/2009 - 12:03
User Badges:

I thank everybody for there thoughts and help.


I have no idea why it happend this way but here is what I had to do to enable the notifications.

I had to change the hours of notification to 24 hours everyday. If I just selected 7AM-6PM it would not try to deliver a message. I have checked out Time zone and it is fine.

The time and date on the phones is also correct.


Again thanks.

stacy.thompson Wed, 07/29/2009 - 08:21
User Badges:
  • Bronze, 100 points or more

We had a similar issue with notifications on a SIP circuit.


Marcos may understand what the solution I am describing was better than I do- I am actually taking this off tech notes in our system.  Maybe it will give you some direction?


We were told that CUE only handles g711 so we had to add an 'incoming called-number'  to by pass the default dial peer 0.  Apparently default dial-peer 0 sent traffic at g729 so then it was dropped by CUE.


Stacy

r-mcconnell Fri, 07/31/2009 - 13:50
User Badges:

The time every where shows as corect but it is wrong somewhere.

When I got the notification to email setup the message was sent today(July 31-09 2:00PM)

The header in the message said it was sent Sunday July 19-09 1:55AM.

So when I set it to deliver 24 hrs it works.

Correct Answer
Marcos Hernandez Sat, 08/01/2009 - 05:48
User Badges:
  • Blue, 1500 points or more

OK. Can you try to point your CUE to an external NTP server, instead of the UC500 IP? There is a known issue with clock synchronization that will be fix in the next SBCS release.


1) Log into the CUE CLI

2) Type "conf t"

3) Configure "ntp server". You can do "?" for command syntax.

4) Exit out of config mode

5) Type "write mem" to save.


Let me know if this helps,


Marcos

Actions

This Discussion