Re: [Bayonne-devel] Globalcall issues with 1.2.15

[Anthony DeRobertis]

On Thu, 2005-11-17 at 16:31 -0500, David Sugar wrote:
> Hmm...we are missing EventError!  How very odd...I would suggest
> commenting out the reference to it in line 578 in driver.cpp.

That might have something to do with this changelog entry:

Changes from 1.2.13 to 1.2.14
- more sunrpc updates.
- EventError removed from gc driver...
- Some build fixes...
- fix for dialogic driver counting
- audioconferencing in globalcall driver

I commented out the call to it, and now (no idea if this is related or
not) Bayonne does not seem to notice incoming calls. Here is what it
spits out. "SigInfo length= 26" is approximately when the call came in;
eventually I get a fast busy(?) on the telephone.

scheduler starting...
SigInfo length= 26
4
3
ffffff80
ffffff90
ffffffa2
18
3
ffffffa9
ffffff83
ffffff86
1e
2
ffffff82
ffffff83
6c
c
21
ffffff83
37
30
33
34
33
30
37
34
39
39
70
8
ffffffc1
34
31
34
35
39
32
34
extraitPossibilite : Possibilite parsing 
No commande Possibilite
1a4
scheduler starting...
server: checking cache...
scheduler starting...


If I hang up before the error tone, this is what Bayonne spits out
(starting with the "No commande Possibilite" message):

...
No commande Possibilite
1a4
cc
dx(7): hangup
dx(7): release
trunk.cpp releaseCall: releasing CRN: 6000019 OK state=1
: IDLE TRUNK_ENTER_STATE: call waiting HDL:19 CRN:6000019
64
dx(7): ring
dx(7): error accepting
dx(7): hangup
dx(7): gc_DropCall 42 Invalid call reference number has been used
dx(7): gc_GetCallState(6000019) == FAILURE
: IDLE TRUNK_ENTER_STATE HDL:19 CRN:6000019
trunk.cpp releaseCall: releasing CRN: 6000019 FAILED state=0
dx(7): gc_ReleaseCallEx 42 Invalid call reference number has been used
dx(7): idle
: IDLE TRUNK_ENTER_STATE HDL:19 CRN:ffffffff
dx(7): idle
scheduler starting...