Buy or Renew
Buy or Renew
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
3562
Views
0
Helpful
16
Replies

Cisco 8841 Voicemail Delay

matthew.murch1
Level 1
Level 1

‎09-10-2015 11:56 AM - edited ‎03-17-2019 04:16 AM

We have recently upgraded our VoIP phones from the Cisco 7942 to 8841. Our unit is running Cisco Unified Call Manager version 8.6.2 and Unity 5.0. When using the voicemail button on the 8841, there is roughly a 10 second delay before connecting with the voicemail server. Is this a normal feature or is there a configuration that can reduce this? Thanks.

 

Matt

Labels:
0 Helpful
16 Replies 16

Dennis Mink
VIP Alumni
VIP Alumni

‎09-10-2015 07:30 PM

that doesnt sound normal Matt,

 

can you add the trace files of a VM call and add them to this post, so we can have a look, cheers

Please remember to rate useful posts, by clicking on the stars below.

0 Helpful

matthew.murch1
Level 1
Level 1
In response to Dennis Mink

‎09-11-2015 07:01 AM

Dennis, attached is a trace file from a recent VM call. What stuck out to me was the second line, where it has 100 Trying. This seems to be where most of the time is take, roughly 15 seconds. Thank you for any help you can provide.

Preview file
13 KB
0 Helpful

Mohammed al Baqari
Level 11
Level 11
In response to matthew.murch1

‎09-11-2015 09:03 AM

Hi,

 

Please share the detailed SDL traces from CUCM to see what is happening during the call (assuming the trace level is arbitrary).

 

Also, please use voice port monitor to a check how long it takes between you initiating the call and a voicemail port getting occupied.

 

What integration are you using between CUCM and unity? SCCP or SIP?

 

 

0 Helpful

Wilson Samuel
Level 7
Level 7
In response to Mohammed al Baqari

‎09-11-2015 10:03 AM

Hi,

I have had a similar issue, it turned out that we had a WAN Issue between the UCXN Servers and in the SIP Trunk I was using Top Down approach and the first Server was unreachable.

Could you please elaborate the topology?

 

0 Helpful

mark tinsley
Level 1
Level 1
In response to Wilson Samuel

‎09-14-2015 06:09 AM

Hi,

I work in the same office as Matt and he will be out of the office for the next 6 weeks.  so im going to take this issue over.  here is a little more background on our setup and the issue that we are having.

we work on a large campus which receives its primary voice services from an MSL-100.  we have our call manager hanging off the MSL and is connected through 2 voice gateways.  we have roughly 1800 VOIP phones, all 7900 series and all run SCCP.  we recently purchased some 8841's, which only run SIP.  we were able to program the phones and get them up and running no problem.  we are able to dial on campus, local area, and long distance no problem.  all of the PLAR and shortened dialing prefix's (3 and 4 digit) which hit building paging systems work fine.

the only issue we have had is the message button, which is a speed dial that dials into our voicemail hunt pilot is delayed for 15 seconds after pressing.  we thought maybe it was an issue with the button, but even if we dial the number directly we still receive the delay.  we also took a phone from the 7900 series and programmed it as a SIP and it had the same issues. 

I don't think this is an issue with the network, I believe it is an issue with some minor programming within the call manager itself.  but we are just having issues finding the best places to start.  we set up a SIP dial rule for the number that hits our messages hunt pilot, but we probably didn't set it up correctly.

any suggestions?

 

0 Helpful

Wilson Samuel
Level 7
Level 7
In response to mark tinsley

‎09-14-2015 06:28 AM

You would want to use the Unity Port Usage Analyzer or rPSM (Port Status Monitor) and see what is going on when you dial the VM Pilot Point?

Also, could you please do DNA output and see what is the Call Flow path for this call

Regards

0 Helpful

mark tinsley
Level 1
Level 1
In response to Wilson Samuel

