Вход | Регистрация
Вы здесь: Главная / Форум / Главный форум по Asterisk / Конфигурация и настройка / Asterisk + zaptel, как настроить факсы?

Asterisk + zaptel, как настроить факсы?

Откуда: Красноярск
Сообщений: 9

Asterisk + zaptel, как настроить факсы?

Добрый день! Взяли на тест TE122P, поставили на астериск 1.4.23.1. На * зарегестрировали AP100, если с него звонить на *, дальше по SIP лить на cisco 5350, и с него уже в ТфОП, то факсы ходят нормально по Т38. Если же с АддПака лить на * и далее через TE122P в ТфОП, то факсы не ходят, в городе факсы просто не понимают сигнал факса от платы, может где то надо для факсов параметр выставить? Спросил у производителей посоветовали убрать эхоподавление, убрал не помогло, подскажите кто сталкивался!!

zaptel.conf
span=1,1,0,ccs,hdb3
bchan=1-15,17-31
dchan=16
loadzone = us
defaultzone=us

zapata.conf
[channels]
group=1
signalling = pri_cpe
switchtype = qsig
echocancel=no
context = incoming
channel=1-15,17-31


[root@localhost a]# ztcfg -v
Zaptel Version: 1.4.12.1
Echo Canceller: MG2
Configuration
======================
SPAN 1: CCS/HDB3 Build-out: 0 db (CSU)/0-133 feet (DSX-1)
31 channels to configure.
Press any key to continue...
2009-03-19 12:56

Avatara of litnimax
Откуда: Москва
Сообщений: 3421

Re: Asterisk + zaptel, как настроить факсы?

Ну для начала покажите лог звонка с set verbose 5 / set debug 5.
http://pbxware.ru - все для Asterisk! || Switchvox - сделано на Asterisk! Подробности на http://switchvox.ru
2009-03-19 15:54

Откуда: Красноярск
Сообщений: 9

Re: Asterisk + zaptel, как настроить факсы?

Вот лог звонка (большой че то получился) когда звонок идет с АддПака на *, дальше через плату по Е1 на город. Факсы не проходят, после чего опять появляется голос.

