Cool, May we have this modif ?
Le mercredi 17 Août 2005 21:17, Julien Chavanton a écrit :
I have made modification to Bayonne Globalcall to remove CRN
modification from outside driver.cpp (the Dialogic event handler)
This way the CRN is always correct.
I am stressing the port as much as I can.
I have good result.
_____
From: Julien Chavanton
Sent: August 17, 2005 10:25 AM
To: 'address@hidden'
Subject:
While debugging and stressing Bayonne1 / Globalcall I have found another
problem that take place under heavy stress
Here we can see a call clearing and a new call coming with almost no
delay between them
Bayonne is in idle while the new call as been offered.
The problem is that Bayonne idle clear the CRN but in this case the CRN
of the new call is cleared !
I think only driver.cpp should be able to clear CRN since it is the
driver event handler.
I am testing the modification.
Aug 27 08:37:18 localhost bayonne: dx(16): GCEV_DISCONNECTED HDL:39
Aug 27 08:37:18 localhost bayonne: dx(16): step 2 exit()
Aug 27 08:37:18 localhost bayonne: dx(16): exit
Aug 27 08:37:18 localhost bayonne: dx(16): script exiting
Aug 27 08:37:18 localhost bayonne: dx(16): hangup
Aug 27 08:37:18 localhost bayonne: dx(16): detach script
Aug 27 08:37:18 localhost bayonne: dx(16): GCEV_DROPCALL HDL:39
Aug 27 08:37:18 localhost bayonne: dx(16): release
Aug 27 08:37:19 localhost bayonne: dx(16): GCEV_RELEASECALL HDL:39
Aug 27 08:37:19 localhost bayonne: dx(16): GCEV_OFFERED HDL:39
CRN:33604644
Aug 27 08:37:19 localhost bayonne: dx(16): idle
Aug 27 08:37:19 localhost bayonne: dx(16): gc_AcceptCall error HDL:39
CRN:-1
Aug 27 08:37:19 localhost bayonne: dx(16): ring
Aug 27 08:37:28 localhost bayonne: dx(16): GCEV_DISCONNECTED HDL:39
Aug 27 08:37:29 localhost bayonne: dx(16): hangup
Aug 27 08:37:29 localhost bayonne: dx(16): gc_DropCall 66 Invalid call
reference number has been used
Aug 27 08:37:29 localhost bayonne: dx(16): idle
dyfet.vcf