CS1000 PBX - Issue with Incoming calls - Very sporadic

[babytech2009]

I am still having the issue with very sporadic calls not clearing incoming to the site.

I have had the carrier monitor the site 2 times and did not see any issue on the PRI at all.


I turned on dchannel MSGI and so far this is all I see.


DCH 22 UIPE_IMSG CC_RELEASE_IND REF 00004519 CH 22 1 TOD 10:07:56 CK DDA91F8E


DCH000
.

DCH000
.
DCH 22 UIPE_IMSG CC_SETUP_IND REF 00004C82 CH 22 1 TOD 10:08:52 CK DDAAD93F
CALLED #:45315 NUM PLAN: UNKNOWN TON: UNKNOWN
CALLING #:7038947331 NUM PLAN: E164 TON: NATL

DCH 22 UIPE_IMSG CC_DISC_IND REF 00004C82 CH 22 1 TOD 10:09:01 CK DDAB1DD9
CAUSE: #16 - NORMAL CALL CLEARING

DCH 22 UIPE_IMSG CC_RELEASE_CONF REF 00004C82 CH 22 1 TOD 10:09:01 CK DDAB1E2D

DCH 22 UIPE_IMSG CC_SERVICE_IND REF 00000000 TOD 10:09:48 CK DDAC8B0A
STATUS: IN SERVICE

DCH 22 UIPE_IMSG CC_SETUP_IND REF 0000141B CH 22 1 TOD 10:09:48 CK DDAC8C10
CALLED #:45303 NUM PLAN: UNKNOWN TON: UNKNOWN
CALLING #:7026062669 NUM PLAN: E164 TON: NATL

DCH 22 UIPE_IMSG CC_SETUPCOMP_IND REF 0000141B CH 22 1 TOD 10:09:55 CK DDACC3AF

DCH 22 UIPE_IMSG CC_RELEASE_IND REF 0000141B CH 22 1 TOD 10:11:49 CK DDB03F2D

DCH 22 UIPE_IMSG CC_PROCEED_IND REF 00004352 CH 22 22 TOD 10:12:05 CK DDB0BF11

DCH 22 UIPE_IMSG CC_ALERT_IND REF 00004352 CH 22 22 TOD 10:12:07 CK DDB0D10B
PROGRESS: INBAND INFO OR PATTERN IS AVAIL

DCH 22 UIPE_IMSG CC_SETUP_CONF REF 00004352 CH 22 22 TOD 10:12:11 CK DDB0E74F

DCH 22 UIPE_IMSG CC_SERVICE_IND REF 00000000 TOD 10:12:19 CK DDB127E6
STATUS: IN SERVICE

DCH 22 UIPE_IMSG CC_PROCEED_IND REF 00004353 CH 22 21 TOD 10:12:23 CK DDB143FB

DCH 22 UIPE_IMSG CC_PROGRESS_IND REF 00004353 CH 22 21 TOD 10:12:23 CK DDB14413
PROGRESS: INBAND INFO OR PATTERN IS AVAIL
CAUSE: #1 - UNASSIGNED NUMBER

DCH 22 UIPE_IMSG CC_RELEASE_IND REF 00004353 CH 22 21 TOD 10:12:37 CK DDB1B4F5

DCH 22 UIPE_IMSG CC_PROCEED_IND REF 00004354 CH 22 21 TOD 10:12:45 CK DDB1F455

DCH 22 UIPE_IMSG CC_PROGRESS_IND REF 00004354 CH 22 21 TOD 10:12:47 CK DDB2077C
PROGRESS: INBAND INFO OR PATTERN IS AVAIL

DCH 22 UIPE_IMSG CC_SETUP_CONF REF 00004354 CH 22 21 TOD 10:12:59 CK DDB267A8

DCH 22 UIPE_IMSG CC_SERVICE_IND REF 00000000 TOD 10:14:27 CK DDB5189E
STATUS: IN SERVICE

DCH 22 UIPE_IMSG CC_SERVICE_IND REF 00000000 TOD 10:16:39 CK DDB91457
STATUS: IN SERVICE

DCH 22 UIPE_IMSG CC_RELEASE_IND REF 00004352 CH 22 22 TOD 10:17:07 CK DDB9F9D1

DCH 22 UIPE_IMSG CC_RELEASE_IND REF 00004354 CH 22 21 TOD 10:17:09 CK DDBA0336

DCH 22 UIPE_IMSG CC_RELEASE_IND REF 00004351 CH 22 23 TOD 10:18:29 CK DDBC76BD

DCH 22 UIPE_IMSG CC_SERVICE_IND REF 00000000 TOD 10:19:07 CK DDBDA4A2
STATUS: IN SERVICE

DCH 22 UIPE_IMSG CC_PROCEED_IND REF 00004355 CH 22 23 TOD 10:19:33 CK DDBE6A19

