Disconnect calls after about 10-15 min

haamed

Joined
Jul 23, 2007
Messages
251
Likes
0
Points
0
#1
Hi all.
my calls on Elastix 1.6 & a2billing 1.7 disconnected after about 10-15 minutes.
i install the same applications on another server with another provider ! but i have the same problem..
can i know what is the disconnect reason?
where should i check it?

thanks a lot
 

wasi.syed

Joined
Jan 7, 2011
Messages
94
Likes
0
Points
0
#2
Hi Haameed,

Have you receive any revert on your query ,even me too facing same kind of problem on elastix 2.0.0 with sangoma a101 card on centos system.

if you have anything pls share with me.

regds
Wasi
 

fmvillares

Joined
Sep 8, 2007
Messages
1,785
Likes
0
Points
0
#3
Re: Re:Disconnect calls after about 10-15 min

do you have magic balls? we dont either...send some debug if needing help
 

wasi.syed

Joined
Jan 7, 2011
Messages
94
Likes
0
Points
0
#4
Re: Re:Disconnect calls after about 10-15 min

Hello karma,

Pls check current logs.

[root@elastix ~]# wanrouter messages


Start WANPIPE /var/log/messages

Jan 3 19:24:30 elastix FaxSend[24673]: MODEM Supports B4 page length (364 mm)
Jan 3 19:24:30 elastix FaxSend[24673]: MODEM Supports unlimited page length
Jan 3 19:24:30 elastix FaxSend[24673]: MODEM Supports 1-D MH
Jan 3 19:24:30 elastix FaxSend[24673]: MODEM Supports 2-D MR
Jan 3 19:24:30 elastix FaxSend[24673]: MODEM Supports 2-D MMR
Jan 3 19:24:30 elastix FaxSend[24673]: MODEM Supports no ECM
Jan 3 19:24:30 elastix FaxSend[24673]: MODEM Supports T.30 Annex A, 64-byte ECM
Jan 3 19:24:30 elastix FaxSend[24673]: MODEM Supports T.30 Annex A, 256-byte ECM
Jan 3 19:24:30 elastix FaxSend[24673]: MODEM Supports 0 ms/scanline
Jan 3 19:24:30 elastix FaxSend[24673]: MODEM Supports 5 ms/scanline
Jan 3 19:24:30 elastix FaxSend[24673]: MODEM Supports 10 ms, 5 ms/scanline
Jan 3 19:24:30 elastix FaxSend[24673]: MODEM Supports 10 ms/scanline
Jan 3 19:24:30 elastix FaxSend[24673]: MODEM Supports 20 ms, 10 ms/scanline
Jan 3 19:24:30 elastix FaxSend[24673]: MODEM Supports 20 ms/scanline
Jan 3 19:24:30 elastix FaxSend[24673]: MODEM Supports 40 ms, 20 ms/scanline
Jan 3 19:24:30 elastix FaxSend[24673]: MODEM Supports 40 ms/scanline
Jan 3 19:24:30 elastix FaxSend[24673]: MODEM WWW.SOFT-SWITCH.ORG spandsp/
Jan 3 19:24:30 elastix FaxSend[24673]: <-- [5:ATM0\r]
Jan 3 19:24:30 elastix FaxSend[24673]: --> [2]
Jan 3 19:24:30 elastix FaxSend[24673]: STATE CHANGE: BASE -> RUNNING (timeout 30)
Jan 3 19:24:30 elastix FaxSend[24673]: MODEM input buffering disabled
Jan 3 19:24:30 elastix FaxSend[24673]: SEND FAX: JOB 19 DEST 30417070 COMMID 000000228 DEVICE '/dev/ttyIAX1' FROM 'test <wasi.syed@relianceada.com>' USER test
Jan 3 19:24:30 elastix FaxSend[24673]: SEND FAILED: JOB 19 DEST 30417070 ERR No local dialtone
Jan 3 19:24:30 elastix FaxSend[24673]: SEND FAILED: JOB 19 DEST 30417070 ERR No local dialtone; too many attempts to dial
Jan 3 19:24:30 elastix FaxQueuer[22355]: NOTIFY: bin/notify.php "doneq/q19" "failed" "0:09"
Jan 3 19:24:30 elastix FaxQueuer[22355]: NOTIFY exit status: 0 (24674)
Jan 3 19:24:52 elastix FaxGetty[22365]: MODEM set DTR OFF
Jan 3 19:24:52 elastix FaxGetty[22365]: MODEM set baud rate: 0 baud (flow control unchanged)
Jan 3 19:24:52 elastix FaxGetty[22365]: DELAY 75 ms
Jan 3 19:24:52 elastix FaxGetty[22365]: MODEM set DTR ON
Jan 3 19:24:52 elastix FaxGetty[22365]: DELAY 2600 ms
Jan 3 19:24:55 elastix FaxGetty[22365]: MODEM set baud rate: 19200 baud, input flow XON/XOFF, output flow XON/XOFF
Jan 3 19:24:55 elastix FaxGetty[22365]: DELAY 10 ms
Jan 3 19:24:55 elastix FaxGetty[22365]: MODEM flush i/o
Jan 3 19:24:55 elastix FaxGetty[22365]: <-- [4:ATZ\r]
Jan 3 19:24:55 elastix FaxGetty[22365]: --> [2]
Jan 3 19:24:55 elastix FaxGetty[22365]: DELAY 3000 ms
Jan 3 19:24:58 elastix FaxGetty[22365]: MODEM flush i/o
Jan 3 19:24:58 elastix FaxGetty[22365]: <-- [10:AT+VCID=1\r]
Jan 3 19:24:58 elastix FaxGetty[22365]: --> [9:AT+VCID=1]
Jan 3 19:24:58 elastix FaxGetty[22365]: --> [2]
Jan 3 19:24:58 elastix FaxGetty[22365]: <-- [7:ATS0=0\r]
Jan 3 19:24:58 elastix FaxGetty[22365]: --> [6:ATS0=0]
Jan 3 19:24:58 elastix FaxGetty[22365]: --> [2]
Jan 3 19:24:58 elastix FaxGetty[22365]: <-- [5:ATE0\r]
Jan 3 19:24:58 elastix FaxGetty[22365]: --> [4]
Jan 3 19:24:58 elastix FaxGetty[22365]: --> [2]
Jan 3 19:24:58 elastix FaxGetty[22365]: <-- [5:ATV1\r]
Jan 3 19:24:58 elastix FaxGetty[22365]: --> [2]
Jan 3 19:24:58 elastix FaxGetty[22365]: <-- [5:ATQ0\r]
Jan 3 19:24:58 elastix FaxGetty[22365]: --> [2]
Jan 3 19:24:58 elastix FaxGetty[22365]: <-- [7:ATS8=2\r]
Jan 3 19:24:58 elastix FaxGetty[22365]: --> [2]
Jan 3 19:24:58 elastix FaxGetty[22365]: <-- [8:ATS7=60\r]
Jan 3 19:24:58 elastix FaxGetty[22365]: --> [2]
Jan 3 19:24:58 elastix FaxGetty[22365]: <-- [12:AT+FCLASS=?\r]
Jan 3 19:24:58 elastix FaxGetty[22365]: --> [7:0,1,1.0]
Jan 3 19:24:58 elastix FaxGetty[22365]: --> [2]
Jan 3 19:24:58 elastix FaxGetty[22365]: MODEM Supports "Data"
Jan 3 19:24:58 elastix FaxGetty[22365]: MODEM Supports "Class 1"
Jan 3 19:24:58 elastix FaxGetty[22365]: MODEM Supports "Class 1.0"
Jan 3 19:24:58 elastix FaxGetty[22365]: <-- [12:AT+FCLASS=1\r]
Jan 3 19:24:58 elastix FaxGetty[22365]: --> [2]
Jan 3 19:24:58 elastix FaxGetty[22365]: <-- [5:ATI3\r]
Jan 3 19:24:58 elastix FaxGetty[22365]: --> [19:www.soft-switch.org]
Jan 3 19:24:58 elastix FaxGetty[22365]: --> [2]
Jan 3 19:24:58 elastix FaxGetty[22365]: MODEM: Mfr www.soft-switch.org
Jan 3 19:24:58 elastix FaxGetty[22365]: <-- [5:ATI0\r]
Jan 3 19:24:58 elastix FaxGetty[22365]: --> [7]
Jan 3 19:24:58 elastix FaxGetty[22365]: --> [2]
Jan 3 19:24:58 elastix FaxGetty[22365]: MODEM: Model spandsp
Jan 3 19:24:58 elastix FaxGetty[22365]: <-- [9:AT+FTM=?\r]
Jan 3 19:24:58 elastix FaxGetty[22365]: --> [39:24,48,72,73,74,96,97,98,121,122,145,146]
Jan 3 19:24:58 elastix FaxGetty[22365]: --> [2]
Jan 3 19:24:58 elastix FaxGetty[22365]: MODEM Supports 3.85 line/mm
Jan 3 19:24:58 elastix FaxGetty[22365]: MODEM Supports 7.7 line/mm
Jan 3 19:24:58 elastix FaxGetty[22365]: MODEM Supports 15.4 line/mm
Jan 3 19:24:58 elastix FaxGetty[22365]: MODEM Supports R16 x 15.4 line/mm
Jan 3 19:24:58 elastix FaxGetty[22365]: MODEM Supports 200 x 100 dpi
Jan 3 19:24:58 elastix FaxGetty[22365]: MODEM Supports 200 x 200 dpi
Jan 3 19:24:58 elastix FaxGetty[22365]: MODEM Supports 200 x 400 dpi
Jan 3 19:24:58 elastix FaxGetty[22365]: MODEM Supports 300 x 300 dpi
Jan 3 19:24:58 elastix FaxGetty[22365]: MODEM Supports 2400 bit/s
Jan 3 19:24:58 elastix FaxGetty[22365]: MODEM Supports 4800 bit/s
Jan 3 19:24:58 elastix FaxGetty[22365]: MODEM Supports 7200 bit/s
Jan 3 19:24:58 elastix FaxGetty[22365]: MODEM Supports 9600 bit/s
Jan 3 19:24:58 elastix FaxGetty[22365]: MODEM Supports 12000 bit/s
Jan 3 19:24:58 elastix FaxGetty[22365]: MODEM Supports 14400 bit/s
Jan 3 19:24:58 elastix FaxGetty[22365]: MODEM Supports A4 page width (215 mm)
Jan 3 19:24:58 elastix FaxGetty[22365]: MODEM Supports B4 page width (255 mm)
Jan 3 19:24:58 elastix FaxGetty[22365]: MODEM Supports A3 page width (303 mm)
Jan 3 19:24:58 elastix FaxGetty[22365]: MODEM Supports A4 page length (297 mm)
Jan 3 19:24:58 elastix FaxGetty[22365]: MODEM Supports B4 page length (364 mm)
Jan 3 19:24:58 elastix FaxGetty[22365]: MODEM Supports unlimited page length
Jan 3 19:24:58 elastix FaxGetty[22365]: MODEM Supports 1-D MH
Jan 3 19:24:58 elastix FaxGetty[22365]: MODEM Supports 2-D MR
Jan 3 19:24:58 elastix FaxGetty[22365]: MODEM Supports 2-D MMR
Jan 3 19:24:58 elastix FaxGetty[22365]: MODEM Supports no ECM
Jan 3 19:24:58 elastix FaxGetty[22365]: MODEM Supports T.30 Annex A, 64-byte ECM
Jan 3 19:24:58 elastix FaxGetty[22365]: MODEM Supports T.30 Annex A, 256-byte ECM
Jan 3 19:24:58 elastix FaxGetty[22365]: MODEM Supports 0 ms/scanline
Jan 3 19:24:58 elastix FaxGetty[22365]: MODEM Supports 5 ms/scanline
Jan 3 19:24:58 elastix FaxGetty[22365]: MODEM Supports 10 ms, 5 ms/scanline
Jan 3 19:24:58 elastix FaxGetty[22365]: MODEM Supports 10 ms/scanline
Jan 3 19:24:58 elastix FaxGetty[22365]: MODEM Supports 20 ms, 10 ms/scanline
Jan 3 19:24:58 elastix FaxGetty[22365]: MODEM Supports 20 ms/scanline
Jan 3 19:24:58 elastix FaxGetty[22365]: MODEM Supports 40 ms, 20 ms/scanline
Jan 3 19:24:58 elastix FaxGetty[22365]: MODEM Supports 40 ms/scanline
Jan 3 19:24:58 elastix FaxGetty[22365]: MODEM WWW.SOFT-SWITCH.ORG spandsp/
Jan 3 19:24:58 elastix FaxGetty[22365]: <-- [5:ATM0\r]
Jan 3 19:24:58 elastix FaxGetty[22365]: --> [2]
Jan 3 19:24:58 elastix FaxGetty[22365]: <-- [9:AT+FAR=1\r]
Jan 3 19:24:58 elastix FaxGetty[22365]: --> [2]
Jan 3 19:24:58 elastix FaxGetty[22365]: STATE CHANGE: LOCKWAIT -> RUNNING (timeout 30)
Jan 3 19:35:52 elastix avahi-daemon[4163]: Invalid response packet from host 192.168.10.50.
Jan 3 19:41:03 elastix ntpd[3388]: synchronized to 198.137.202.16, stratum 2
Jan 3 21:57:32 elastix ntpd[3388]: synchronized to 208.53.158.34, stratum 2
Jan 3 22:58:36 elastix ntpd[3388]: synchronized to 204.235.61.9, stratum 2
Jan 4 09:54:45 elastix ntpd[3388]: synchronized to 208.53.158.34, stratum 2
Jan 4 12:24:55 elastix kernel: hub 2-0:1.0: port 2 disabled by hub (EMI?), re-enabling...
Jan 4 12:24:55 elastix kernel: usb 2-2: USB disconnect, address 2
Jan 4 12:24:55 elastix kernel: usb 2-2: new low speed USB device using uhci_hcd and address 3
Jan 4 12:24:55 elastix kernel: usb 2-2: configuration #1 chosen from 1 choice
Jan 4 12:24:55 elastix kernel: input: USB Optical Mouse as /class/input/input3
Jan 4 12:24:55 elastix kernel: input: USB HID v1.11 Mouse [USB Optical Mouse] on usb-0000:00:1d.0-2
Jan 4 12:24:56 elastix kernel: hub 2-0:1.0: port 2 disabled by hub (EMI?), re-enabling...
Jan 4 12:24:56 elastix kernel: usb 2-2: USB disconnect, address 3
Jan 4 12:24:56 elastix kernel: usb 2-2: new low speed USB device using uhci_hcd and address 4
Jan 4 12:24:56 elastix kernel: usb 2-2: configuration #1 chosen from 1 choice
Jan 4 12:24:57 elastix kernel: input: USB Optical Mouse as /class/input/input4
Jan 4 12:24:57 elastix kernel: input: USB HID v1.11 Mouse [USB Optical Mouse] on usb-0000:00:1d.0-2
Jan 4 12:56:01 elastix kernel: usb 2-2: USB disconnect, address 4
Jan 4 13:00:17 elastix kernel: input: ImExPS/2 Generic Explorer Mouse as /class/input/input5
Jan 4 14:19:50 elastix avahi-daemon[4163]: Invalid response packet from host 192.168.10.50.
Jan 4 14:20:21 elastix last message repeated 5 times
Jan 4 14:24:05 elastix avahi-daemon[4163]: Invalid response packet from host 192.168.10.50.
Jan 4 14:28:21 elastix avahi-daemon[4163]: Invalid response packet from host 192.168.10.50.
Jan 4 14:36:53 elastix avahi-daemon[4163]: Invalid response packet from host 192.168.10.50.
Jan 4 14:53:57 elastix avahi-daemon[4163]: Invalid response packet from host 192.168.10.50.
Jan 4 15:20:06 elastix kernel: dahdi: Disabled echo canceller NLP because of CED rx detected on channel 1
Jan 4 16:19:19 elastix ntpd[3388]: synchronized to 204.235.61.9, stratum 2
Jan 4 16:53:00 elastix kernel: dahdi: Disabled echo canceller NLP because of CED tx detected on channel 25
Jan 4 18:14:47 elastix kernel: dahdi: Disabled echo canceller NLP because of CED tx detected on channel 2
Jan 4 20:29:46 elastix kernel: wanpipe1: RAI alarm is ON
Jan 4 20:29:46 elastix kernel: wanpipe1: E1 disconnected!
Jan 4 20:29:47 elastix kernel: wanpipe1: AFT communications disabled! (Dev Cnt: 1 Cause: Link Down)
Jan 4 20:29:47 elastix kernel: wanpipe1: TDM Free Run Timing Enabled 1 ms
Jan 4 20:29:50 elastix kernel: wanpipe1: AIS : ON
Jan 4 20:29:52 elastix kernel: wanpipe1: RAI : OFF
Jan 4 20:30:00 elastix kernel: wanpipe1: E1 connected!
Jan 4 20:30:00 elastix kernel: wanpipe1: AFT communications enabled!
Jan 4 20:30:00 elastix kernel: wanpipe1: AFT Global TDM Intr
Jan 4 20:30:00 elastix kernel: ADDRCONF(NETDEV_CHANGE): w1g1: link becomes ready
Jan 4 20:30:00 elastix kernel: wanpipe1: Global TDM Ring Resync TDM = 0x1
Jan 4 20:30:02 elastix kernel: wanpipe1: AIS : OFF
Jan 5 02:42:53 elastix ntpd[3388]: synchronized to 198.137.202.16, stratum 2
Jan 5 03:33:42 elastix ntpd[3388]: synchronized to 208.53.158.34, stratum 2
Jan 5 05:07:59 elastix ntpd[3388]: synchronized to 204.235.61.9, stratum 2
Jan 5 07:32:41 elastix ntpd[3388]: synchronized to 198.137.202.16, stratum 2
Jan 5 08:23:56 elastix ntpd[3388]: synchronized to 208.53.158.34, stratum 2
Jan 5 11:06:55 elastix ntpd[3388]: synchronized to 204.235.61.9, stratum 2
Jan 5 12:51:08 elastix kernel: dahdi: Disabled echo canceller NLP because of CED tx detected on channel 31
Jan 5 14:22:20 elastix ntpd[3388]: synchronized to 198.137.202.16, stratum 2
Jan 5 14:33:16 elastix avahi-daemon[4163]: Invalid query packet.
Jan 5 14:33:47 elastix last message repeated 18 times
Jan 5 14:33:56 elastix last message repeated 9 times
Jan 5 16:38:54 elastix ntpd[3388]: synchronized to 204.235.61.9, stratum 2
Jan 5 17:55:21 elastix kernel: dahdi: Disabled echo canceller NLP because of CED rx detected on channel 1
Jan 5 17:56:26 elastix kernel: dahdi: Disabled echo canceller NLP because of CED rx detected on channel 1
Jan 5 18:05:14 elastix ntpd[3388]: synchronized to 198.137.202.16, stratum 2
Jan 5 19:12:52 elastix ntpd[3388]: synchronized to 204.235.61.9, stratum 2
Jan 5 20:03:57 elastix ntpd[3388]: synchronized to 198.137.202.16, stratum 2
Jan 5 21:12:06 elastix ntpd[3388]: synchronized to 208.53.158.34, stratum 2
Jan 6 00:11:34 elastix ntpd[3388]: synchronized to 204.235.61.9, stratum 2
Jan 6 08:18:19 elastix ntpd[3388]: synchronized to 208.53.158.34, stratum 2
Jan 6 10:09:13 elastix ntpd[3388]: synchronized to 198.137.202.16, stratum 2
Jan 6 16:24:44 elastix avahi-daemon[4163]: Invalid response packet from host 192.168.10.50.
Jan 6 16:25:15 elastix last message repeated 5 times
Jan 6 16:26:51 elastix last message repeated 2 times
Jan 6 16:28:59 elastix avahi-daemon[4163]: Invalid response packet from host 192.168.10.50.
Jan 6 16:33:15 elastix avahi-daemon[4163]: Invalid response packet from host 192.168.10.50.
Jan 6 16:37:25 elastix kernel: dahdi: Disabled echo canceller NLP because of CED rx detected on channel 2
Jan 6 16:41:47 elastix avahi-daemon[4163]: Invalid response packet from host 192.168.10.50.
Jan 6 17:32:59 elastix avahi-daemon[4163]: Invalid response packet from host 192.168.10.50.
Jan 6 17:42:04 elastix ntpd[3388]: synchronized to 204.235.61.9, stratum 2
Jan 6 18:32:59 elastix avahi-daemon[4163]: Invalid response packet from host 192.168.10.50.
Jan 6 18:33:35 elastix ntpd[3388]: synchronized to 208.53.158.34, stratum 2
Jan 6 19:32:59 elastix avahi-daemon[4163]: Invalid response packet from host 192.168.10.50.
Jan 6 20:07:12 elastix ntpd[3388]: synchronized to 204.235.61.9, stratum 2
Jan 7 03:05:02 elastix ntpd[3388]: synchronized to 198.137.202.16, stratum 2
Jan 7 06:12:50 elastix ntpd[3388]: synchronized to 204.235.61.9, stratum 2
Jan 7 09:38:25 elastix ntpd[3388]: synchronized to 208.53.158.34, stratum 2
Jan 7 12:03:07 elastix ntpd[3388]: synchronized to 198.137.202.16, stratum 2
Jan 7 12:19:19 elastix kernel: dahdi: Disabled echo canceller NLP because of CED tx detected on channel 19
Jan 7 15:36:26 elastix ntpd[3388]: synchronized to 208.53.158.34, stratum 2
Jan 7 16:39:24 elastix avahi-daemon[4163]: Invalid query packet.
Jan 7 16:40:04 elastix last message repeated 7 times
Jan 7 18:18:41 elastix ntpd[3388]: synchronized to 204.235.61.9, stratum 2
Jan 8 00:43:01 elastix ntpd[3388]: synchronized to 198.137.202.16, stratum 2
Jan 8 03:16:26 elastix ntpd[3388]: synchronized to 204.235.61.9, stratum 2