[Mar 24 21:19:54] DEBUG[2407] chan_sip.c: = No match Their Call ID: 6B49B218A53D45EA89A9F8CDEAFFCD690xc382d605 Their Tag 6d9190b569c Our tag: as184f3478
[Mar 24 21:19:54] DEBUG[2407] chan_sip.c: Setting NAT on RTP to Off
[Mar 24 21:19:54] DEBUG[2407] chan_sip.c: Setting NAT on UDPTL to Off
[Mar 24 21:19:54] DEBUG[2407] chan_sip.c: Allocating new SIP dialog for 10320000-757f-45ad-802a-0002a405c6ca@192.168.123.171 - INVITE (With RTP)
[Mar 24 21:19:54] DEBUG[2407] chan_sip.c: **** Received INVITE (5) - Command in SIP INVITE
[Mar 24 21:19:54] DEBUG[2407] chan_sip.c: Setting NAT on RTP to On
[Mar 24 21:19:54] DEBUG[2407] chan_sip.c: Setting NAT on UDPTL to On
[Mar 24 21:19:54] DEBUG[2407] chan_sip.c: = Found Their Call ID: 10320000-757f-45ad-802a-0002a405c6ca@192.168.123.171 Their Tag 1000452aa4 Our tag: as12e2ebc3
[Mar 24 21:19:54] DEBUG[2407] chan_sip.c: **** Received ACK (6) - Command in SIP ACK
[Mar 24 21:19:54] DEBUG[2407] chan_sip.c: Stopping retransmission on '10320000-757f-45ad-802a-0002a405c6ca@192.168.123.171' of Response 25: Match Found
[Mar 24 21:19:54] DEBUG[2407] chan_sip.c: = Found Their Call ID: 10320000-757f-45ad-802a-0002a405c6ca@192.168.123.171 Their Tag 1000452aa4 Our tag: as12e2ebc3
[Mar 24 21:19:54] DEBUG[2407] chan_sip.c: **** Received INVITE (5) - Command in SIP INVITE
[Mar 24 21:19:54] DEBUG[2407] chan_sip.c: Setting NAT on RTP to On
[Mar 24 21:19:54] DEBUG[2407] chan_sip.c: Setting NAT on UDPTL to On
[Mar 24 21:19:54] DEBUG[2407] chan_sip.c: T38 state changed to 0 on channel <none>
[Mar 24 21:19:54] DEBUG[2407] chan_sip.c: We're settling with these formats: 0x100 (g729)
[Mar 24 21:19:54] DEBUG[2407] chan_sip.c: Checking SIP call limits for device 101
[Mar 24 21:19:54] DEBUG[2407] chan_sip.c: Updating call counter for incoming call
[Mar 24 21:19:54] DEBUG[2407] chan_sip.c: *** Our native formats are 0x100 (g729)
[Mar 24 21:19:54] DEBUG[2407] chan_sip.c: *** Joint capabilities are 0x100 (g729)
[Mar 24 21:19:54] DEBUG[2407] chan_sip.c: *** Our capabilities are 0x100 (g729)
[Mar 24 21:19:54] DEBUG[2407] chan_sip.c: *** AST_CODEC_CHOOSE formats are 0x100 (g729)
[Mar 24 21:19:54] DEBUG[2407] chan_sip.c: This channel will not be able to handle video.
[Mar 24 21:19:54] DEBUG[2407] chan_sip.c: build_route: Contact hop: <sip:101@192.168.123.171:5061>
[Mar 24 21:19:54] DEBUG[2407] chan_sip.c: SIP/101-b7d05ea0: New call is still down.... Trying...
[Mar 24 21:19:54] DEBUG[2407] devicestate.c: Notification of state change to be queued on device/channel SIP/101
[Mar 24 21:19:54] DEBUG[2316] devicestate.c: No provider found, checking channel drivers for SIP - 101
[Mar 24 21:19:54] DEBUG[2316] chan_sip.c: Checking device state for peer 101
[Mar 24 21:19:54] DEBUG[2316] devicestate.c: Changing state for SIP/101 - state 1 (Not in use)
[Mar 24 21:19:54] DEBUG[2404] app_queue.c: Device 'SIP/101' changed to state '1' (Not in use) but we don't care because they're not a member of any queue.
[Mar 24 21:19:54] DEBUG[2633] pbx.c: Launching 'Dial'
[Mar 24 21:19:54] VERBOSE[2633] logger.c: -- Executing [2745000@to_gorod:1] Dial("SIP/101-b7d05ea0", "ZAP/2/2745000||Tt") in new stack
[Mar 24 21:19:54] DEBUG[2633] chan_dahdi.c: Using channel 2
[Mar 24 21:19:54] DEBUG[2633] rtp.c: Channel 'Zap/2-1' has no RTP, not doing anything
[Mar 24 21:19:54] DEBUG[2633] channel.c: Not copying variable DIALEDTIME.
[Mar 24 21:19:54] DEBUG[2633] channel.c: Not copying variable ANSWEREDTIME.
[Mar 24 21:19:54] DEBUG[2633] channel.c: Not copying variable DIALEDPEERNAME.
[Mar 24 21:19:54] DEBUG[2633] channel.c: Not copying variable DIALEDPEERNUMBER.
[Mar 24 21:19:54] DEBUG[2633] channel.c: Not copying variable DIALSTATUS.
[Mar 24 21:19:54] DEBUG[2633] channel.c: Not copying variable SIPCALLID.
[Mar 24 21:19:54] DEBUG[2633] channel.c: Not copying variable SIPUSERAGENT.
[Mar 24 21:19:54] DEBUG[2633] channel.c: Not copying variable SIPDOMAIN.
[Mar 24 21:19:54] DEBUG[2633] channel.c: Not copying variable SIPURI.
[Mar 24 21:19:54] VERBOSE[2633] logger.c: -- Requested transfer capability: 0x00 - SPEECH
[Mar 24 21:19:54] DEBUG[2633] devicestate.c: Notification of state change to be queued on device/channel Zap/2
[Mar 24 21:19:54] DEBUG[2316] devicestate.c: No provider found, checking channel drivers for Zap - 2
[Mar 24 21:19:54] DEBUG[2316] channel.c: Avoiding initial deadlock for channel '0x8943fc8'
..........................................................................................
[Mar 24 21:19:54] DEBUG[2316] channel.c: Avoiding initial deadlock for channel '0x8943fc8'
[Mar 24 21:19:54] DEBUG[2316] devicestate.c: Changing state for Zap/2 - state 2 (In use)
[Mar 24 21:19:54] DEBUG[2404] app_queue.c: Device 'Zap/2' changed to state '2' (In use) but we don't care because they're not a member of any queue.
[Mar 24 21:19:54] VERBOSE[2633] logger.c: -- Called 2/2745000
[Mar 24 21:19:54] DEBUG[2633] channel.c: Set channel Zap/2-1 to read format g729
[Mar 24 21:19:54] DEBUG[2633] channel.c: Set channel SIP/101-b7d05ea0 to read format slin
[Mar 24 21:19:54] DEBUG[2633] channel.c: Set channel Zap/2-1 to write format slin
[Mar 24 21:19:54] DEBUG[2633] chan_sip.c: Setting framing from config on incoming call
[Mar 24 21:19:54] DEBUG[2633] chan_sip.c: ** Our capability: 0x100 (g729) Video flag: True
[Mar 24 21:19:54] DEBUG[2633] chan_sip.c: ** Our prefcodec: 0x0 (nothing)
[Mar 24 21:19:54] DEBUG[2633] chan_sip.c: -- Done with adding codecs to SDP
[Mar 24 21:19:54] DEBUG[2633] channel.c: Internal timing is disabled (option_internal_timing=1048576 chan->timingfd=-1)
[Mar 24 21:19:54] DEBUG[2633] chan_sip.c: Done building SDP. Settling with this capability: 0x100 (g729)
[Mar 24 21:19:54] DEBUG[2633] rtp.c: Ooh, format changed from unknown to g729
[Mar 24 21:19:54] DEBUG[2633] rtp.c: Created smoother: format: 256 ms: 20 len: 20
[Mar 24 21:19:56] DEBUG[2407] chan_sip.c: = No match Their Call ID: 10320000-757f-45ad-802a-0002a405c6ca@192.168.123.171 Their Tag 1000452aa4 Our tag: as203dfc4f
[Mar 24 21:19:56] DEBUG[2407] chan_sip.c: = No match Their Call ID: 6B49B218A53D45EA89A9F8CDEAFFCD690xc382d605 Their Tag 6d9190b569c Our tag: as184f3478
[Mar 24 21:19:56] DEBUG[2407] chan_sip.c: Allocating new SIP dialog for 0a000000-e91e-f167-8000-0002a405c6ca@192.168.123.171 - REGISTER (No RTP)
[Mar 24 21:19:56] DEBUG[2407] chan_sip.c: **** Received REGISTER (2) - Command in SIP REGISTER
[Mar 24 21:19:56] DEBUG[2407] chan_sip.c: = Found Their Call ID: 0a000000-e91e-f167-8000-0002a405c6ca@192.168.123.171 Their Tag 0a00f100a4 Our tag: as32211ac7
[Mar 24 21:19:56] DEBUG[2407] chan_sip.c: **** Received REGISTER (2) - Command in SIP REGISTER
[Mar 24 21:19:56] DEBUG[2407] chan_sip.c: Allocating new SIP dialog for (No Call-ID) - OPTIONS (No RTP)
[Mar 24 21:19:56] DEBUG[2407] devicestate.c: Notification of state change to be queued on device/channel SIP/101
[Mar 24 21:19:56] DEBUG[2316] devicestate.c: No provider found, checking channel drivers for SIP - 101
[Mar 24 21:19:56] DEBUG[2316] chan_sip.c: Checking device state for peer 101
[Mar 24 21:19:56] DEBUG[2316] devicestate.c: Changing state for SIP/101 - state 1 (Not in use)
[Mar 24 21:19:56] DEBUG[2404] app_queue.c: Device 'SIP/101' changed to state '1' (Not in use) but we don't care because they're not a member of any queue.
[Mar 24 21:19:56] DEBUG[2407] chan_sip.c: = Found Their Call ID: 7e6a52046e2ab6fd6c3856dd2b1b4787@192.168.123.216 Their Tag Our tag: as667d9f6d
[Mar 24 21:19:56] DEBUG[2407] chan_sip.c: Stopping retransmission on '7e6a52046e2ab6fd6c3856dd2b1b4787@192.168.123.216' of Request 102: Match Found
[Mar 24 21:19:56] VERBOSE[2407] logger.c: Really destroying SIP dialog '7e6a52046e2ab6fd6c3856dd2b1b4787@192.168.123.216' Method: OPTIONS
[Mar 24 21:19:59] DEBUG[2368] chan_dahdi.c: Queuing frame from PRI_EVENT_PROCEEDING on channel 0/2 span 1
[Mar 24 21:19:59] DEBUG[2368] chan_dahdi.c: Queuing frame from PRI_EVENT_PROGRESS on channel 0/2 span 1
[Mar 24 21:19:59] VERBOSE[2633] logger.c: -- Zap/2-1 is proceeding passing it to SIP/101-b7d05ea0
[Mar 24 21:19:59] DEBUG[2633] rtp.c: Channel 'Zap/2-1' has no RTP, not doing anything
[Mar 24 21:19:59] VERBOSE[2633] logger.c: -- Zap/2-1 is making progress passing it to SIP/101-b7d05ea0
[Mar 24 21:19:59] DEBUG[2633] rtp.c: Channel 'Zap/2-1' has no RTP, not doing anything
[Mar 24 21:20:00] DEBUG[2633] rtp.c: Got RTCP report of 84 bytes
[Mar 24 21:20:00] DEBUG[2368] chan_dahdi.c: Enabled echo cancellation on channel 2
[Mar 24 21:20:00] DEBUG[2633] devicestate.c: Notification of state change to be queued on device/channel Zap/2
[Mar 24 21:20:00] DEBUG[2316] devicestate.c: No provider found, checking channel drivers for Zap - 2
[Mar 24 21:20:00] DEBUG[2316] channel.c: Avoiding initial deadlock for channel '0x8943fc8'
.........................................................................................
[Mar 24 21:20:00] DEBUG[2316] channel.c: Avoiding initial deadlock for channel '0x8943fc8'
[Mar 24 21:20:00] DEBUG[2316] devicestate.c: Changing state for Zap/2 - state 6 (Ringing)
[Mar 24 21:20:00] DEBUG[2404] app_queue.c: Device 'Zap/2' changed to state '6' (Ringing) but we don't care because they're not a member of any queue.
[Mar 24 21:20:00] VERBOSE[2633] logger.c: -- Zap/2-1 is ringing
[Mar 24 21:20:00] DEBUG[2633] rtp.c: Channel 'Zap/2-1' has no RTP, not doing anything
[Mar 24 21:20:00] DEBUG[2368] chan_dahdi.c: Echo cancellation already on
[Mar 24 21:20:00] DEBUG[2633] devicestate.c: Notification of state change to be queued on device/channel Zap/2
[Mar 24 21:20:00] DEBUG[2316] devicestate.c: No provider found, checking channel drivers for Zap - 2
[Mar 24 21:20:00] DEBUG[2316] channel.c: Avoiding initial deadlock for channel '0x8943fc8'
.........................................................................................
[Mar 24 21:20:00] DEBUG[2316] channel.c: Avoiding initial deadlock for channel '0x8943fc8'
[Mar 24 21:20:00] DEBUG[2316] devicestate.c: Changing state for Zap/2 - state 2 (In use)
[Mar 24 21:20:00] DEBUG[2404] app_queue.c: Device 'Zap/2' changed to state '2' (In use) but we don't care because they're not a member of any queue.
[Mar 24 21:20:00] VERBOSE[2633] logger.c: -- Zap/2-1 answered SIP/101-b7d05ea0
[Mar 24 21:20:00] DEBUG[2633] devicestate.c: Notification of state change to be queued on device/channel SIP/101
[Mar 24 21:20:00] DEBUG[2316] devicestate.c: No provider found, checking channel drivers for SIP - 101
[Mar 24 21:20:00] DEBUG[2316] chan_sip.c: Checking device state for peer 101
[Mar 24 21:20:00] DEBUG[2316] devicestate.c: Changing state for SIP/101 - state 1 (Not in use)
[Mar 24 21:20:00] DEBUG[2404] app_queue.c: Device 'SIP/101' changed to state '1' (Not in use) but we don't care because they're not a member of any queue.
[Mar 24 21:20:00] DEBUG[2633] chan_sip.c: SIP answering channel: SIP/101-b7d05ea0
[Mar 24 21:20:00] DEBUG[2633] chan_sip.c: Setting framing from config on incoming call
[Mar 24 21:20:00] DEBUG[2633] chan_sip.c: ** Our capability: 0x100 (g729) Video flag: True
[Mar 24 21:20:00] DEBUG[2633] chan_sip.c: ** Our prefcodec: 0x0 (nothing)
[Mar 24 21:20:00] DEBUG[2633] chan_sip.c: -- Done with adding codecs to SDP
[Mar 24 21:20:00] DEBUG[2633] channel.c: Internal timing is disabled (option_internal_timing=1048576 chan->timingfd=-1)
[Mar 24 21:20:00] DEBUG[2633] chan_sip.c: Done building SDP. Settling with this capability: 0x100 (g729)
[Mar 24 21:20:00] DEBUG[2633] chan_dahdi.c: Requested indication 20 on channel Zap/2-1
[Mar 24 21:20:00] DEBUG[2633] rtp.c: Created smoother: format: 256 ms: 20 len: 20
[Mar 24 21:20:00] DEBUG[2407] chan_sip.c: = No match Their Call ID: 0a000000-e91e-f167-8000-0002a405c6ca@192.168.123.171 Their Tag 0a00f100a4 Our tag: as32211ac7
[Mar 24 21:20:00] DEBUG[2407] chan_sip.c: = Found Their Call ID: 10320000-757f-45ad-802a-0002a405c6ca@192.168.123.171 Their Tag 1000452aa4 Our tag: as203dfc4f
[Mar 24 21:20:00] DEBUG[2407] chan_sip.c: **** Received ACK (6) - Command in SIP ACK
[Mar 24 21:20:00] DEBUG[2407] chan_sip.c: Stopping retransmission on '10320000-757f-45ad-802a-0002a405c6ca@192.168.123.171' of Response 26: Match Found
[Mar 24 21:20:05] DEBUG[2633] rtp.c: - RTP 2833 Event: 00000001 (len = 4)
[Mar 24 21:20:05] DEBUG[2633] rtp.c: Sending dtmf: 49 (1), at 192.168.123.171
[Mar 24 21:20:05] DEBUG[2633] channel.c: Got DTMF begin on channel (SIP/101-b7d05ea0)
[Mar 24 21:20:05] DEBUG[2633] chan_dahdi.c: Requested indication 20 on channel Zap/2-1
[Mar 24 21:20:05] DEBUG[2633] channel.c: Bridge stops bridging channels SIP/101-b7d05ea0 and Zap/2-1
[Mar 24 21:20:05] DEBUG[2633] chan_dahdi.c: Requested indication 20 on channel Zap/2-1
[Mar 24 21:20:05] DEBUG[2633] rtp.c: - RTP 2833 Event: 00000001 (len = 4)
[Mar 24 21:20:05] DEBUG[2633] rtp.c: - RTP 2833 Event: 00000001 (len = 4)
[Mar 24 21:20:05] DEBUG[2633] rtp.c: - RTP 2833 Event: 00000001 (len = 4)
[Mar 24 21:20:05] DEBUG[2633] rtp.c: - RTP 2833 Event: 00000001 (len = 4)
[Mar 24 21:20:05] DEBUG[2633] rtp.c: - RTP 2833 Event: 00000001 (len = 4)
[Mar 24 21:20:05] DEBUG[2633] rtp.c: - RTP 2833 Event: 00000001 (len = 4)
[Mar 24 21:20:05] DEBUG[2633] rtp.c: - RTP 2833 Event: 00000001 (len = 4)
[Mar 24 21:20:05] DEBUG[2633] rtp.c: - RTP 2833 Event: 00000001 (len = 4)
[Mar 24 21:20:05] DEBUG[2633] rtp.c: - RTP 2833 Event: 00000001 (len = 4)
[Mar 24 21:20:05] DEBUG[2633] rtp.c: - RTP 2833 Event: 00000001 (len = 4)
[Mar 24 21:20:05] DEBUG[2633] rtp.c: - RTP 2833 Event: 00000001 (len = 4)
[Mar 24 21:20:05] DEBUG[2633] rtp.c: Sending dtmf: 49 (1), at 192.168.123.171
[Mar 24 21:20:05] DEBUG[2633] channel.c: Got DTMF end on channel (SIP/101-b7d05ea0)
[Mar 24 21:20:05] DEBUG[2633] chan_dahdi.c: Requested indication 20 on channel Zap/2-1
[Mar 24 21:20:05] DEBUG[2633] channel.c: Bridge stops bridging channels SIP/101-b7d05ea0 and Zap/2-1
[Mar 24 21:20:05] DEBUG[2633] res_features.c: Feature interpret: chan=SIP/101-b7d05ea0, peer=Zap/2-1, code=1, sense=1, features=2 dynamic=atxfer
[Mar 24 21:20:05] DEBUG[2634] rtp.c: - RTP 2833 Event: 00000001 (len = 4)
[Mar 24 21:20:05] DEBUG[2633] chan_dahdi.c: Started VLDTMF digit '1'
[Mar 24 21:20:05] DEBUG[2634] rtp.c: - RTP 2833 Event: 00000001 (len = 4)
[Mar 24 21:20:05] DEBUG[2634] rtp.c: - RTP 2833 Event: 00000001 (len = 4)
[Mar 24 21:20:05] DEBUG[2634] rtp.c: - RTP 2833 Event: 00000001 (len = 4)
[Mar 24 21:20:05] DEBUG[2634] rtp.c: - RTP 2833 Event: 00000001 (len = 4)
[Mar 24 21:20:05] DEBUG[2634] rtp.c: - RTP 2833 Event: 00000001 (len = 4)
[Mar 24 21:20:05] DEBUG[2634] rtp.c: - RTP 2833 Event: 00000001 (len = 4)
[Mar 24 21:20:05] DEBUG[2634] rtp.c: - RTP 2833 Event: 00000001 (len = 4)
[Mar 24 21:20:05] DEBUG[2633] chan_dahdi.c: Ending VLDTMF digit '1'
[Mar 24 21:20:05] DEBUG[2633] chan_dahdi.c: Requested indication 20 on channel Zap/2-1
[Mar 24 21:20:05] DEBUG[2633] rtp.c: Difference is 1752, ms is 239
[Mar 24 21:20:05] DEBUG[2633] rtp.c: - RTP 2833 Event: 00000002 (len = 4)
[Mar 24 21:20:05] DEBUG[2633] rtp.c: Sending dtmf: 50 (2), at 192.168.123.171
[Mar 24 21:20:05] DEBUG[2633] channel.c: Got DTMF begin on channel (SIP/101-b7d05ea0)
[Mar 24 21:20:05] DEBUG[2633] chan_dahdi.c: Requested indication 20 on channel Zap/2-1
[Mar 24 21:20:05] DEBUG[2633] channel.c: Bridge stops bridging channels SIP/101-b7d05ea0 and Zap/2-1
[Mar 24 21:20:05] DEBUG[2633] chan_dahdi.c: Requested indication 20 on channel Zap/2-1
[Mar 24 21:20:05] DEBUG[2633] rtp.c: - RTP 2833 Event: 00000002 (len = 4)
[Mar 24 21:20:05] DEBUG[2633] rtp.c: - RTP 2833 Event: 00000002 (len = 4)
[Mar 24 21:20:05] DEBUG[2633] rtp.c: - RTP 2833 Event: 00000002 (len = 4)
[Mar 24 21:20:05] DEBUG[2633] rtp.c: - RTP 2833 Event: 00000002 (len = 4)
[Mar 24 21:20:05] DEBUG[2633] rtp.c: - RTP 2833 Event: 00000002 (len = 4)
[Mar 24 21:20:05] DEBUG[2633] rtp.c: - RTP 2833 Event: 00000002 (len = 4)
[Mar 24 21:20:05] DEBUG[2633] rtp.c: - RTP 2833 Event: 00000002 (len = 4)
[Mar 24 21:20:05] DEBUG[2633] rtp.c: - RTP 2833 Event: 00000002 (len = 4)
[Mar 24 21:20:05] DEBUG[2633] rtp.c: - RTP 2833 Event: 00000002 (len = 4)
[Mar 24 21:20:05] DEBUG[2633] rtp.c: - RTP 2833 Event: 00000002 (len = 4)
[Mar 24 21:20:05] DEBUG[2633] rtp.c: Sending dtmf: 50 (2), at 192.168.123.171
[Mar 24 21:20:05] DEBUG[2633] channel.c: Got DTMF end on channel (SIP/101-b7d05ea0)
[Mar 24 21:20:05] DEBUG[2633] chan_dahdi.c: Requested indication 20 on channel Zap/2-1
[Mar 24 21:20:05] DEBUG[2633] channel.c: Bridge stops bridging channels SIP/101-b7d05ea0 and Zap/2-1
[Mar 24 21:20:05] DEBUG[2633] res_features.c: Feature interpret: chan=SIP/101-b7d05ea0, peer=Zap/2-1, code=2, sense=1, features=2 dynamic=atxfer
[Mar 24 21:20:05] DEBUG[2634] rtp.c: - RTP 2833 Event: 00000002 (len = 4)
[Mar 24 21:20:05] DEBUG[2633] chan_dahdi.c: Started VLDTMF digit '2'
[Mar 24 21:20:05] DEBUG[2634] rtp.c: - RTP 2833 Event: 00000002 (len = 4)
[Mar 24 21:20:05] DEBUG[2634] rtp.c: - RTP 2833 Event: 00000002 (len = 4)
[Mar 24 21:20:05] DEBUG[2634] rtp.c: - RTP 2833 Event: 00000002 (len = 4)
[Mar 24 21:20:05] DEBUG[2634] rtp.c: - RTP 2833 Event: 00000002 (len = 4)
[Mar 24 21:20:06] DEBUG[2634] rtp.c: - RTP 2833 Event: 00000002 (len = 4)
[Mar 24 21:20:06] DEBUG[2634] rtp.c: - RTP 2833 Event: 00000002 (len = 4)
[Mar 24 21:20:06] DEBUG[2634] rtp.c: - RTP 2833 Event: 00000002 (len = 4)
[Mar 24 21:20:06] DEBUG[2633] chan_dahdi.c: Ending VLDTMF digit '2'
[Mar 24 21:20:06] DEBUG[2634] rtp.c: - RTP 2833 Event: 00000001 (len = 4)
[Mar 24 21:20:06] DEBUG[2634] rtp.c: Sending dtmf: 49 (1), at 192.168.123.171
[Mar 24 21:20:06] DEBUG[2634] rtp.c: - RTP 2833 Event: 00000001 (len = 4)
[Mar 24 21:20:06] DEBUG[2634] rtp.c: - RTP 2833 Event: 00000001 (len = 4)
[Mar 24 21:20:06] DEBUG[2634] rtp.c: - RTP 2833 Event: 00000001 (len = 4)
[Mar 24 21:20:06] DEBUG[2633] chan_dahdi.c: Requested indication 20 on channel Zap/2-1
[Mar 24 21:20:06] DEBUG[2633] rtp.c: - RTP 2833 Event: 00000001 (len = 4)
[Mar 24 21:20:06] DEBUG[2633] rtp.c: Difference is 1752, ms is 239
[Mar 24 21:20:06] DEBUG[2633] rtp.c: - RTP 2833 Event: 00000001 (len = 4)
[Mar 24 21:20:06] DEBUG[2633] rtp.c: - RTP 2833 Event: 00000001 (len = 4)
[Mar 24 21:20:06] DEBUG[2633] rtp.c: - RTP 2833 Event: 00000001 (len = 4)
[Mar 24 21:20:06] DEBUG[2633] rtp.c: - RTP 2833 Event: 00000001 (len = 4)
[Mar 24 21:20:06] DEBUG[2633] rtp.c: - RTP 2833 Event: 00000001 (len = 4)
[Mar 24 21:20:06] DEBUG[2633] rtp.c: - RTP 2833 Event: 00000001 (len = 4)
[Mar 24 21:20:06] DEBUG[2633] rtp.c: Sending dtmf: 49 (1), at 192.168.123.171
[Mar 24 21:20:06] DEBUG[2633] channel.c: Got DTMF begin on channel (SIP/101-b7d05ea0)
[Mar 24 21:20:06] DEBUG[2633] chan_dahdi.c: Requested indication 20 on channel Zap/2-1
[Mar 24 21:20:06] DEBUG[2633] channel.c: Bridge stops bridging channels SIP/101-b7d05ea0 and Zap/2-1
[Mar 24 21:20:06] DEBUG[2633] chan_dahdi.c: Requested indication 20 on channel Zap/2-1
[Mar 24 21:20:06] DEBUG[2633] rtp.c: - RTP 2833 Event: 00000001 (len = 4)
[Mar 24 21:20:06] DEBUG[2633] rtp.c: - RTP 2833 Event: 00000001 (len = 4)
[Mar 24 21:20:06] DEBUG[2633] rtp.c: - RTP 2833 Event: 00000001 (len = 4)
[Mar 24 21:20:06] DEBUG[2633] rtp.c: - RTP 2833 Event: 00000001 (len = 4)
[Mar 24 21:20:06] DEBUG[2633] rtp.c: Got RTCP report of 84 bytes
[Mar 24 21:20:06] DEBUG[2633] rtp.c: - RTP 2833 Event: 00000001 (len = 4)
[Mar 24 21:20:06] DEBUG[2633] rtp.c: - RTP 2833 Event: 00000001 (len = 4)
[Mar 24 21:20:06] DEBUG[2633] rtp.c: - RTP 2833 Event: 00000001 (len = 4)
[Mar 24 21:20:06] DEBUG[2633] rtp.c: - RTP 2833 Event: 00000001 (len = 4)
[Mar 24 21:20:06] DEBUG[2633] channel.c: Got DTMF end on channel (SIP/101-b7d05ea0)
[Mar 24 21:20:06] DEBUG[2633] chan_dahdi.c: Requested indication 20 on channel Zap/2-1
[Mar 24 21:20:06] DEBUG[2633] channel.c: Bridge stops bridging channels SIP/101-b7d05ea0 and Zap/2-1
[Mar 24 21:20:06] DEBUG[2633] res_features.c: Feature interpret: chan=SIP/101-b7d05ea0, peer=Zap/2-1, code=1, sense=1, features=2 dynamic=atxfer
[Mar 24 21:20:06] DEBUG[2633] chan_dahdi.c: Started VLDTMF digit '1'
[Mar 24 21:20:06] DEBUG[2633] chan_dahdi.c: Ending VLDTMF digit '1'
[Mar 24 21:20:06] DEBUG[2633] chan_dahdi.c: Requested indication 20 on channel Zap/2-1
[Mar 24 21:20:06] DEBUG[2633] rtp.c: Difference is 1752, ms is 239
[Mar 24 21:20:08] DEBUG[2407] chan_sip.c: Auto destroying SIP dialog '6B49B218A53D45EA89A9F8CDEAFFCD690xc382d605'
[Mar 24 21:20:08] DEBUG[2407] chan_sip.c: Destroying SIP dialog 6B49B218A53D45EA89A9F8CDEAFFCD690xc382d605
[Mar 24 21:20:08] VERBOSE[2407] logger.c: Really destroying SIP dialog '6B49B218A53D45EA89A9F8CDEAFFCD690xc382d605' Method: REGISTER
[Mar 24 21:20:10] DEBUG[2633] rtp.c: Got RTCP report of 84 bytes
[Mar 24 21:20:15] DEBUG[2633] rtp.c: Got RTCP report of 84 bytes
[Mar 24 21:20:21] DEBUG[2633] rtp.c: Got RTCP report of 84 bytes
[Mar 24 21:20:25] DEBUG[2633] rtp.c: Got RTCP report of 84 bytes
[Mar 24 21:20:28] DEBUG[2407] chan_sip.c: Auto destroying SIP dialog '0a000000-e91e-f167-8000-0002a405c6ca@192.168.123.171'
[Mar 24 21:20:28] DEBUG[2407] chan_sip.c: Destroying SIP dialog 0a000000-e91e-f167-8000-0002a405c6ca@192.168.123.171
[Mar 24 21:20:28] VERBOSE[2407] logger.c: Really destroying SIP dialog '0a000000-e91e-f167-8000-0002a405c6ca@192.168.123.171' Method: REGISTER
[Mar 24 21:20:28] DEBUG[2633] rtp.c: Got RTCP report of 84 bytes
[Mar 24 21:20:31] DEBUG[2633] rtp.c: Got RTCP report of 64 bytes
[Mar 24 21:20:34] DEBUG[2633] rtp.c: Got RTCP report of 64 bytes
[Mar 24 21:20:36] DEBUG[2407] chan_sip.c: Allocating new SIP dialog for (No Call-ID) - OPTIONS (No RTP)
[Mar 24 21:20:36] DEBUG[2407] chan_sip.c: = Found Their Call ID: 19b7a1dd4988e2d64a3bf2b81744dee3@192.168.123.216 Their Tag Our tag: as23c5550d
[Mar 24 21:20:36] DEBUG[2407] chan_sip.c: Stopping retransmission on '19b7a1dd4988e2d64a3bf2b81744dee3@192.168.123.216' of Request 102: Match Found
[Mar 24 21:20:36] VERBOSE[2407] logger.c: Really destroying SIP dialog '19b7a1dd4988e2d64a3bf2b81744dee3@192.168.123.216' Method: OPTIONS
[Mar 24 21:20:38] DEBUG[2633] rtp.c: Got RTCP report of 64 bytes
[Mar 24 21:20:44] DEBUG[2633] rtp.c: Got RTCP report of 64 bytes
[Mar 24 21:20:44] DEBUG[2407] chan_sip.c: = No match Their Call ID: 10320000-757f-45ad-802a-0002a405c6ca@192.168.123.171 Their Tag 1000452aa4 Our tag: as203dfc4f
[Mar 24 21:20:44] DEBUG[2407] chan_sip.c: Allocating new SIP dialog for 0a000000-e91e-f167-8000-0002a405c6ca@192.168.123.171 - REGISTER (No RTP)
[Mar 24 21:20:44] DEBUG[2407] chan_sip.c: **** Received REGISTER (2) - Command in SIP REGISTER
[Mar 24 21:20:44] DEBUG[2407] chan_sip.c: = Found Their Call ID: 0a000000-e91e-f167-8000-0002a405c6ca@192.168.123.171 Their Tag 0a00f100a4 Our tag: as372f8443
[Mar 24 21:20:44] DEBUG[2407] chan_sip.c: **** Received REGISTER (2) - Command in SIP REGISTER
[Mar 24 21:20:44] DEBUG[2407] chan_sip.c: Allocating new SIP dialog for (No Call-ID) - OPTIONS (No RTP)
[Mar 24 21:20:44] DEBUG[2407] devicestate.c: Notification of state change to be queued on device/channel SIP/101
[Mar 24 21:20:44] DEBUG[2316] devicestate.c: No provider found, checking channel drivers for SIP - 101
[Mar 24 21:20:44] DEBUG[2316] chan_sip.c: Checking device state for peer 101
[Mar 24 21:20:44] DEBUG[2316] devicestate.c: Changing state for SIP/101 - state 1 (Not in use)
[Mar 24 21:20:44] DEBUG[2404] app_queue.c: Device 'SIP/101' changed to state '1' (Not in use) but we don't care because they're not a member of any queue.
[Mar 24 21:20:44] DEBUG[2407] chan_sip.c: = Found Their Call ID: 33df9ba4698a7dd9385fd3f90450b96c@192.168.123.216 Their Tag Our tag: as78940cf7
[Mar 24 21:20:44] DEBUG[2407] chan_sip.c: Stopping retransmission on '33df9ba4698a7dd9385fd3f90450b96c@192.168.123.216' of Request 102: Match Found
[Mar 24 21:20:44] VERBOSE[2407] logger.c: Really destroying SIP dialog '33df9ba4698a7dd9385fd3f90450b96c@192.168.123.216' Method: OPTIONS
[Mar 24 21:20:50] DEBUG[2633] rtp.c: Got RTCP report of 64 bytes
[Mar 24 21:20:55] DEBUG[2633] rtp.c: Got RTCP report of 64 bytes
[Mar 24 21:21:02] DEBUG[2633] rtp.c: Got RTCP report of 64 bytes
[Mar 24 21:21:08] DEBUG[2633] rtp.c: Got RTCP report of 64 bytes
[Mar 24 21:21:10] DEBUG[2633] rtp.c: Got RTCP report of 64 bytes
[Mar 24 21:21:16] DEBUG[2407] chan_sip.c: Auto destroying SIP dialog '0a000000-e91e-f167-8000-0002a405c6ca@192.168.123.171'
[Mar 24 21:21:16] DEBUG[2407] chan_sip.c: Destroying SIP dialog 0a000000-e91e-f167-8000-0002a405c6ca@192.168.123.171
[Mar 24 21:21:16] VERBOSE[2407] logger.c: Really destroying SIP dialog '0a000000-e91e-f167-8000-0002a405c6ca@192.168.123.171' Method: REGISTER
[Mar 24 21:21:16] DEBUG[2633] rtp.c: Got RTCP report of 64 bytes
[Mar 24 21:21:23] DEBUG[2633] rtp.c: Got RTCP report of 64 bytes
[Mar 24 21:21:30] DEBUG[2633] rtp.c: Got RTCP report of 64 bytes
[Mar 24 21:21:32] DEBUG[2407] chan_sip.c: = No match Their Call ID: 10320000-757f-45ad-802a-0002a405c6ca@192.168.123.171 Their Tag 1000452aa4 Our tag: as203dfc4f
[Mar 24 21:21:32] DEBUG[2407] chan_sip.c: Allocating new SIP dialog for 0a000000-e91e-f167-8000-0002a405c6ca@192.168.123.171 - REGISTER (No RTP)
[Mar 24 21:21:32] DEBUG[2407] chan_sip.c: **** Received REGISTER (2) - Command in SIP REGISTER
[Mar 24 21:21:32] DEBUG[2407] chan_sip.c: = Found Their Call ID: 0a000000-e91e-f167-8000-0002a405c6ca@192.168.123.171 Their Tag 0a00f100a4 Our tag: as5d332a93
[Mar 24 21:21:32] DEBUG[2407] chan_sip.c: **** Received REGISTER (2) - Command in SIP REGISTER
[Mar 24 21:21:32] DEBUG[2407] chan_sip.c: Allocating new SIP dialog for (No Call-ID) - OPTIONS (No RTP)
[Mar 24 21:21:32] DEBUG[2407] devicestate.c: Notification of state change to be queued on device/channel SIP/101
[Mar 24 21:21:32] DEBUG[2316] devicestate.c: No provider found, checking channel drivers for SIP - 101
[Mar 24 21:21:32] DEBUG[2316] chan_sip.c: Checking device state for peer 101
[Mar 24 21:21:32] DEBUG[2316] devicestate.c: Changing state for SIP/101 - state 1 (Not in use)
[Mar 24 21:21:32] DEBUG[2404] app_queue.c: Device 'SIP/101' changed to state '1' (Not in use) but we don't care because they're not a member of any queue.
[Mar 24 21:21:32] DEBUG[2407] chan_sip.c: = Found Their Call ID: 0c0a1b6104930de27fcc66ba56610294@192.168.123.216 Their Tag Our tag: as249744f7
[Mar 24 21:21:32] DEBUG[2407] chan_sip.c: Stopping retransmission on '0c0a1b6104930de27fcc66ba56610294@192.168.123.216' of Request 102: Match Found
[Mar 24 21:21:32] VERBOSE[2407] logger.c: Really destroying SIP dialog '0c0a1b6104930de27fcc66ba56610294@192.168.123.216' Method: OPTIONS
[Mar 24 21:21:33] DEBUG[2633] rtp.c: Got RTCP report of 84 bytes
[Mar 24 21:21:36] DEBUG[2407] chan_sip.c: = No match Their Call ID: 0a000000-e91e-f167-8000-0002a405c6ca@192.168.123.171 Their Tag 0a00f100a4 Our tag: as5d332a93
[Mar 24 21:21:36] DEBUG[2407] chan_sip.c: = No match Their Call ID: 10320000-757f-45ad-802a-0002a405c6ca@192.168.123.171 Their Tag 1000452aa4 Our tag: as203dfc4f
[Mar 24 21:21:36] DEBUG[2407] chan_sip.c: Allocating new SIP dialog for 6B49B218A53D45EA89A9F8CDEAFFCD690xc382d605 - REGISTER (No RTP)
[Mar 24 21:21:36] DEBUG[2407] chan_sip.c: **** Received REGISTER (2) - Command in SIP REGISTER
[Mar 24 21:21:36] DEBUG[2407] chan_sip.c: = Found Their Call ID: 6B49B218A53D45EA89A9F8CDEAFFCD690xc382d605 Their Tag 1489190d2b6c Our tag: as07e14300
[Mar 24 21:21:36] DEBUG[2407] chan_sip.c: **** Received REGISTER (2) - Command in SIP REGISTER
[Mar 24 21:21:36] DEBUG[2407] chan_sip.c: Allocating new SIP dialog for (No Call-ID) - OPTIONS (No RTP)
[Mar 24 21:21:36] DEBUG[2407] devicestate.c: Notification of state change to be queued on device/channel SIP/VitaliyNikolaevich2
[Mar 24 21:21:36] DEBUG[2316] devicestate.c: No provider found, checking channel drivers for SIP - VitaliyNikolaevich2
[Mar 24 21:21:36] DEBUG[2316] chan_sip.c: Checking device state for peer VitaliyNikolaevich2
[Mar 24 21:21:36] DEBUG[2316] devicestate.c: Changing state for SIP/VitaliyNikolaevich2 - state 1 (Not in use)
[Mar 24 21:21:36] DEBUG[2404] app_queue.c: Device 'SIP/VitaliyNikolaevich2' changed to state '1' (Not in use) but we don't care because they're not a member of any queue.
[Mar 24 21:21:36] DEBUG[2407] chan_sip.c: = Found Their Call ID: 5e3041e64184fb5b73a616230c046275@192.168.123.216 Their Tag Our tag: as06845d7e
[Mar 24 21:21:36] DEBUG[2407] chan_sip.c: Stopping retransmission on '5e3041e64184fb5b73a616230c046275@192.168.123.216' of Request 102: Match Found
[Mar 24 21:21:36] VERBOSE[2407] logger.c: Really destroying SIP dialog '5e3041e64184fb5b73a616230c046275@192.168.123.216' Method: OPTIONS
[Mar 24 21:21:37] DEBUG[2633] rtp.c: Got RTCP report of 84 bytes
[Mar 24 21:21:41] DEBUG[2633] rtp.c: Got RTCP report of 84 bytes
[Mar 24 21:21:42] VERBOSE[2368] logger.c: -- Channel 0/2, span 1 got hangup request, cause 16


2009-03-24 10:45

Откуда: Красноярск
Сообщений: 9

Re: Asterisk + zaptel, как настроить факсы?

А вообще есть люди у которых бы через платы на астериске, ходили бы факсы из сипа в тфоп?
2009-03-25 06:19

Avatara of switch
Откуда: Уфа
Сообщений: 5856

Re: Asterisk + zaptel, как настроить факсы?

у меня ходят по G711.
http://www.lynks.ru - Решения телефонии, мини-АТС, VoIP на основе Trixbox и Asterisk
2009-03-25 09:39

Сообщений: 866

Re: Asterisk + zaptel, как настроить факсы?

v1t83:

А вообще есть люди у которых бы через платы на астериске, ходили бы факсы из сипа в тфоп?
если по g711 то может. а из T38 делать "обычный" аналоговый факс астериск не умеет.
2009-03-25 21:28

Добавить страницу в закладки:  Delicious Google Slashdot Yahoo Yandex.ru Reddit Digg Technorati Bobrdobr.ru Newsland.ru Smi2.ru Rumarkz.ru Vaau.ru Memori.ru Rucity.com Moemesto.ru News2.ru Mister-Wong.ru Myscoop.ru 100zakladok.ru