Works ECT on HICOM 300?

Works ECT on HICOM 300?

Post by Michael Hüthe » Sun, 24 Sep 2000 04:00:00



Hi all,

I try to forward a received phone connection via ECT to another phone number
(user). I set the first connection to hold, make a new connection to the
second user and initiated the ECT message handle. When I use the ECP I got
the following trace:

FACILITY_REQ               ID=001 #0x000d LEN=0022     03:20:51:44
  Controller/PLCI/NCCI            = 0x10201
  FacilitySelector                        = 0x3
  FacilityRequestParameter         = <06 00 04 01 01 00 00>

FACILITY_CONF              ID=001 #0x000d LEN=0022     03:20:51:48
  Controller/PLCI/NCCI            = 0x10201
  Info                                         = 0x0
  FacilitySelector                        = 0x3
  FacilityConfirmationParameter   = <06 00 02 00 00>

FACILITY_IND               ID=001 #0x02b4 LEN=0020     03:20:55:47
  Controller/PLCI/NCCI            = 0x201
  FacilitySelector                        = 0x3
  FacilityIndicationParameter      = <06 00 02 e6>4

I must wait 4sec. till for the message Facility_ind. Is that normal? And
what's the meaning of  Facility Indication Parameter for this case?
When I use ICT I got the same values for the Facility Indication Parameter.

Can someone help me?

Tia,

Michael

P.S.: I work with 2 AVM B1 Controller and a Siemens HICOM 300

 
 
 

Works ECT on HICOM 300?

Post by Vlad » Sun, 24 Sep 2000 04:00:00



Quote:> Hi all,

> I try to forward a received phone connection via ECT to another phone
number
> (user). I set the first connection to hold, make a new connection to the
> second user and initiated the ECT message handle. When I use the ECP I got
> the following trace:

> FACILITY_REQ               ID=001 #0x000d LEN=0022     03:20:51:44
>   Controller/PLCI/NCCI            = 0x10201
>   FacilitySelector                        = 0x3
>   FacilityRequestParameter         = <06 00 04 01 01 00 00>

> FACILITY_CONF              ID=001 #0x000d LEN=0022     03:20:51:48
>   Controller/PLCI/NCCI            = 0x10201
>   Info                                         = 0x0
>   FacilitySelector                        = 0x3
>   FacilityConfirmationParameter   = <06 00 02 00 00>

> FACILITY_IND               ID=001 #0x02b4 LEN=0020     03:20:55:47
>   Controller/PLCI/NCCI            = 0x201
>   FacilitySelector                        = 0x3
>   FacilityIndicationParameter      = <06 00 02 e6>4

Hi Michael

Yes, ECT works on Hicom 300, i have Hicom 150 Office COM thought, but that
shouldn't matter

ECT: PLCI parameter in ECT req must contain new connection PLCI you made and
FacilityRequestParam must contain  the held connection PLCI. Nothing can go
wrong if you coded the structure correctly and your capi works correctly

 
 
 

Works ECT on HICOM 300?

Post by Hans-Juergen Ortman » Tue, 26 Sep 2000 04:00:00


On Sat, 23 Sep 2000 16:26:23 +0200, "Michael Hther"


>Hi all,

>I try to forward a received phone connection via ECT to another phone number
>(user). I set the first connection to hold, make a new connection to the
>second user and initiated the ECT message handle. When I use the ECP I got
>the following trace:

>FACILITY_REQ               ID=001 #0x000d LEN=0022     03:20:51:44
>  Controller/PLCI/NCCI            = 0x10201
>  FacilitySelector                        = 0x3
>  FacilityRequestParameter         = <06 00 04 01 01 00 00>

>FACILITY_CONF              ID=001 #0x000d LEN=0022     03:20:51:48
>  Controller/PLCI/NCCI            = 0x10201
>  Info                                         = 0x0
>  FacilitySelector                        = 0x3
>  FacilityConfirmationParameter   = <06 00 02 00 00>

>FACILITY_IND               ID=001 #0x02b4 LEN=0020     03:20:55:47
>  Controller/PLCI/NCCI            = 0x201
>  FacilitySelector                        = 0x3
>  FacilityIndicationParameter      = <06 00 02 e6>4

>I must wait 4sec. till for the message Facility_ind. Is that normal? And
>what's the meaning of  Facility Indication Parameter for this case?

please, first just read the CAPI spec (Part III, p. 11/12):
 FACILITY_IND->FacilityIndParameter->SupplementaryReason: 0x34E6
0x34xx: you have to look at ETS 300102 to interpret this cause value:
'timeout'.
up to here everthing can be found in CAPI and ETSI specs.

why timeout ? it seems, your PABX does not support ECT

--
Hans-Juergen Ortmann

 
 
 

Works ECT on HICOM 300?

Post by Thomas Wintergers » Tue, 26 Sep 2000 04:00:00


Hi Michael,

ECT works on a HICOM 300 with at least software 3.6 (or 2.0 for HICOM
300E). All PBXes I know only support implicit invokation of ECT, so use
the PLCI for the held connection in both the message header _and_ the
facility-request parameter.

--
Thomas Wintergerst

 
 
 

Works ECT on HICOM 300?

Post by Michael Joos » Wed, 27 Sep 2000 04:00:00



> All PBXes I know only support implicit invokation of ECT, ...

In this case be prepared that it is not possible to handle two channels
simultaneously, as the PBX will (must) reject either the HOLD, the
consultation call or the transfer command. This is caused by the fact
that CAPI cards support only one TEI, and there would be an ambiguity
for the PBX if there is more than one active call per "user" (TEI).
See ETS 300 369.