End of WANPIPE /var/log/messages

[root@elastix ~]# wanrouter conflog


Start WANPIPE /var/log/wanrouter

Shutting down device: wanpipe1
WAN Router Configurator(c) 1995-2003 Sangoma Technologies Inc.
* Reading section [devices]...
* Shutting down WAN device wanpipe1 ...
Done
Mon Dec 27 11:28:16 IST 2010: starting WAN router
Loading driver wanpipe ... ok
Starting up device: wanpipe1
WAN Router Configurator(c) 1995-2003 Sangoma Technologies Inc.
* Parsing configuration file /etc/wanpipe/wanpipe1.conf ...
* Reading section [devices]...
* Reading section [wanpipe1]...
* Reading section [interfaces]...
* w1g1 to used by TDM_VOICE
* Reading section [w1g1]...
* Configuring device wanpipe1 (no description)
* Setting CARD_TYPE to AFT
* Setting S514CPU to A
* Setting COMMPORT to PRI
* Setting AUTO_PCISLOT to NO
* Setting PCISLOT to 2
* Setting PCIBUS to 6
* Setting FE_MEDIA to E1
* Setting FE_LCODE to HDB3
* Setting FE_FRAME to CRC4
* Setting FE_LINE to 1
* Setting TE_CLOCK to MASTER
* Setting TE_REF_CLOCK to 0
* Setting TE_SIG_MODE to CCS
* Setting TE_HIGHIMPEDANCE to NO
* Setting TE_RX_SLEVEL to 430
* Setting LBO to 120OH
* Setting FE_TXTRISTATE to NO
* Setting MTU to 1500
* Setting UDPPORT to 9000
* Setting TTL to 255
* Setting IGNORE_FRONT_END to NO
* Setting TDMV_SPAN to 1
* Setting TDMV_DCHAN to 16
* Setting TE_AIS_MAINTENANCE to NO
* Setting TDMV_HW_DTMF to NO
* Setting TDMV_HW_FAX_DETECT to NO
* Setting HWEC_OPERATION_MODE to OCT_NORMAL
* Setting HWEC_DTMF_REMOVAL to NO
* Setting HWEC_NOISE_REDUCTION to NO
* Setting HWEC_ACUSTIC_ECHO to NO
* Setting HWEC_NLP_DISABLE to NO
* Setting HWEC_TX_AUTO_GAIN to 0
* Setting HWEC_RX_AUTO_GAIN to 0
* Setting HWEC_TX_GAIN to 0
* Setting HWEC_RX_GAIN to 0
* Configuring channel w1g1 (no description). Media address:
* Setting ACTIVE_CH to ALL
* Setting TDMV_HWEC to NO
* Setting MTU to 8
Shutting down device: wanpipe1
WAN Router Configurator(c) 1995-2003 Sangoma Technologies Inc.
* Reading section [devices]...
* Shutting down WAN device wanpipe1 ...
Shutting down device: wanpipe1
WAN Router Configurator(c) 1995-2003 Sangoma Technologies Inc.
* Reading section [devices]...
* Shutting down WAN device wanpipe1 ...
Shutting down device: wanpipe1
WAN Router Configurator(c) 1995-2003 Sangoma Technologies Inc.
* Reading section [devices]...
* Shutting down WAN device wanpipe1 ...
Shutting down device: wanpipe1
WAN Router Configurator(c) 1995-2003 Sangoma Technologies Inc.
* Reading section [devices]...
* Shutting down WAN device wanpipe1 ...
Shutting down device: wanpipe1
WAN Router Configurator(c) 1995-2003 Sangoma Technologies Inc.
* Reading section [devices]...
* Shutting down WAN device wanpipe1 ...
Shutting down device: wanpipe1
WAN Router Configurator(c) 1995-2003 Sangoma Technologies Inc.
* Reading section [devices]...
* Shutting down WAN device wanpipe1 ...
Done
Mon Dec 27 12:01:47 IST 2010: starting WAN router
Loading driver wanpipe ... ok
Starting up device: wanpipe1
WAN Router Configurator(c) 1995-2003 Sangoma Technologies Inc.
* Parsing configuration file /etc/wanpipe/wanpipe1.conf ...
* Reading section [devices]...
* Reading section [wanpipe1]...
* Reading section [interfaces]...
* w1g1 to used by TDM_VOICE
* Reading section [w1g1]...
* Configuring device wanpipe1 (no description)
* Setting CARD_TYPE to AFT
* Setting S514CPU to A
* Setting COMMPORT to PRI
* Setting AUTO_PCISLOT to NO
* Setting PCISLOT to 2
* Setting PCIBUS to 6
* Setting FE_MEDIA to E1
* Setting FE_LCODE to HDB3
* Setting FE_FRAME to CRC4
* Setting FE_LINE to 1
* Setting TE_CLOCK to MASTER
* Setting TE_REF_CLOCK to 0
* Setting TE_SIG_MODE to CCS
* Setting TE_HIGHIMPEDANCE to NO
* Setting TE_RX_SLEVEL to 430
* Setting LBO to 120OH
* Setting FE_TXTRISTATE to NO
* Setting MTU to 1500
* Setting UDPPORT to 9000
* Setting TTL to 255
* Setting IGNORE_FRONT_END to NO
* Setting TDMV_SPAN to 1
* Setting TDMV_DCHAN to 16
* Setting TE_AIS_MAINTENANCE to NO
* Setting TDMV_HW_DTMF to NO
* Setting TDMV_HW_FAX_DETECT to NO
* Setting HWEC_OPERATION_MODE to OCT_NORMAL
* Setting HWEC_DTMF_REMOVAL to NO
* Setting HWEC_NOISE_REDUCTION to NO
* Setting HWEC_ACUSTIC_ECHO to NO
* Setting HWEC_NLP_DISABLE to NO
* Setting HWEC_TX_AUTO_GAIN to 0
* Setting HWEC_RX_AUTO_GAIN to 0
* Setting HWEC_TX_GAIN to 0
* Setting HWEC_RX_GAIN to 0
* Configuring channel w1g1 (no description). Media address:
* Setting ACTIVE_CH to ALL
* Setting TDMV_HWEC to NO
* Setting MTU to 8
Shutting down device: wanpipe1
WAN Router Configurator(c) 1995-2003 Sangoma Technologies Inc.
* Reading section [devices]...
* Shutting down WAN device wanpipe1 ...
Shutting down device: wanpipe1
WAN Router Configurator(c) 1995-2003 Sangoma Technologies Inc.
* Reading section [devices]...
* Shutting down WAN device wanpipe1 ...
Shutting down device: wanpipe1
WAN Router Configurator(c) 1995-2003 Sangoma Technologies Inc.
* Reading section [devices]...
* Shutting down WAN device wanpipe1 ...
Shutting down device: wanpipe1
WAN Router Configurator(c) 1995-2003 Sangoma Technologies Inc.
* Reading section [devices]...
* Shutting down WAN device wanpipe1 ...
Shutting down device: wanpipe1
WAN Router Configurator(c) 1995-2003 Sangoma Technologies Inc.
* Reading section [devices]...
* Shutting down WAN device wanpipe1 ...
Shutting down device: wanpipe1
WAN Router Configurator(c) 1995-2003 Sangoma Technologies Inc.
* Reading section [devices]...
* Shutting down WAN device wanpipe1 ...
Shutting down device: wanpipe1
WAN Router Configurator(c) 1995-2003 Sangoma Technologies Inc.
* Reading section [devices]...
* Shutting down WAN device wanpipe1 ...
Shutting down device: wanpipe1
WAN Router Configurator(c) 1995-2003 Sangoma Technologies Inc.
* Reading section [devices]...
* Shutting down WAN device wanpipe1 ...
Shutting down device: wanpipe1
WAN Router Configurator(c) 1995-2003 Sangoma Technologies Inc.
* Reading section [devices]...
* Shutting down WAN device wanpipe1 ...
Shutting down device: wanpipe1
WAN Router Configurator(c) 1995-2003 Sangoma Technologies Inc.
* Reading section [devices]...
* Shutting down WAN device wanpipe1 ...
Shutting down device: wanpipe1
WAN Router Configurator(c) 1995-2003 Sangoma Technologies Inc.
* Reading section [devices]...
* Shutting down WAN device wanpipe1 ...
Shutting down device: wanpipe1
WAN Router Configurator(c) 1995-2003 Sangoma Technologies Inc.
* Reading section [devices]...
* Shutting down WAN device wanpipe1 ...
Shutting down device: wanpipe1
WAN Router Configurator(c) 1995-2003 Sangoma Technologies Inc.
* Reading section [devices]...
* Shutting down WAN device wanpipe1 ...
Shutting down device: wanpipe1
WAN Router Configurator(c) 1995-2003 Sangoma Technologies Inc.
* Reading section [devices]...
* Shutting down WAN device wanpipe1 ...
Shutting down device: wanpipe1
WAN Router Configurator(c) 1995-2003 Sangoma Technologies Inc.
* Reading section [devices]...
* Shutting down WAN device wanpipe1 ...
Shutting down device: wanpipe1
WAN Router Configurator(c) 1995-2003 Sangoma Technologies Inc.
* Reading section [devices]...
* Shutting down WAN device wanpipe1 ...
Shutting down device: wanpipe1
WAN Router Configurator(c) 1995-2003 Sangoma Technologies Inc.
* Reading section [devices]...
* Shutting down WAN device wanpipe1 ...
Shutting down device: wanpipe1
WAN Router Configurator(c) 1995-2003 Sangoma Technologies Inc.
* Reading section [devices]...
* Shutting down WAN device wanpipe1 ...
Shutting down device: wanpipe1
WAN Router Configurator(c) 1995-2003 Sangoma Technologies Inc.
* Reading section [devices]...
* Shutting down WAN device wanpipe1 ...
Shutting down device: wanpipe1
WAN Router Configurator(c) 1995-2003 Sangoma Technologies Inc.
* Reading section [devices]...
* Shutting down WAN device wanpipe1 ...
Shutting down device: wanpipe1
WAN Router Configurator(c) 1995-2003 Sangoma Technologies Inc.
* Reading section [devices]...
* Shutting down WAN device wanpipe1 ...
Shutting down device: wanpipe1
WAN Router Configurator(c) 1995-2003 Sangoma Technologies Inc.
* Reading section [devices]...
* Shutting down WAN device wanpipe1 ...
Shutting down device: wanpipe1
WAN Router Configurator(c) 1995-2003 Sangoma Technologies Inc.
* Reading section [devices]...
* Shutting down WAN device wanpipe1 ...
Shutting down device: wanpipe1
WAN Router Configurator(c) 1995-2003 Sangoma Technologies Inc.
* Reading section [devices]...
* Shutting down WAN device wanpipe1 ...
Shutting down device: wanpipe1
WAN Router Configurator(c) 1995-2003 Sangoma Technologies Inc.
* Reading section [devices]...
* Shutting down WAN device wanpipe1 ...
Shutting down device: wanpipe1
WAN Router Configurator(c) 1995-2003 Sangoma Technologies Inc.
* Reading section [devices]...
* Shutting down WAN device wanpipe1 ...
Shutting down device: wanpipe1
WAN Router Configurator(c) 1995-2003 Sangoma Technologies Inc.
* Reading section [devices]...
* Shutting down WAN device wanpipe1 ...
Shutting down device: wanpipe1
WAN Router Configurator(c) 1995-2003 Sangoma Technologies Inc.
* Reading section [devices]...
* Shutting down WAN device wanpipe1 ...
Shutting down device: wanpipe1
WAN Router Configurator(c) 1995-2003 Sangoma Technologies Inc.
* Reading section [devices]...
* Shutting down WAN device wanpipe1 ...
Shutting down device: wanpipe1
WAN Router Configurator(c) 1995-2003 Sangoma Technologies Inc.
* Reading section [devices]...
* Shutting down WAN device wanpipe1 ...
Shutting down device: wanpipe1
WAN Router Configurator(c) 1995-2003 Sangoma Technologies Inc.
* Reading section [devices]...
* Shutting down WAN device wanpipe1 ...
Shutting down device: wanpipe1
WAN Router Configurator(c) 1995-2003 Sangoma Technologies Inc.
* Reading section [devices]...
* Shutting down WAN device wanpipe1 ...
Shutting down device: wanpipe1
WAN Router Configurator(c) 1995-2003 Sangoma Technologies Inc.
* Reading section [devices]...
* Shutting down WAN device wanpipe1 ...
Shutting down device: wanpipe1
WAN Router Configurator(c) 1995-2003 Sangoma Technologies Inc.
* Reading section [devices]...
* Shutting down WAN device wanpipe1 ...
Shutting down device: wanpipe1
WAN Router Configurator(c) 1995-2003 Sangoma Technologies Inc.
* Reading section [devices]...
* Shutting down WAN device wanpipe1 ...
Shutting down device: wanpipe1
WAN Router Configurator(c) 1995-2003 Sangoma Technologies Inc.
* Reading section [devices]...
* Shutting down WAN device wanpipe1 ...
Shutting down device: wanpipe1
WAN Router Configurator(c) 1995-2003 Sangoma Technologies Inc.
* Reading section [devices]...
* Shutting down WAN device wanpipe1 ...
Shutting down device: wanpipe1
WAN Router Configurator(c) 1995-2003 Sangoma Technologies Inc.
* Reading section [devices]...
* Shutting down WAN device wanpipe1 ...
Done
Mon Dec 27 12:24:49 IST 2010: starting WAN router
Loading driver wanpipe ... ok
Starting up device: wanpipe1
WAN Router Configurator(c) 1995-2003 Sangoma Technologies Inc.
* Parsing configuration file /etc/wanpipe/wanpipe1.conf ...
* Reading section [devices]...
* Reading section [wanpipe1]...
* Reading section [interfaces]...
* w1g1 to used by TDM_VOICE
* Reading section [w1g1]...
* Configuring device wanpipe1 (no description)
* Setting CARD_TYPE to AFT
* Setting S514CPU to A
* Setting COMMPORT to PRI
* Setting AUTO_PCISLOT to NO
* Setting PCISLOT to 2
* Setting PCIBUS to 6
* Setting FE_MEDIA to E1
* Setting FE_LCODE to HDB3
* Setting FE_FRAME to CRC4
* Setting FE_LINE to 1
* Setting TE_CLOCK to MASTER
* Setting TE_REF_CLOCK to 0
* Setting TE_SIG_MODE to CCS
* Setting TE_HIGHIMPEDANCE to NO
* Setting TE_RX_SLEVEL to 430
* Setting LBO to 120OH
* Setting FE_TXTRISTATE to NO
* Setting MTU to 1500
* Setting UDPPORT to 9000
* Setting TTL to 255
* Setting IGNORE_FRONT_END to NO
* Setting TDMV_SPAN to 1
* Setting TDMV_DCHAN to 16
* Setting TE_AIS_MAINTENANCE to NO
* Setting TDMV_HW_DTMF to NO
* Setting TDMV_HW_FAX_DETECT to NO
* Setting HWEC_OPERATION_MODE to OCT_NORMAL
* Setting HWEC_DTMF_REMOVAL to NO
* Setting HWEC_NOISE_REDUCTION to NO
* Setting HWEC_ACUSTIC_ECHO to NO
* Setting HWEC_NLP_DISABLE to NO
* Setting HWEC_TX_AUTO_GAIN to 0
* Setting HWEC_RX_AUTO_GAIN to 0
* Setting HWEC_TX_GAIN to 0
* Setting HWEC_RX_GAIN to 0
* Configuring channel w1g1 (no description). Media address:
* Setting ACTIVE_CH to ALL
* Setting TDMV_HWEC to NO
* Setting MTU to 8
Shutting down device: wanpipe1
WAN Router Configurator(c) 1995-2003 Sangoma Technologies Inc.
* Reading section [devices]...
* Shutting down WAN device wanpipe1 ...
Done
Fri Dec 31 18:52:38 IST 2010: starting WAN router
Loading driver wanpipe ... ok
Starting up device: wanpipe1
WAN Router Configurator(c) 1995-2003 Sangoma Technologies Inc.
* Parsing configuration file /etc/wanpipe/wanpipe1.conf ...
* Reading section [devices]...
* Reading section [wanpipe1]...
* Reading section [interfaces]...
* w1g1 to used by TDM_VOICE
* Reading section [w1g1]...
* Configuring device wanpipe1 (no description)
* Setting CARD_TYPE to AFT
* Setting S514CPU to A
* Setting COMMPORT to PRI
* Setting AUTO_PCISLOT to NO
* Setting PCISLOT to 2
* Setting PCIBUS to 6
* Setting FE_MEDIA to E1
* Setting FE_LCODE to HDB3
* Setting FE_FRAME to CRC4
* Setting FE_LINE to 1
* Setting TE_CLOCK to MASTER
* Setting TE_REF_CLOCK to 0
* Setting TE_SIG_MODE to CCS
* Setting TE_HIGHIMPEDANCE to NO
* Setting TE_RX_SLEVEL to 430
* Setting LBO to 120OH
* Setting FE_TXTRISTATE to NO
* Setting MTU to 1500
* Setting UDPPORT to 9000
* Setting TTL to 255
* Setting IGNORE_FRONT_END to NO
* Setting TDMV_SPAN to 1
* Setting TDMV_DCHAN to 16
* Setting TE_AIS_MAINTENANCE to NO
* Setting TDMV_HW_DTMF to NO
* Setting TDMV_HW_FAX_DETECT to NO
* Setting HWEC_OPERATION_MODE to OCT_NORMAL
* Setting HWEC_DTMF_REMOVAL to NO
* Setting HWEC_NOISE_REDUCTION to NO
* Setting HWEC_ACUSTIC_ECHO to NO
* Setting HWEC_NLP_DISABLE to NO
* Setting HWEC_TX_AUTO_GAIN to 0
* Setting HWEC_RX_AUTO_GAIN to 0
* Setting HWEC_TX_GAIN to 0
* Setting HWEC_RX_GAIN to 0
* Configuring channel w1g1 (no description). Media address:
* Setting ACTIVE_CH to ALL
* Setting TDMV_HWEC to NO
* Setting MTU to 8

