cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1211
Views
10
Helpful
1
Replies

CER - Onsite Alerts failing

tina.hopper
Level 1
Level 1

Hi all:

 

Have recently deployed CER 12.5.1, and all was working fine until we added a new site.

 

This site has multiple onsite alerts (about 9) that they all state are mandatory to receive telephone and email notifications. We just tested 911 today, and only one person out of the 9 received a telephone alert for the 911 call.  For the rest, checking the logs, I see the following error from JTAPI:

 

9087943: Apr 14 10:37:09.279 EST %CER-CER_TELEPHONY-3-ERROR:com.cisco.jtapi.PlatformExceptionImpl: Could not meet post conditions of connect()
com.cisco.jtapi.CallImpl.connect(CTQF)
com.cisco.e911.server.telephony.skate.UnisonCMSpecificClass.connectCall(UnisonCMSpecificClass.java:24)
com.cisco.e911.server.telephony.E911TapiPort.connectCall(E911TapiPort.java:590)
com.cisco.e911.server.telephony.E911TapiPort.makeCall(E911TapiPort.java:475)
com.cisco.e911.server.telephony.OutboundCallInitiator.initiateOutboundCall(OutboundCallInitiator.java:56)
com.cisco.e911.server.telephony.OutboundCallInitiator.run(OutboundCallInitiator.java:30)
java.lang.Thread.run(Thread.java:748)

 

293941: Apr 14 10:37:09.278 EST %JTAPI-JTAPIIMPL-7-UNK:{(P3-cerctiuser) GCID=(2,15105)->ACTIVE} CallManager.processCallStateChange: Handling STATE_DISCONNECTED for 5550025:E911:1 Cause: Other: 109

 

Not sure what 109 cause code is for JTAPI, so if anyone knows, please pass it on.

 

All CTI ports are registered, no CSS/PT config has changed at all.  For the working call, it uses another CTI port, but succeeds - it was the third alert in the list, from the top:

 

294117: Apr 14 10:37:11.485 EST %JTAPI-CTI-7-UNK:(P3-cerctiuser){Line:CER5550026:5550026:E911:(2,476)|Call:[GCID=(15106/2),CID=47589259]} CallStateChanged (V2) [state=RINGBACK cause=NOERROR

 

294119: Apr 14 10:37:11.485 EST %JTAPI-JTAPIIMPL-7-UNK:{(P3-cerctiuser) GCID=(2,15106)->ACTIVE} CallManager.processCallStateChange: Handling STATE_RINGBACK for 5550026:E911:1 Cause: CAUSE_NORMAL
294120: Apr 14 10:37:11.485 EST %JTAPI-CTI-7-UNK:{ALL EXTERNAL ADDRESSES|Call:(P3-cerctiuser) GCID=(2,15106)->ACTIVE} ExternalCallStateChanged [ state=ACCEPTED cause=100 processEvent= reason =1 ]

 

I suppose I have two questions then:

 

What is cause code 109 for the failed call?

Is it possible this site just needs to use one alert contact - is there a limit on CER to the # of onsite alerts?  I did not see anything in the documentation but I think 9 is a bit excessive.

 

We'll be rebooting the box at some point and/or resetting the CTI ports after hours but any help would be appreciated here.

 

UPDATE:

 

As soon as I posted this, I realized all the other alerts that were failing were going to phones forwarded to cell phones (staff are mostly WFH due to COVID).  CSS on the ports don't include any PSTN gateways, so I'm guessing that's why it's failing.  The one phone that was getting the alert was not forwarded.  I don't have access to any CUCM logs so can't verify.

 

So now my sanity-check question is...CER should be able to dial outbound as long as there's a route pattern pointing to a valid PSTN gateway?  

 

TIA

1 Reply 1

scheived
Level 3
Level 3

CER will not follow a call forward for Onsite alert number. Not sure of a workaround I've noticed this issue as well.