bayonne-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Bayonne-devel] Global Call outbound call problem resolution


From: Gilmore, Gerry
Subject: RE: [Bayonne-devel] Global Call outbound call problem resolution
Date: Wed, 8 Dec 2004 11:54:46 -0800

Julien,

 

Here’s what you need to do: (BTW, for the best GC examples – IMNSHO - J look at gcdiag)

 

When initializing, issue gc_ResetLineDev() as a response to the GCEV_UNBLOCKED event. When you get the GCEV_RESETLINEDEV event, issue gc_WaitCall() *once*. This “primes the pump” for GC to be able to accept an incoming call, so long as the linestate is idle.


>From there, you can issue gc_MakeCall() to make an outbound call whenever you want. Any incoming calls will still be answered as normal, again as long as the line is idle.

 

So, to recap, yes! *only* issue gc_WaitCall() *once*, in response to the GCEV_RESETLINEDEV, and then all should be well.

 

Gerry

 

There are 10 kinds of people in the world, those who understand binary and those who don't.

 

Gerry Gilmore

Field Applications Engineer

Intel Corporation

(http://www.intel.com)

 


From: address@hidden [mailto:address@hidden On Behalf Of Julien Chavanton
Sent: Wednesday, December 08, 2004 2:16 PM
To: Julien Chavanton; address@hidden
Subject: RE: [Bayonne-devel] Global Call outbound call problem resolution

 

Sorry this was wrong:  Bayonne/Globalcall Drivers use gc_openex() When using gc_openex() we do not need to issue gc_waitcall()

 

But still I did found the problem it does take place when we call gc_waitcall() several time without necessity

This could have made no problem but it looks like it is wasting a CRN every time.

 

I have to find the proper modification because we still need to invoque gc_waitcall() after a gc_resetlinedev()

 

I will make intensive testing and post the result.

Julien

 


From: address@hidden [mailto:address@hidden On Behalf Of Julien Chavanton
Sent: December 7, 2004 1:42 PM
To: address@hidden
Cc: address@hidden
Subject: [Bayonne-devel] Global Call outbound call problem resolution

 

Following the recommendation of Mark Lipscombe I now revert to Dialogic Drivers.

 

And finally good news, I have found the problem with outbound call with Globalcall

 

1 – Bayonne/Globalcall Drivers use gc_openex() When using gc_openex() we do not need to issue gc_waitcall()

2 – Bayonne/Globalcall was also make gc_waitcall() every calls this is not the normal behavior.

 

I have commented gc_waitcall() from trunk.cpp

 

Before bayonne was receiving makecall failed with: invalid CRN as been used every 31 calls now no problem !!

 

I will now revert to globalcall since this was the only known bug and dialogic drivers are not realy fine.

 

Julien

 

 


reply via email to

[Prev in Thread] Current Thread [Next in Thread]