End of WANPIPE /var/log/wanrouter

pls let me know any other logs to investigate further & how to get that logs.


wasi
 

mm.alpha2k

Joined
Jun 19, 2010
Messages
165
Likes
0
Points
0
#5
Re: Re:Disconnect calls after about 10-15 min

enable logger.conf
console => notice,warning,error,debug
messages => notice,warning,error

And showing what appears in the CLI, when you cut the call
 

wasi.syed

Joined
Jan 7, 2011
Messages
94
Likes
0
Points
0
#6
Re: Re:Disconnect calls after about 10-15 min

hi karma,

i had made changes in logger.conf as per above requirement..
but now tell me how do i collect logs

regds
wasi
 

wasi.syed

Joined
Jan 7, 2011
Messages
94
Likes
0
Points
0
#7
Re: Re:Disconnect calls after about 10-15 min

hello,

seeking help from elastix team...my elastix problem still not resolve call disconnect in every 15min .

regds
wasi
 

wasi.syed

Joined
Jan 7, 2011
Messages
94
Likes
0
Points
0
#8
Hello Elastix expert,

I am still not able to resolve 15min call disconnection problem on my elastix ,can anybody help me

even my provider line being check there is no problem found on E1 line .

regds
wasi
 

mm.alpha2k

Joined
Jun 19, 2010
Messages
165
Likes
0
Points
0
#9
Show Cli When communication is cut, so we know What Happens.
 

