Here's a "fun" one.
Symptom:
I received intermittent reports/questions about the main line, "being forwarded to a cell phone". I know there's no reason why I would have forwarded the mainline to a cell phone.
Troubleshooting:
I checked Cisco Communications Manager and confirmed the main line wasn't forwarded to another number. Then I began to call the mainline from a land line & a cell phone but could not to reproduce the reported problem. During the tests when an operator wasn't available after 90 seconds my call was routed to the auto attendant as designed. I checked the logs for the reported problem call and found a normal call clearing from the PSTN. Sadly, I wasn't any closer to finding where the end user's disconnect was.
Luckily, one of the reporting persons then sent me a video of an example problem call to the main line on her mobile phone. Her mobile phone rang for right around 60 seconds and then played the following message.
"
Welcome to Verizon wireless. The wireless customer you called is not available at this time Please try your call again later. Announcement 1 switch [redacted]
"
This helped explain the confusion around why users were reporting the main line was being forwarded to a cell phone. The Verizon error states that the "wireless customer" is not available.
I validated that the reporting user was indeed using a Verizon mobile phone. Armed with that information I repeated the test from a couple of other Verizon mobile phones and was able to consistently recreate the issue.
Issue:
Verizon Wireless pulled back the call at 60 seconds and played the following error message:
"
Welcome to Verizon wireless. The wireless customer you
called is not available at this time Please try your call again later.
Announcement 1 switch [redacted]
"
Work Around:
Modified the timers on the Cisco Communications Manager. Previously the system was configured to route calls to the auto attendant after 90 seconds. I discussed the issue with the customer and we decided to change the value to 30 seconds. Now, when an operator doesn't pick up the call within 30 seconds, the call is routed to the auto-attendant instead of being disconnected by our friends at Verizon.
This is a collection of my experiences around Cisco Collaboration. These technical notes are for me to look back on and jog my memory of my adventures in Collab. With any luck, they may be helpful for others too. (Your mileage may vary, this is not a replacement for official TAC support from Cisco and all the other usual disclaimers that go along with an unofficial tech blog.)
Tuesday, September 11, 2018
Subscribe to:
Posts (Atom)
Integrating WebEx Calling and Communications Manager Express 2/2
This is the second post in the two post series. It will go into more detail on the configuration of the solutions and workarounds put in pla...
-
This is the second post in the two post series. It will go into more detail on the configuration of the solutions and workarounds put in pla...
-
It's been a long minute since I've run into this particular scenario. Unfortunately, I didn't have the solution in my notes s...
-
Let's say there is a Communications Manager Express and a PSTN SIP trunk to the telco that requires authentication. How does CME bind S...