Timer for E1-R2 (Brazil) channel (Dev type DIUCQ421) get response for outside call

[jarruda]

Hi folks,

I'm trying to found a way to resolve the following issue:

In a setup with this configuration:
-------- ---------- ---------- ----------
| HIPATH | -> | Cisco GW | -> | Cisco GW | -> | Provider |
-------- E1 -------- SIP ---------- E1 ----------

When a phone in the Hipath dial an outside number that call will traverse the first E1 (between Hipath and a Cisco GW) and then after some SIP signaling it will traverse the second E1 connection (between a Cisco GW and the Phone Provider).

The problem is that, if the second leg connection takes more than 15 seconds to ring (from the time that the first Cisco GW have received all the E1 signaling) the Hipath will disconnect the call.
If the second start to rings before 15 seconds then the call will work fine. The 15 seconds is very consistent, happens every time.

I suspect that this is some kind of configurable timer in the Hipath that could be increased but I already looked for many of them (PTIME, CTIME, DTIM1, DTIM2) and after changing all the ones I thought that would work I run out of ideas.

Anyone have some suggestion to share about where I can look for increase this "timer"?

Regards,
Joao Arruda

 

[sbcsu]

You could do a trace on the circuit on the HiPath end.

There is a document HERE which might assist.

 

[jarruda]

sbcsu,

The only way to do the trace is using the Assistant right?
Do you think the trace would tell which timer to look for?

I saw the doc you sent, it do not cover much of this kind of E1 signalling issue.

Regards,
Joao Arruda

 

[sbcsu]

Hi Joao,
Well there are more detailed Hard Disk traces but the Assistant trace will point you in the right direction.
It will tell you where the disconnect signal is coming from.
It could be from the Cisco

If you have time you could setup the system as in the document to see if that works as it could be one of the COT/COP parameters which are failing the call.

 

[jarruda]

sbcsu,

Do you have any instructions on how do get those "Hard Disk traces"?
I need to check if I have any Assistant working at all and I didn't know that there is another way to trace calls.

I did a full debug on the Cisco GW to check this.. and it seems that the disconnect signal is really coming from the Hipath side.

Thanks again.

 

[sbcsu]

Hi,
No those traces would normally be requested by upper level support.
You could try using a 2MB tester which would tell you as well on it's screen if you can access one?

The assistant should be working in every system.

http://192.0.2.5

Go through client preparation

If you have problems then use Windows 7 and make up a Virtual XP from Microsoft.
Use that Virtual XP to log on to the Assistant.

What version of HiPath are you working on
Comwin/Macro/Retreive System Variant ?

 

[jarruda]

sbcsu,

Here is the result for Comwin/Macro/Retreive System Variant:

<HicomLanguage=English
DISPLAY-VEGAS:LIST=SHORT,UNIT=SWU&ADS;
DISPLAY-VEGAS:LIST=SHORT,UNIT=SWU&ADS;
H500: AMO VEGAS STARTED
SYSTEM NO. AMO APS NO. START USER STATUS
SWU: L31903Q8031A00001 REGEN P30252B4300B00113 04.11.14 09:19 041114 FINISHED
ADS: L31903Q8031A00001 REGEN P30252B4300A00113 04.11.14 09:40 041114 FINISHED
AMO-VEGAS-111 ADMIN. OF DATABASE GENERATION RUNS ON SUPPORT SYSTEM
DISPLAY COMPLETED;
<HicomVariant=UV1.0-SA13

 

[jarruda]

Just for reference,

I was able to resolve the issue. It turns out that I was reaching two 15 seconds timer.

1) The first one was in the Cisco GW (that's why trying many changes in Hipath side didn't fix the issue).

The configuration to be changed was alert-wait-time (Time to wait for alert indication for incoming R2 calls. Default is 15 seconds.)
This doc was helpfull to find that:

http://www.cisco.com/c/en/us/support/docs/voice/digital-cas/53049-e1-r2-cookbook.html

Increasing that timer (to 30 seconds) is easy as:

[pre]controller E1 0/0/0
cas-custom 0
alert-wait-time 30
[/pre]​

Even after changing this, the call still drops after 15 seconds, then I got back to the Siemens configuration
​

2) The second timer was in the Siemens MFCTA AMO, type MFCVAR opt SUPERV.

The configuration to be changed was SIGLENF from 15000 to 30000.

[pre]CHANGE-MFCTA:MFCVAR=3,TYPE=MFCVAR,OPT=SUPERV,SIGLENF=30000;[/pre]​

(This command did the trick, considering that MFCVAR 3 is the configured value in TACSU)
​

After both timers got increased now the call works fine!!!

 

[sbcsu]

Great, well sorted out.
Glad you are now OK.
The Brazil kit always had a specific setup from the memory of TMCOW days.