DCH 22 UIPE_IMSG CC_PROGRESS_IND REF 00004355 CH 22 23 TOD 10:19:33 CK DDBE6E02
PROGRESS: INBAND INFO OR PATTERN IS AVAIL
CAUSE: #1 - UNASSIGNED NUMBER

DCH 22 UIPE_IMSG CC_RELEASE_IND REF 00004355 CH 22 23 TOD 10:19:45 CK DDBEC208

DCH 22 UIPE_IMSG CC_PROCEED_IND REF 00004356 CH 22 23 TOD 10:20:53 CK DDC0DA7F

DCH 22 UIPE_IMSG CC_PROGRESS_IND REF 00004356 CH 22 23 TOD 10:20:55 CK DDC0E50F
PROGRESS: CALL IS NOT END TO END ISDN
CAUSE: #127 - INTERNETWORKING UNSPECIFIED


DCH 22 UIPE_IMSG CC_SETUP_CONF REF 00004356 CH 22 23 TOD 10:21:05 CK DDC13B00

DCH 22 UIPE_IMSG CC_SERVICE_IND REF 00000000 TOD 10:21:07 CK DDC150A1
STATUS: IN SERVICE

DCH 22 UIPE_IMSG CC_RELEASE_IND REF 00004356 CH 22 23 TOD 10:21:59 CK DDC2D9E5

DCH 22 UIPE_IMSG CC_SERVICE_IND REF 00000000 TOD 10:23:09 CK DDC4FAFD
STATUS: IN SERVICE


I dont see anything so far that would warrent an issue with the PRI on our side.

Any ideas or advise on what to look for?



Thank you in advance

 

[babytech2009]

I am still monitoring the PRI on the PBX however I dont see any issues occuring. I asked the site for a date and time and call to and from number.

However I dont have any information


DCH 22 UIPE_IMSG CC_SETUP_IND REF 00004D19 CH 22 3 TOD 11:09:38 CK DE1A3DB3
CALLED #:45332 NUM PLAN: UNKNOWN TON: UNKNOWN
CALLING #:7753347601 NUM PLAN: E164 TON: NATL

DCH 22 UIPE_IMSG CC_SERVICE_IND REF 00000000 TOD 11:09:48 CK DE1A7FF3
STATUS: IN SERVICE

DCH 22 UIPE_IMSG CC_DISC_IND REF 00004D19 CH 22 3 TOD 11:09:58 CK DE1AD2CD
CAUSE: #16 - NORMAL CALL CLEARING

DCH 22 UIPE_IMSG CC_RELEASE_CONF REF 00004D19 CH 22 3 TOD 11:09:58 CK DE1AD392

DCH 22 UIPE_IMSG CC_SETUP_IND REF 00004786 CH 22 3 TOD 11:12:00 CK DE1E84D7
CALLED #:45313 NUM PLAN: UNKNOWN TON: UNKNOWN
CALLING #:5202032717 NUM PLAN: E164 TON: NATL

DCH 22 UIPE_IMSG CC_SERVICE_IND REF 00000000 TOD 11:12:18 CK DE1F1CC6
STATUS: IN SERVICE

DCH 22 UIPE_IMSG CC_SETUPCOMP_IND REF 00004786 CH 22 3 TOD 11:12:20 CK DE1F2747

DCH 22 UIPE_IMSG CC_DISC_IND REF 00004786 CH 22 3 TOD 11:12:32 CK DE1F7EE1
CAUSE: #16 - NORMAL CALL CLEARING

DCH 22 UIPE_IMSG CC_RELEASE_CONF REF 00004786 CH 22 3 TOD 11:12:32 CK DE1F7FA6

DCH 22 UIPE_IMSG CC_SETUP_IND REF 00005293 CH 22 3 TOD 11:13:06 CK DE209260
CALLED #:45314 NUM PLAN: UNKNOWN TON: UNKNOWN
CALLING #:5202032717 NUM PLAN: E164 TON: NATL

DCH 22 UIPE_IMSG CC_SETUP_IND REF 00000311 CH 22 4 TOD 11:13:06 CK DE2093F1
CALLED #:38756 NUM PLAN: UNKNOWN TON: UNKNOWN
CALLING #:7025779421 NUM PLAN: E164 TON: NATL

DCH 22 UIPE_IMSG CC_SETUPCOMP_IND REF 00000311 CH 22 4 TOD 11:13:08 CK DE209BDD

DCH 22 UIPE_IMSG CC_SETUPCOMP_IND REF 00005293 CH 22 3 TOD 11:13:12 CK DE20BA63

DCH 22 UIPE_IMSG CC_DISC_IND REF 00000311 CH 22 4 TOD 11:13:12 CK DE20BD27
CAUSE: #16 - NORMAL CALL CLEARING

DCH 22 UIPE_IMSG CC_RELEASE_CONF REF 00000311 CH 22 4 TOD 11:13:12 CK DE20BDE9

DCH 22 UIPE_IMSG CC_SERVICE_IND REF 00000000 TOD 11:14:28 CK DE231245
STATUS: IN SERVICE

