atcomsystems.ca/forum
Posted By: Motohead LAYER 3 STUFF - 02/15/18 06:17 PM
I have a client on a PRI from Charter Fiber they have switched from pots line service to a full PRI. One of their departments (originally had only 4 pots lines) was being overrun with calls I programmed call by call and 4 GCO keys limited the number of inbound calls to 4 that took care of the incoming call volume problem but now on the 5th call we are getting an intercept from the carrier saying "your call can not be completed at this time" the customer wants a simple busy signal. does anyone know what layer 3 message the CIX 100 R3 sends in this scenario. I'm trying to sound like I know what I'm talking about when I approach Charter
Posted By: Motohead Re: LAYER 3 STUFF - 02/27/18 05:24 PM
Wow 146 views and no responses. Have I stumped the band on this?
Posted By: phonemeister Re: LAYER 3 STUFF - 02/27/18 05:52 PM
Did you assign just 4 channels for the ILG in the call by call section?
Posted By: Motohead Re: LAYER 3 STUFF - 02/27/18 06:18 PM
Correct and on the 5 inbound call instead of a fast busy you get an intercept saying your call can not be completed at this time i’m trying to figure out what message the CIX is sending to the carrier on the D Channel
Posted By: Carlos#1 Re: LAYER 3 STUFF - 02/28/18 03:36 AM
Have you done a Hyperterminal trace of the call off the PRI card?
This will show you what the CIX100 PRI card is sending back to the exchange.
Posted By: newtecky Re: LAYER 3 STUFF - 02/28/18 08:43 AM
Interestingly in the Toshiba KB they have a KB regarding Call-by-Call to limit calls on a PRI with the subject "Fax busy work around for the CTX with PRI only".

Toshiba has a Digitrace utility to capture ISDN messages, but it works about the same as Hyperterminal (or TeraTerm or Putty). That is probably the best way to find out what messages are being sent back to the carrier. You could ask the Charter techs what they see, but the chance is probably pretty low that they will be able to tell you.

Have you tried reducing the B channels to 4 channels?
Posted By: Carlos#1 Re: LAYER 3 STUFF - 02/28/18 11:09 PM
The only difference between Digitrace and Hyper Terminal/Putty/Hercules etc is that it is date and time stamped to help with finding the data quickly.

Connect a TTY cable onto the monitor port of the RPTB/BPTU card and set your capture software to 9600 baud rate, 8 bits, No Parity,1 stop bit and set it to capture the data to a text file.
If you are unsure what you see then send it to one of us to decipher for you.
Tell us the DID number you are dialing and the number you are dialing in from.
Posted By: Carlos#1 Re: LAYER 3 STUFF - 02/28/18 11:11 PM
Originally Posted by Motohead
Wow 146 views and no responses. Have I stumped the band on this?

You will have stumped most but not all of us smile
Posted By: newtecky Re: LAYER 3 STUFF - 03/01/18 02:59 AM
Originally Posted by Carlos#1
Originally Posted by Motohead
Wow 146 views and no responses. Have I stumped the band on this?

You will have stumped most but not all of us smile

I have spent a lot more time looking at SIP trunk messages then I ever did looking at Q.931 messages.
Typical PRI turnup:
4 Digits - Check
NI2 - Check
B8ZS/ESF - Check
Test call. Done

Worse case I still use a third party PRI trace utility that does a great job of visualizing the PRI channels. That way I can tell the telco: "Nope, the call didn't hit my PBX. Check your stuff again".

Posted By: Motohead Re: LAYER 3 STUFF - 03/01/18 09:36 PM
Originally Posted by newtecky
Interestingly in the Toshiba KB they have a KB regarding Call-by-Call to limit calls on a PRI with the subject "Fax busy work around for the CTX with PRI only".

Toshiba has a Digitrace utility to capture ISDN messages, but it works about the same as Hyperterminal (or TeraTerm or Putty). That is probably the best way to find out what messages are being sent back to the carrier. You could ask the Charter techs what they see, but the chance is probably pretty low that they will be able to tell you.

Have you tried reducing the B channels to 4 channels?