wasi.syed

Joined
Jan 7, 2011
Messages
94
Likes
0
Points
0
#10
hello ,

can anybody provide solution on attch log
yesterday same problem about in 15min call drop from the our setup ext 5813 during 15:27 to 15:42hrs on 1st feb 2011.

regds
wasi
 

wasi.syed

Joined
Jan 7, 2011
Messages
94
Likes
0
Points
0
#11
hello,

pls check attch log in txt format.

regds
wasi
 

wasi.syed

Joined
Jan 7, 2011
Messages
94
Likes
0
Points
0
#12
hello,
Pls check latest log and let me know what kind of problem to troubleshoot.


[Feb 7 19:06:14] VERBOSE[4040] chan_sip.c:
<--- SIP read from UDP:192.168.10.6:5086 --->
SIP/2.0 420 Bad Extension
Via: SIP/2.0/UDP 192.168.10.5:5060;branch=z9hG4bK2edc1cfd;rport=5060
From: <sip:907505108526@192.168.10.5;user=phone>;tag=as33fe1cc8
To: "Wasi Syed" <sip:5824@192.168.10.5;user=phone>;tag=66698467
Call-ID: 1528641097-5086-25@192.168.10.6
CSeq: 102 INVITE
Supported: replaces, path, timer
User-Agent: Grandstream GXW-4024 V0.2C 1.0.3.10
Unsupported: timer
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, INFO, REFER, UPDATE
Content-Length: 0