DCH 22 UIPE_IMSG CC_SERVICE_IND REF 00000000 TOD 11:16:28 CK DE26BCA1
STATUS: IN SERVICE

DCH 22 UIPE_IMSG CC_SERVICE_IND REF 00000000 TOD 11:18:59 CK DE2B5AF6
STATUS: IN SERVICE

 

[babytech2009]

here is the call and when i am looking on the system i dont see the error for this.

Any other avenue to look at?



Calling from 702-577-9405

Calling to 702-914-5315
DCH 22 UIPE_IMSG CC_SETUP_IND REF 00000311 CH 22 4 TOD 11:13:06 CK DE2093F1
CALLED #:38756 NUM PLAN: UNKNOWN TON: UNKNOWN
CALLING #:7025779421 NUM PLAN: E164 TON: NATL

DCH 22 UIPE_IMSG CC_SETUPCOMP_IND REF 00000311 CH 22 4 TOD 11:13:08 CK DE209BDD

DCH 22 UIPE_IMSG CC_SETUPCOMP_IND REF 00005293 CH 22 3 TOD 11:13:12 CK DE20BA63

DCH 22 UIPE_IMSG CC_DISC_IND REF 00000311 CH 22 4 TOD 11:13:12 CK DE20BD27
CAUSE: #16 - NORMAL CALL CLEARING

DCH 22 UIPE_IMSG CC_RELEASE_CONF REF 00000311 CH 22 4 TOD 11:13:12 CK DE20BDE9

DCH 22 UIPE_IMSG CC_SERVICE_IND REF 00000000 TOD 11:14:28 CK DE231245
STATUS: IN SERVICE

DCH 22 UIPE_IMSG CC_SERVICE_IND REF 00000000 TOD 11:16:28 CK DE26BCA1
STATUS: IN SERVICE

DCH 22 UIPE_IMSG CC_SERVICE_IND REF 00000000 TOD 11:18:59 CK DE2B5AF6
STATUS: IN SERVICE

 

[yyrkroon]

I am still having the issue with very sporadic calls not clearing incoming to the site. <---- what exactly does this mean, what's the actual reported symptoms/problem

 

[babytech2009]

yyrkroon

when the call comes in they get an all circuits are busy. It is limited to maybe 1-3 times every month and its not anything that the carrier noticed on the PRI side when i had it monitored.

I asked the site to send me the entire messages they recieve. However they hear the message and hangup. It doesnt repeat the message once they hang up and try again so I dont get full detail and since the carrier monitored the PRI i cannot tell what is causing the issue.

 

[yyrkroon]

Unless you or someone added the recording "all circuits are busy" to your system...this is a telco recording. If the caller is hearing this, they didn't make it to your switch,so you're not going to see anything on the DCH messaging, and they may not have made it to your circuit provider either.

This recording could be from the caller telco, the hand-off telco/second teir/upper level telco...depends on and where and how the call is being routed.

Good luck chasing this down.

 

[babytech2009]

yykroon,

Thank you. It has been a pain to chase down so far. I have told them it is not our system. Because if they can get through after a retry it is either the cell carrier or the carrier at the location they are calling from.

Making people understand doesnt seem to work in the field that we are in. I mean even house phones have the issue at times.
And what is a normal human response, either check the number you are calling to verify you entered it correectly. Or to call back and see if you get through the next time.

 

[jaxuser]

as yyrkroon said, this is a Telco issue. When I encounter this type of complaint from customers, I tell them that there is no little man or woman sitting inside their PBX giving out "all circuits busy" recordings; these recordings are coming from the Telco and if they listen to the entire recording, sometimes there is a number at the end that Telco can use in helping them track down where the failure is.

 

[EddieDuece]

This ususally happens when your circuit drops, but you should see the error messages when that happens. We did however add a intercept that if the circuit drops, tells tells the caller we are expriencing difficulties and please call back.

 

[babytech2009]

EddieDuece,

Our system is not programmed that way but I did MSGO and MSGI on the PRI's. Even had the carrier monitor. No errors on the Dchannel or Loops.

I have told the site repeated times that it could be a cell carrier or the site of the calling party's issue not our PBX.

 

[EddieDuece]

If your spans go down, then you would know......I'd say the problem is on the calling parties side.

 

[babytech2009]

jaxuser (TechnicalUser)10 Mar 15 16:17
as yyrkroon said, this is a Telco issue. When I encounter this type of complaint from customers, I tell them that there is no little man or woman sitting inside their PBX giving out "all circuits busy" recordings; these recordings are coming from the Telco and if they listen to the entire recording, sometimes there is a number at the end that Telco can use in helping them track down where the failure is. >>>>>>>>>>>>>>>>>>>>>>>ONLY IF IT WERE THAT EASY! HAHA! I tried to tell them no leprechauns or gremlins in our equipment!


Thank you all for the responses!