Reducing the b channels to four would have a global effect
They have multiple departments.
Posted By: Motohead Re: LAYER 3 STUFF - 03/01/18 09:41 PM
Originally Posted by Carlos#1
Originally Posted by Motohead
Wow 146 views and no responses. Have I stumped the band on this?

You will have stumped most but not all of us smile

But so far I have . smile
No one has answered my question and the job is 2 hours away I was hoping that someone on here had gone through this and would have the answer.
Posted By: Motohead Re: LAYER 3 STUFF - 03/01/18 09:56 PM

Posted By: Carlos#1 Re: LAYER 3 STUFF - 03/02/18 03:57 AM
When I tested it on the bench I got ISDN cause 17 "User busy" explanation is "The called system has acknowledged the connection request but is unable to accept the call because the B channels are in use."

This was the event off the PRI card I captured

17;07'138 Rx:[SAPI]00 C [TEI]000 [FRAME]INFO [N(S)]004 [N(R)]006
PD = Q.931(08)
CR = 02 001E
MT = SETUP(05)
A1 04 03 80 90 A3 18 03 A9 83 83 6C 0B 80 30 32 ...........l..02
39 39 39 39 38 38 38 38 70 05 80 31 32 33 34 99998888p..1234
17;07'149 Tx :[SAPI]00 R [TEI]000 [FRAME]RR [N(R)]005
17;07'151 S DL_DAT_IND
17;07'547 R DL_DAT
17;07'552 Tx :[SAPI]00 C [TEI]000 [FRAME]INFO [N(S)]006 [N(R)]005
PD = Q.931(08)
CR = 02 801E
MT = REL COMP(5A)
08 02 81 91

The 81 91 after the REL COMP(5A)
81 means the private network near the local user (possibly a local private branch exchange [PBX])
91 means User Busy The called system acknowledges the connection request. However, the system cannot accept the call because all B-channels are in use. The user equipment is compatible with the call in this situation.

You need to be talking to the ISDN carrier on how they are responding to our ISDN Q931 disconnect cause codes.

Posted By: phonemeister Re: LAYER 3 STUFF - 03/02/18 10:00 PM
You're too awesome Carlos!
Posted By: Carlos#1 Re: LAYER 3 STUFF - 03/04/18 10:43 PM
Originally Posted by phonemeister
You're too awesome Carlos!

You're welcome

I don't normally give this level of support for free! smile
Posted By: Motohead Re: LAYER 3 STUFF - 03/07/18 03:01 PM
Originally Posted by Carlos#1
When I tested it on the bench I got ISDN cause 17 "User busy" explanation is "The called system has acknowledged the connection request but is unable to accept the call because the B channels are in use."

This was the event off the PRI card I captured

17;07'138 Rx:[SAPI]00 C [TEI]000 [FRAME]INFO [N(S)]004 [N(R)]006
PD = Q.931(08)
CR = 02 001E
MT = SETUP(05)
A1 04 03 80 90 A3 18 03 A9 83 83 6C 0B 80 30 32 ...........l..02
39 39 39 39 38 38 38 38 70 05 80 31 32 33 34 99998888p..1234
17;07'149 Tx :[SAPI]00 R [TEI]000 [FRAME]RR [N(R)]005
17;07'151 S DL_DAT_IND
17;07'547 R DL_DAT
17;07'552 Tx :[SAPI]00 C [TEI]000 [FRAME]INFO [N(S)]006 [N(R)]005
PD = Q.931(08)
CR = 02 801E
MT = REL COMP(5A)
08 02 81 91

The 81 91 after the REL COMP(5A)
81 means the private network near the local user (possibly a local private branch exchange [PBX])
91 means User Busy The called system acknowledges the connection request. However, the system cannot accept the call because all B-channels are in use. The user equipment is compatible with the call in this situation.

You need to be talking to the ISDN carrier on how they are responding to our ISDN Q931 disconnect cause codes.


That is EXACTLY what i was looking for!! Carlos your a god thank you thank You!!!
Posted By: Carlos#1 Re: LAYER 3 STUFF - 03/19/18 05:28 AM
Motohead do you have an update on this issue?
how did you get on resolving this issue with your carrier?
© Sundance Phone System Forums - VOIP & Cloud Phone Help