<------------->
[Feb 7 19:06:14] VERBOSE[4040] chan_sip.c: --- (11 headers 0 lines) ---
[Feb 7 19:06:14] VERBOSE[4040] chan_sip.c: -- Got SIP response 420 "Bad Extension" back from 192.168.10.6
[Feb 7 19:06:14] VERBOSE[4040] chan_sip.c: set_destination: Parsing <sip:5824@192.168.10.6:5086;user=phone> for address/port to send to
[Feb 7 19:06:14] VERBOSE[4040] chan_sip.c: set_destination: set destination to 192.168.10.6, port 5086
[Feb 7 19:06:14] VERBOSE[4040] chan_sip.c: Transmitting (NAT) to 192.168.10.6:5086:
ACK sip:5824@192.168.10.6:5086;user=phone SIP/2.0
Via: SIP/2.0/UDP 192.168.10.5:5060;branch=z9hG4bK2edc1cfd;rport
Max-Forwards: 70
From: <sip:907505108526@192.168.10.5;user=phone>;tag=as33fe1cc8
To: "Wasi Syed" <sip:5824@192.168.10.5;user=phone>;tag=66698467
Contact: <sip:907505108526@192.168.10.5>
Call-ID: 1528641097-5086-25@192.168.10.6
CSeq: 102 ACK
User-Agent: Asterisk PBX 1.6.2.13
Content-Length: 0