‎09-14-2015 06:40 AM

  • Results Summary
    • Calling Party Information
      • Calling Party = 7227304
      • Partition = AllPhones_pt
      • Device CSS = Device_css
      • Line CSS = Device_css
      • AAR Group Name =
      • AAR CSS =
    • Dialed Digits = 6000
    • Match Result = RouteThisPattern
    • Matched Pattern Information
      • Pattern = 6000
      • Partition = AllPhones_pt
      • Time Schedule =
    • Called Party Number = 6000
    • Time Zone = America/New_York
    • End Device = CiscoUM_HL
    • Call Classification = OnNet
    • InterDigit Timeout = YES
    • Device Override = Disabled
    • Outside Dial Tone = NO
  • Call Flow
    • TranslationPattern :Pattern=
      • Partition =
      • Positional Match List = 6000
      • Calling Party Number = 7227304
      • PreTransform Calling Party Number =
      • PreTransform Called Party Number =
      • Calling Party Transformations
        • External Phone Number Mask = NO
        • Calling Party Mask =
        • Prefix =
        • CallingLineId Presentation =
        • CallingName Presentation =
        • Calling Party Number = 7227304
      • ConnectedParty Transformations
        • ConnectedLineId Presentation =
        • ConnectedName Presentation =
      • Called Party Transformations
        • Called Party Mask =
        • Discard Digits Instruction =
        • Prefix =
        • Called Number =
    • Hunt Pilot :Pattern= 6000
      • Positional Match List = 6000
      • DialPlan =
      • Route Filter
        • Filter Name =
        • Filter Clause =
      • Hunt Forward Settings
        • Forward Hunt No Answer
        • Forward Hunt Busy
        • Maximum Hunt Timer =
      • Call Classification =
      • PreTransform Calling Party Number = 7227304
      • PreTransform Called Party Number = 6000
      • Calling Party Transformations
        • External Phone Number Mask = NO
        • Calling Party Mask =
        • Prefix =
        • CallingLineId Presentation = Default
        • CallingName Presentation = Default
        • Calling Party Number = 7227304
      • ConnectedParty Transformations
        • ConnectedLineId Presentation = Default
        • ConnectedName Presentation = Default
      • Called Party Transformations
        • Called Party Mask =
        • Discard Digits Instruction = None
        • Prefix =
        • Called Number = 6000
    • Hunt List :HuntListName= CiscoUM_HL
      • Line Group :LineGroupName= CiscoUM1
        • Directory Number :DN= 6300
          • Partition = AllPhones_pt
          • TypeCFACSSPolicy =
          • Call Classification = OnNet
          • Device :Type= Cisco Voice Mail Port
            • Device Status = UnKnown
            • Device Name = CiscoUM1-VI1
            • Ignore Presentation Indicators = Disabled
            • Logged Into Hunt Groups = Enabled
            • Alerting Name =
            • Dual Mode = Disabled
            • Automated Alternate Routing (AAR)
              • AAR Group Name =
              • AAR Calling Search Space =
              • AAR VoiceMail Status = Disabled
              • AAR Destination Mask =
              • AAR Prefix Digits =
        • Directory Number :DN= 6301
        • Directory Number :DN= 6302
        • Directory Number :DN= 6303
        • Directory Number :DN= 6304
        • Directory Number :DN= 6305
        • Directory Number :DN= 6306
        • Directory Number :DN= 6307
        • Directory Number :DN= 6308
        • Directory Number :DN= 6309
        • Directory Number :DN= 6310
        • Directory Number :DN= 6311
        • Directory Number :DN= 6312
        • Directory Number :DN= 6313
        • Directory Number :DN= 6314
        • Directory Number :DN= 6315
        • Directory Number :DN= 6316
        • Directory Number :DN= 6317
        • Directory Number :DN= 6318
        • Directory Number :DN= 6319
        • Directory Number :DN= 6320
        • Directory Number :DN= 6321
        • Directory Number :DN= 6322
        • Directory Number :DN= 6323
        • Directory Number :DN= 6324
        • Directory Number :DN= 6325
        • Directory Number :DN= 6326
        • Directory Number :DN= 6327
        • Directory Number :DN= 6328
        • Directory Number :DN= 6329
        • Directory Number :DN= 6330
        • Directory Number :DN= 6331
        • Directory Number :DN= 6332
        • Directory Number :DN= 6333
        • Directory Number :DN= 6334
        • Directory Number :DN= 6335
        • Directory Number :DN= 6336
        • Directory Number :DN= 6337
        • Directory Number :DN= 6338
        • Directory Number :DN= 6339
        • Directory Number :DN= 6340
        • Directory Number :DN= 6341
        • Directory Number :DN= 6342
        • Directory Number :DN= 6343
        • Directory Number :DN= 6344
        • Directory Number :DN= 6345
        • Directory Number :DN= 6346
        • Directory Number :DN= 6347
        • Directory Number :DN= 6348
        • Directory Number :DN= 6349
        • Directory Number :DN= 6350
        • Directory Number :DN= 6351
        • Directory Number :DN= 6352
        • Directory Number :DN= 6353
        • Directory Number :DN= 6354
        • Directory Number :DN= 6355
        • Directory Number :DN= 6356
        • Directory Number :DN= 6357
        • Directory Number :DN= 6358
        • Directory Number :DN= 6359
        • Directory Number :DN= 6360
        • Directory Number :DN= 6361
        • Directory Number :DN= 6362
        • Directory Number :DN= 6363
        • Directory Number :DN= 6364
        • Directory Number :DN= 6365
        • Directory Number :DN= 6366
        • Directory Number :DN= 6367
        • Directory Number :DN= 6368
        • Directory Number :DN= 6369
        • Directory Number :DN= 6370
        • Directory Number :DN= 6371
        • Directory Number :DN= 6372
        • Directory Number :DN= 6373
        • Directory Number :DN= 6374
        • Directory Number :DN= 6375
        • Directory Number :DN= 6376
        • Directory Number :DN= 6377
        • Directory Number :DN= 6378
        • Directory Number :DN= 6379
        • Directory Number :DN= 6380
        • Directory Number :DN= 6381
        • Directory Number :DN= 6382
        • Directory Number :DN= 6383
        • Directory Number :DN= 6384
        • Directory Number :DN= 6385
        • Directory Number :DN= 6386
        • Directory Number :DN= 6387
        • Directory Number :DN= 6388
        • Directory Number :DN= 6389
        • Directory Number :DN= 6390
        • Directory Number :DN= 6391
        • Directory Number :DN= 6392
        • Directory Number :DN= 6393
        • Directory Number :DN= 6394
        • Directory Number :DN= 6395
        • Directory Number :DN= 6396
        • Directory Number :DN= 6397
        • Directory Number :DN= 6398
        • Directory Number :DN= 6399
  • Alternate Matches
    • Note: Information Not Available