The solution is
- to use two ISDN controllers per line
- to have ISDN controllers that support two TEIs (implemented as two
virtual controllers per line interface)
- to have the PBXes implement ECT Explicit Linkage

Michael

 
 
 

Works ECT on HICOM 300?

Post by Michael Hüthe » Wed, 27 Sep 2000 04:00:00


Hi Michael,

can you give me a tip where I can find more information about the following
solutions?

Quote:> - to use two ISDN controllers per line

How can I use two ISDN controllers per line, they have several MSN's and use
several lines?

Quote:> - to have ISDN controllers that support two TEIs (implemented as two
> virtual controllers per line interface)

Which company produce these controllers?

Tia,

 Michael

 
 
 

Works ECT on HICOM 300?

Post by Michael Joos » Wed, 27 Sep 2000 04:00:00



> can you give me a tip where I can find more information about the
> following solutions?

> > - to use two ISDN controllers per line
> How can I use two ISDN controllers per line, they have several MSN's
> and use several lines?

I guess I don't understand this question. What is 'several lines' ?
The idea is to attach two controllers to the same line (P-MP bus
structure). This is independent of the use of MSNs, both can listen to
the same, or to individual MSNs.

Quote:> > - to have ISDN controllers that support two TEIs (implemented as two
> > virtual controllers per line interface)
> Which company produce these controllers?

A good question, which I also very much would like to see answered.
I guess there are currently none, as this problem raised only recently.
The implementation of 'virtual' controllers would avoid the need to
change the CAPI interface. For the application it would quite ideally
look the same as the first alternative, but the costs for hardware and
installation would be half.
A response I got was that it would be better to convince the PBX vendors
for the third alternative, but I don't expect that this is a workable
solution, at least not in this decennium.

Michael

 
 
 

Works ECT on HICOM 300?

Post by Thomas Wintergers » Wed, 27 Sep 2000 04:00:00


Hi Michael,



> > All PBXes I know only support implicit invokation of ECT, ...

> In this case be prepared that it is not possible to handle two channels
> simultaneously, as the PBX will (must) reject either the HOLD, the
> consultation call or the transfer command. This is caused by the fact
> that CAPI cards support only one TEI, and there would be an ambiguity
> for the PBX if there is more than one active call per "user" (TEI).
> See ETS 300 369.

> The solution is
> - to use two ISDN controllers per line
> - to have ISDN controllers that support two TEIs (implemented as two
> virtual controllers per line interface)

Another solution is to hold back the 2nd ECT request until the first is
done (assumed there are two concurrend calls to transfer). If you do the
ECT request in the alerting phase of the outgoing call the 2nd caller
does not have to wait for long.

Quote:> - to have the PBXes implement ECT Explicit Linkage

This would be very nice. Do you know any PBXs supporting this?

Or could you direct Siemens, Alcatel and others to implement this in
their PBXs? ;-) / :-((

--
Thomas Wintergerst

 
 
 

Works ECT on HICOM 300?

Post by Michael Joos » Thu, 28 Sep 2000 15:00:57



> Another solution is to hold back the 2nd ECT request until the first
> is done (assumed there are two concurrend calls to transfer). If
> you do the ECT request in the alerting phase of the outgoing call
> the 2nd caller does not have to wait for long.

Unfortunately, this is not a general solution. As I explained in my
first writing, some PBX already block a possible ambiguity quite early,
when you try to make the 2nd HOLD, or when you try to make a 2nd
consultation call. Since in some applications a consultation call may
last non-negligible time, there is significant impact on the other call.
For example, if the application tries several alternative extensions
from a list until a successful connect, it has to wait in each try until
the consultation call is answered, or a 'reasonable' timeout occurs.

Furthermore, it would require significant changes to the state machine
to implement such delays, and it is not rather a modular design to
implement such inter-call dependencies.

Quote:> > - to have the PBXes implement ECT Explicit Linkage
> This would be very nice. Do you know any PBXs supporting this?
> Or could you direct Siemens, Alcatel and others to implement this in
> their PBXs? ;-) / :-((

Sure, no problem.   ;-)
Unfortunately, I (and others) recently spend significant time just to
find out whether or not ECT would be implemented in their currently
existing releases. This seems to be one of the most secured secrets (or
they don't know themselves).
BTW, yes, I have really seen a (experimental) version of ECT Explicit
Linkage, but I am not to expose details (but you've already mentioned
them).

Michael

 
 
 

Works ECT on HICOM 300?

Post by Michael Hüthe » Tue, 03 Oct 2000 04:00:00


Hi all,

I've solved my problem. ECT works on HICOM 300, but you need the software
version 3.6. I had a meeting with some technicans from Siemens and tested my
application on their PBX.

Thanks all for the help

     Michael

 
 
 

1. Siemens Hicom 300 / Hicom Trading 300

I am interested in technical information on the Siemens PBX Hicom 300
and especially the Hicom Trading 300. Although these products are not
currently being produced for larger-scale domestic use, I imagine
there is a certain amout of information available here. I would really
appreciate any help on this topic.

Thanks,


2. EMAIL Server Virus Detectio Software

3. Siemens Hicom 300 E and Siemens Hicom 300 H

4. Quitting Threaded App

5. Tips and tricks for HICOM 300

6. Clean install

7. More Hicom 300 problems

8. Euro ISDN standard - 300 403 or 300 102

9. ECT with AVM Fritz/DSL doesn′t work but 3 PTY works !

10. Getting EnterNet 300 and Linksys Router working

11. Only EnterNET 300 Works !!!???