---
[Feb 7 19:06:14] VERBOSE[2217] pbx.c: -- Executing [h@macro-dialout-trunk:1] Macro("SIP/5824-00000e58", "hangupcall,") in new stack
[Feb 7 19:06:14] VERBOSE[2217] pbx.c: -- Executing [s@macro-hangupcall:1] GotoIf("SIP/5824-00000e58", "1?noautomon") in new stack
[Feb 7 19:06:14] VERBOSE[2217] pbx.c: -- Goto (macro-hangupcall,s,3)
[Feb 7 19:06:14] VERBOSE[2217] pbx.c: -- Executing [s@macro-hangupcall:3] NoOp("SIP/5824-00000e58", "TOUCH_MONITOR_OUTPUT=") in new stack
[Feb 7 19:06:14] VERBOSE[2217] pbx.c: -- Executing [s@macro-hangupcall:4] GotoIf("SIP/5824-00000e58", "1?noautomon2") in new stack
[Feb 7 19:06:14] VERBOSE[2217] pbx.c: -- Goto (macro-hangupcall,s,6)
[Feb 7 19:06:14] VERBOSE[2217] pbx.c: -- Executing [s@macro-hangupcall:6] NoOp("SIP/5824-00000e58", "MONITOR_FILENAME=") in new stack
[Feb 7 19:06:14] VERBOSE[2217] pbx.c: -- Executing [s@macro-hangupcall:7] GotoIf("SIP/5824-00000e58", "1?skiprg") in new stack
[Feb 7 19:06:14] VERBOSE[2217] pbx.c: -- Goto (macro-hangupcall,s,10)
[Feb 7 19:06:14] VERBOSE[2217] pbx.c: -- Executing [s@macro-hangupcall:10] GotoIf("SIP/5824-00000e58", "1?skipblkvm") in new stack
[Feb 7 19:06:14] VERBOSE[2217] pbx.c: -- Goto (macro-hangupcall,s,13)
[Feb 7 19:06:14] VERBOSE[2217] pbx.c: -- Executing [s@macro-hangupcall:13] GotoIf("SIP/5824-00000e58", "1?theend") in new stack
[Feb 7 19:06:14] VERBOSE[2217] pbx.c: -- Goto (macro-hangupcall,s,15)
[Feb 7 19:06:14] VERBOSE[2217] pbx.c: -- Executing [s@macro-hangupcall:15] Hangup("SIP/5824-00000e58", "") in new stack
[Feb 7 19:06:14] VERBOSE[2217] app_macro.c: == Spawn extension (macro-hangupcall, s, 15) exited non-zero on 'SIP/5824-00000e58' in macro 'hangupcall'
[Feb 7 19:06:14] VERBOSE[2217] chan_dahdi.c: -- Hungup 'DAHDI/1-1'
[Feb 7 19:06:14] VERBOSE[2217] app_macro.c: == Spawn extension (macro-dialout-trunk, s, 19) exited non-zero on 'SIP/5824-00000e58' in macro 'dialout-trunk'
[Feb 7 19:06:14] VERBOSE[2217] pbx.c: == Spawn extension (from-internal, 907505108526, 4) exited non-zero on 'SIP/5824-00000e58'
[Feb 7 19:06:15] VERBOSE[4040] chan_sip.c: Reliably Transmitting (NAT) to 192.168.10.6:5074:
OPTIONS sip:5818@192.168.10.6:5074;user=phone SIP/2.0
Via: SIP/2.0/UDP 192.168.10.5:5060;branch=z9hG4bK4e5c6b6c;rport
Max-Forwards: 70
From: "Unknown" <sip:Unknown@192.168.10.5>;tag=as60bd3ace
To: <sip:5818@192.168.10.6:5074;user=phone>
Contact: <sip:Unknown@192.168.10.5>
Call-ID: 55393af539bfa5fa1a1732d02fb2bef6@192.168.10.5
CSeq: 102 OPTIONS
User-Agent: Asterisk PBX 1.6.2.13
Date: Mon, 07 Feb 2011 13:36:15 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO
Supported: replaces, timer
Content-Length: 0