0 Helpful

mark tinsley
Level 1
Level 1
In response to mark tinsley

‎09-14-2015 07:05 AM

above is the output from the DNA.  it looks like it knows to route it, I will try to get the data from the Unity Port Usage Analyzer or rPSM (Port Status Monitor) here shortly.

0 Helpful

mark tinsley
Level 1
Level 1
In response to mark tinsley

‎09-14-2015 08:44 AM

I also need to clarify that currently we have voice mail ports set up between our call manager and unity server.  we do not have any SIP trunks set up between the two.

0 Helpful

Wilson Samuel
Level 7
Level 7
In response to mark tinsley

‎09-14-2015 09:43 AM

This looks like you have an SCCP Integration and shouldnt cause any delays per say.

Mind taking out the traces and submitting the trace files to the forum?

Regards

0 Helpful

mark tinsley
Level 1
Level 1
In response to Wilson Samuel

‎09-14-2015 10:23 AM

015/09/14 13:11:24.135|SIPL|0|TCP|IN|132.23.5.21|5060|SEP7426ACFA5485|172.16.12.37|50784|2,100,63,1.12797^172.16.12.37^*|37588|7426acfa-54850018-1460a3c3-2769ad6d@172.16.12.37|INVITE
2015/09/14 13:11:24.136|SIPL|0|TCP|OUT|132.23.5.21|5060|SEP7426ACFA5485|172.16.12.37|50784|2,100,63,1.12797^172.16.12.37^*|37589|7426acfa-54850018-1460a3c3-2769ad6d@172.16.12.37|100 Trying
2015/09/14 13:11:39.182|CC|SETUP|37762947|37762948|7227304|6000|6000
2015/09/14 13:11:39.190|CC|OFFERED|37762947|37762948|7227304|6000|6000|SEP7426ACFA5485|CiscoUM1-VI1
2015/09/14 13:11:39.192|SIPL|37762947|TCP|OUT|132.23.5.21|5060|SEP7426ACFA5485|172.16.12.37|50784|2,100,63,1.12802^172.16.12.37^*|37604|7426acfa-54850018-1460a3c3-2769ad6d@172.16.12.37|180 Ringing
2015/09/14 13:11:39.206|SIPL|37762947|TCP|OUT|132.23.5.21|5060|SEP7426ACFA5485|172.16.12.37|50784|1,100,56,1.57133769^132.23.5.23^CiscoUM1-VI1|37607|7426acfa-54850018-1460a3c3-2769ad6d@172.16.12.37|200 OK
2015/09/14 13:11:39.206|SIPL|37762947|TCP|OUT|132.23.5.21|5060|SEP7426ACFA5485|172.16.12.37|50784|1,100,56,1.57133769^132.23.5.23^CiscoUM1-VI1|37608|7426acfa-54850018-1460a3c3-2769ad6d@172.16.12.37|SUBSCRIBE
2015/09/14 13:11:39.212|SIPL|37762947|TCP|IN|132.23.5.21|5060|SEP7426ACFA5485|172.16.12.37|50784|2,100,63,1.12805^172.16.12.37^*|37609|7426acfa-54850018-1460a3c3-2769ad6d@172.16.12.37|ACK
2015/09/14 13:11:39.297|SIPL|37762947|TCP|IN|132.23.5.21|5060|SEP7426ACFA5485|172.16.12.37|50784|2,100,63,1.12806^172.16.12.37^*|37610|7426acfa-54850018-1460a3c3-2769ad6d@172.16.12.37|200 OK
2015/09/14 13:11:39.302|SIPL|37762947|TCP|IN|132.23.5.21|5060|SEP7426ACFA5485|172.16.12.37|50784|2,100,63,1.12807^172.16.12.37^*|37611|7426acfa-54850018-1460a3c3-2769ad6d@172.16.12.37|NOTIFY
2015/09/14 13:11:39.302|SIPL|37762947|TCP|OUT|132.23.5.21|5060|SEP7426ACFA5485|172.16.12.37|50784|2,100,63,1.12807^172.16.12.37^*|37612|7426acfa-54850018-1460a3c3-2769ad6d@172.16.12.37|200 OK
2015/09/14 13:11:41.873|SIPL|37762947|TCP|IN|132.23.5.21|5060|SEP7426ACFA5485|172.16.12.37|50784|2,100,63,1.12809^172.16.12.37^*|37615|7426acfa-54850018-1460a3c3-2769ad6d@172.16.12.37|BYE
2015/09/14 13:11:41.874|SIPL|37762947|TCP|OUT|132.23.5.21|5060|SEP7426ACFA5485|172.16.12.37|50784|2,100,63,1.12809^172.16.12.37^*|37616|7426acfa-54850018-1460a3c3-2769ad6d@172.16.12.37|200 OK
2015/09/14 13:11:41.876|SIPL|37762947|TCP|OUT|132.23.5.21|5060|SEP7426ACFA5485|172.16.12.37|50784|2,100,63,1.12809^172.16.12.37^*|37617|7426acfa-54850018-1460a3c3-2769ad6d@172.16.12.37|SUBSCRIBE
2015/09/14 13:11:41.876|CC|RELEASE|37762947|37762948|16
2015/09/14 13:11:41.937|SIPL|37762947|TCP|IN|132.23.5.21|5060|SEP7426ACFA5485|172.16.12.37|50784|2,100,63,1.12810^172.16.12.37^*|37618|7426acfa-54850018-1460a3c3-2769ad6d@172.16.12.37|200 OK
2015/09/14 13:11:41.977|SIPL|37762947|TCP|IN|132.23.5.21|5060|SEP7426ACFA5485|172.16.12.37|50784|2,100,63,1.12811^172.16.12.37^*|37619|7426acfa-54850018-1460a3c3-2769ad6d@172.16.12.37|NOTIFY
2015/09/14 13:11:41.978|SIPL|37762947|TCP|OUT|132.23.5.21|5060|SEP7426ACFA5485|172.16.12.37|50784|2,100,63,1.12811^172.16.12.37^*|37620|7426acfa-54850018-1460a3c3-2769ad6d@172.16.12.37|200 OK

0 Helpful

mark tinsley
Level 1
Level 1
In response to mark tinsley

‎09-14-2015 10:26 AM

between log numbers 2 and 3 there is 15 seconds that pass.  that is what we are trying to correct

0 Helpful

matthew.murch1
Level 1
Level 1
In response to Mohammed al Baqari

‎09-11-2015 12:01 PM

We are using SIP. We have other, older phones on the network that use SCCP that work just fine. When we switch one of the older phones to SIP we have the same delay issue. It seems there is something wrong with the way our SIP is set up.

0 Helpful

Wilson Samuel
Level 7
Level 7
In response to matthew.murch1

‎09-11-2015 12:18 PM

Run the Port Usage Analyzer and see what is really going on the UCXN side or if its on the CCM side.

http://www.ciscounitytools.com/Applications/CxN/PortUsageAnalyzer/PortUsageAnalyzer.html

HTH

0 Helpful
Customers Also Viewed These Support Documents