regds
wasi
 

wasi.syed

Joined
Jan 7, 2011
Messages
94
Likes
0
Points
0
#13
Hello,

can you pls help to troubleshoot on attch log call disconnection in 15min...

ystday ext 5824 got disconnect at 19.06hrs.

regds
wasi
 

dicko

Joined
Oct 24, 2008
Messages
4,099
Likes
0
Points
0
#14
wasi:

Might I suggest that you start a new thread, you are totally off topic here, all you post shows here is that you have a mis-configured Grandstream, (and prior to that a misconfigured Sangoma), It can't connect 5824 and 907505108526, there is absolutely nothing to do with disconnecting after 10-15 minutes that this thread is about (it probably disconnected in 10-15 millseconds though :) and why this thread is in the a2billing forum is even more obtuse) please rationalize and identify one problem at a time.

(I will not however participate as I won't do grandstreams, I prefer to put them in microwave ovens)
 

wasi.syed

Joined
Jan 7, 2011
Messages
94
Likes
0
Points
0
#15
Karma,

But as per subject its shows 10-15min disconnection problem ,,any way will open another thread and investigate.

thanks for all solution .

regds
wasi
 

fmvillares

Joined
Sep 8, 2007
Messages
1,785
Likes
0
Points
0
#16
Re: Re:Disconnect calls after about 10-15 min

its a problem with your provider. yur telephone cmopany has give you a cisco e1 router? there is a known bug n rtp timers with cisco routers
 

wasi.syed

Joined
Jan 7, 2011
Messages
94
Likes
0
Points
0
#17
there is no router available from provider ...E1 link direct terminate on Linux cent os on sangoma a101 internal card.
 

fmvillares

Joined
Sep 8, 2007
Messages
1,785
Likes
0
Points
0
#18
Re: Re:Disconnect calls after about 10-15 min

do you have grandstream phones? there is a know bug also in all new firmwares
 

wasi.syed

Joined
Jan 7, 2011
Messages
94
Likes
0
Points
0
#19
i have grandstream gxw4024 device with all analog instrument connected with sangoma a101 pci card on cent os 5.5 server
 

fmvillares

Joined
Sep 8, 2007
Messages
1,785
Likes
0
Points
0
#20
its a grandstream issue.....try 4024 1.0.4.2 firmware from this week....
 

Members online

No members online now.

Latest posts

Forum statistics

Threads
30,898
Messages
130,879
Members
17,560
Latest member
manuelc
Top