forum.bitel.ru :: Просмотр темы - монитор модуля VoiceIP и наработка пусты

08-18/15:27:11 INFO [main] DefaultServerSetup - Binding javax.jms.ConnectionFactory[org.apache.activemq.ActiveMQConnectionFactory@480bdb19] to java:comp/env/mq/connectionFactory
08-18/15:27:11 INFO [main] DefaultServerSetup - Init DB connection pools
08-18/15:27:11 INFO [main] DefaultServerSetup - Binding JDBC pool "master" to java:comp/env/jdbc/master
08-18/15:27:12 INFO [main] AnnotatedMBean - Register MBean ru.bitel.bgbilling.server.util:type=DatabaseConnectionPool,name=master
08-18/15:27:13 INFO [main] DefaultServerSetup - Init trash pools..
08-18/15:27:16 INFO [main] DefaultServerSetup - Init trash pools..
08-18/15:27:22 INFO [main] Radius - Starting radius auth_port:1822 acct_port:1823 admin_port:2056
08-18/15:27:23 INFO [main] Radius - Init processor
class: ru.bitel.bgbilling.modules.voiceip.radius.VoiceIpRadiusProcessor
mid: 5
08-18/15:27:23 INFO [main] radius - Eap not enabled (keystore file not loaded).
08-18/15:27:24 INFO [main] Radius - Starting authentication listener...
08-18/15:27:24 INFO [main] Setup - Load config for mid=5
08-18/15:27:24 INFO [main] DatagramChannelListener - Open socket [0.0.0.0/0.0.0.0:1822]
08-18/15:27:24 INFO [main] DatagramChannelListener - ru.bitel.bgbilling.kernel.network.radius.RadiusListener socket init ok.
08-18/15:27:24 INFO [main] Radius - Starting accounting listener...
08-18/15:27:24 INFO [main] DatagramChannelListener - Open socket [0.0.0.0/0.0.0.0:1823]
08-18/15:27:24 INFO [main] DatagramChannelListener - ru.bitel.bgbilling.kernel.network.radius.RadiusListener socket init ok.
08-18/15:27:24 INFO [Thread-13] AdminPortListener - Starting AdminPortListener on 2056
08-18/15:27:42 INFO [rdsLstnr-p-4-t-1] RadiusListenerWorker - REQUEST:
Packet type: Accounting-Request
Identifier: 151
Authenticator: {E6 C9 38 2C 03 B5 44 29 40 37 D2 B8 F3 20 E2 82}
Attributes:
User-Name=XXXXXXX
NAS-IP-Address=XXX.XXX.XX.X
Service-Type=1
Acct-Status-Type=1
Acct-Delay-Time=0
Acct-Session-Id=00005933
Acct-Authentic=2
Called-Station-Id=YYYYYYYYYYYYYY
Calling-Station-Id=XXXXXXX
cisco-avpair=call-id=4abc536072e4950938031d28796bf9a3@XXX.XXX.XX.X
cisco-avpair=iphop=count:1
cisco-avpair=iphop=hop1:XXX.XXX.XX.Y
cisco-avpair=h323-incoming-conf-id=F8DA7E39 44DA11E5 9D61E634 15FCFF90
cisco-avpair=subscriber=Unknown
cisco-avpair=session-protocol=sipv2
cisco-avpair=gw-rxd-cdn=ton:0,npi:0,#:YYYYYYYYYYYYYY
cisco-avpair=feature-vsa=fn:TWC,ft:08/18/2015 12:24:57.341,cgn:XXXXXXX,cdn:YYYYYYYYYYYYYY,frs:0,fid:2506,fcid:F8DA7E3944DA11E59D61E63415FCFF90,legID:C29
cisco-avpair=connect-progress=Call Up
h323-gw-id=testtest
h323-conf-id=F8DA7E39 44DA11E5 9D61E634 15FCFF90
h323-setup-time=*12:24:57.341 UTC Tue Aug 18 2015
h323-call-origin=answer
h323-call-type=VoIP

08-18/15:27:43 INFO [rdsLstnr-p-4-t-1] RadiusListenerWorker - RESPONSE:
Packet type: Accounting-Response
Identifier: 151
Authenticator: {6F 01 50 68 AE 0F DE 90 99 15 A6 52 4E 0C C6 58}
Attributes:

Process time start: 30

08-18/15:27:43 INFO [rdsLstnr-p-4-t-2] RadiusListenerWorker - REQUEST:
Packet type: Accounting-Request
Identifier: 152
Authenticator: {8B A3 68 DE F0 67 DC 87 76 57 26 48 BF 24 DE 9D}
Attributes:
User-Name=XXXXXXX
NAS-IP-Address=XXX.XXX.XX.X
NAS-Port=22837
Service-Type=1
NAS-Port-Id=ISDN 0/2/0:15:8
Acct-Status-Type=1
Acct-Delay-Time=0
Acct-Session-Id=00005935
Acct-Authentic=2
NAS-Port-Type=0
Called-Station-Id=YYYYYYYYYYYYYY
Calling-Station-Id=XXXXXXX
h323-gw-id=testtest
cisco-avpair=h323-incoming-conf-id=F8DA7E39 44DA11E5 9D61E634 15FCFF90
cisco-avpair=subscriber=Unknown
cisco-avpair=gw-rxd-cdn=ton:0,npi:0,#:YYYYYYYYYYYYYY
cisco-avpair=feature-vsa=fn:TWC,ft:08/18/2015 12:24:57.361,cgn:XXXXXXX,cdn:YYYYYYYYYYYYYY,frs:0,fid:2507,fcid:F8DA7E3944DA11E59D61E63415FCFF90,legID:C2A
cisco-avpair=connect-progress=Call Up
h323-conf-id=F8DA7E39 44DA11E5 9D61E634 15FCFF90
h323-setup-time=*12:24:57.593 UTC Tue Aug 18 2015
h323-call-origin=originate
h323-call-type=Telephony

08-18/15:27:43 INFO [rdsLstnr-p-4-t-2] RadiusListenerWorker - RESPONSE:
Packet type: Accounting-Response
Identifier: 152
Authenticator: {D3 37 05 7C 0A 06 1F B7 64 DD EF 78 89 1F 03 54}
Attributes:

Process time start: 15

08-18/15:28:04 INFO [rdsLstnr-p-4-t-3] RadiusListenerWorker - REQUEST:
Packet type: Accounting-Request
Identifier: 153
Authenticator: {EE BE 11 9D 79 2E B1 E6 49 0F 2E 23 CD 94 4F E4}
Attributes:
User-Name=XXXXXXX
NAS-IP-Address=XXX.XXX.XX.X
Service-Type=1
Acct-Status-Type=2
Acct-Delay-Time=0
Acct-Input-Octets=167680
Acct-Output-Octets=168320
Acct-Session-Id=00005933
Acct-Authentic=2
Acct-Session-Time=13
Acct-Input-Packets=1048
Acct-Output-Packets=1052
Called-Station-Id=YYYYYYYYYYYYYY
Calling-Station-Id=XXXXXXX
cisco-avpair=call-id=4abc536072e4950938031d28796bf9a3@XXX.XXX.XX.X
cisco-avpair=iphop=count:1
cisco-avpair=iphop=hop1:XXX.XXX.XX.Y
cisco-avpair=h323-incoming-conf-id=F8DA7E39 44DA11E5 9D61E634 15FCFF90
cisco-avpair=subscriber=Unknown
cisco-avpair=session-protocol=sipv2
cisco-avpair=gw-rxd-cdn=ton:0,npi:0,#:YYYYYYYYYYYYYY
cisco-avpair=feature-vsa=fn:TWC,ft:08/18/2015 12:24:57.341,cgn:XXXXXXX,cdn:YYYYYYYYYYYYYY,frs:0,fid:2506,fcid:F8DA7E3944DA11E59D61E63415FCFF90,legID:C29
cisco-avpair=release-source=2
cisco-avpair=remote-media-address=XXX.XXX.XX.Y
cisco-avpair=gw-rxd-cgn=ton:0,npi:0,pi:0,si:0,#:5953681
h323-gw-id=testtest
h323-remote-address=XXX.XXX.XX.Y
h323-conf-id=F8DA7E39 44DA11E5 9D61E634 15FCFF90
h323-setup-time=*12:24:57.341 UTC Tue Aug 18 2015
h323-call-origin=answer
h323-call-type=VoIP
h323-connect-time=*12:25:05.425 UTC Tue Aug 18 2015
h323-disconnect-time=*12:25:18.875 UTC Tue Aug 18 2015
h323-disconnect-cause=10
h323-voice-quality=0

08-18/15:28:04 INFO [rdsLstnr-p-4-t-4] RadiusListenerWorker - REQUEST:
Packet type: Accounting-Request
Identifier: 154
Authenticator: {4C C4 35 70 BE EB 42 B6 FF F1 0C 7B D3 B1 9C 87}
Attributes:
User-Name=XXXXXXX
NAS-IP-Address=XXX.XXX.XX.X
NAS-Port=22837
Service-Type=1
Acct-Status-Type=2
Acct-Delay-Time=0
Acct-Input-Octets=176064
Acct-Output-Octets=168320
Acct-Session-Id=00005935
Acct-Authentic=2
Acct-Session-Time=13
Acct-Input-Packets=1048
Acct-Output-Packets=1052
NAS-Port-Id=ISDN 0/2/0:15:8
NAS-Port-Type=0
Called-Station-Id=YYYYYYYYYYYYYY
Calling-Station-Id=XXXXXXX
h323-gw-id=testtest
cisco-avpair=h323-incoming-conf-id=F8DA7E39 44DA11E5 9D61E634 15FCFF90
cisco-avpair=subscriber=Unknown
cisco-avpair=gw-rxd-cdn=ton:0,npi:0,#:YYYYYYYYYYYYYY
cisco-avpair=feature-vsa=fn:TWC,ft:08/18/2015 12:24:57.361,cgn:XXXXXXX,cdn:YYYYYYYYYYYYYY,frs:0,fid:2507,fcid:F8DA7E3944DA11E59D61E63415FCFF90,legID:C2A
cisco-avpair=h323-ivr-out=Tariff:Unknown
cisco-avpair=release-source=3
cisco-avpair=alert-timepoint=*12:25:02.783 UTC Tue Aug 18 2015
cisco-avpair=dsp-id=0/1:1
cisco-avpair=gw-rxd-cgn=ton:0,npi:0,pi:0,si:0,#:XXXXXXX
cisco-avpair=gw-final-xlated-cdn=ton:0,npi:0,#:YYYYYYYYYYY
cisco-avpair=gw-final-xlated-cgn=ton:0,npi:0,pi:0,si:0,#:XXXXXXX
h323-conf-id=F8DA7E39 44DA11E5 9D61E634 15FCFF90
h323-setup-time=*12:24:57.593 UTC Tue Aug 18 2015
h323-call-origin=originate
h323-call-type=Telephony
h323-connect-time=*12:25:05.417 UTC Tue Aug 18 2015
h323-disconnect-time=*12:25:18.913 UTC Tue Aug 18 2015
h323-disconnect-cause=10
h323-voice-quality=0

08-18/15:28:04 INFO [rdsLstnr-p-4-t-3] RadiusListenerWorker - RESPONSE:
Packet type: Accounting-Response
Identifier: 153
Authenticator: {87 39 F0 E0 C4 5A A2 AD 98 2E FB 3C 25 84 A1 F8}
Attributes:

Process time stop: 123

08-18/15:28:04 INFO [rdsLstnr-p-4-t-4] RadiusListenerWorker - RESPONSE:
Packet type: Accounting-Response
Identifier: 154
Authenticator: {9C 8D 70 9D 29 46 C8 E0 EC DB 32 FF E4 84 5F 87}
Attributes:

Process time stop: 121

Автор:	ilenka [ 18 авг 2015, 18:41 ]
Заголовок сообщения:	монитор модуля VoiceIP и наработка пусты
Настроен модуль VoiceIp по документации. Необходим исключительно аккаунтинг, без авторизации. Настройка NAS Код: service=12 acct.out=all/all find.order=3 acct.logError=1 В договоре заведен логин с алиасом равным адресу NAS, режим поиска происходит по h323-remote-address=ALIAS. в radius.log данные есть, в наработке и в мониторе никакие логи не отображаются. radius.log Код: 08-18/15:27:11 INFO [main] DefaultServerSetup - Binding javax.jms.ConnectionFactory[org.apache.activemq.ActiveMQConnectionFactory@480bdb19] to java:comp/env/mq/connectionFactory 08-18/15:27:11 INFO [main] DefaultServerSetup - Init DB connection pools 08-18/15:27:11 INFO [main] DefaultServerSetup - Binding JDBC pool "master" to java:comp/env/jdbc/master 08-18/15:27:12 INFO [main] AnnotatedMBean - Register MBean ru.bitel.bgbilling.server.util:type=DatabaseConnectionPool,name=master 08-18/15:27:13 INFO [main] DefaultServerSetup - Init trash pools.. 08-18/15:27:16 INFO [main] DefaultServerSetup - Init trash pools.. 08-18/15:27:22 INFO [main] Radius - Starting radius auth_port:1822 acct_port:1823 admin_port:2056 08-18/15:27:23 INFO [main] Radius - Init processor class: ru.bitel.bgbilling.modules.voiceip.radius.VoiceIpRadiusProcessor mid: 5 08-18/15:27:23 INFO [main] radius - Eap not enabled (keystore file not loaded). 08-18/15:27:24 INFO [main] Radius - Starting authentication listener... 08-18/15:27:24 INFO [main] Setup - Load config for mid=5 08-18/15:27:24 INFO [main] DatagramChannelListener - Open socket [0.0.0.0/0.0.0.0:1822] 08-18/15:27:24 INFO [main] DatagramChannelListener - ru.bitel.bgbilling.kernel.network.radius.RadiusListener socket init ok. 08-18/15:27:24 INFO [main] Radius - Starting accounting listener... 08-18/15:27:24 INFO [main] DatagramChannelListener - Open socket [0.0.0.0/0.0.0.0:1823] 08-18/15:27:24 INFO [main] DatagramChannelListener - ru.bitel.bgbilling.kernel.network.radius.RadiusListener socket init ok. 08-18/15:27:24 INFO [Thread-13] AdminPortListener - Starting AdminPortListener on 2056 08-18/15:27:42 INFO [rdsLstnr-p-4-t-1] RadiusListenerWorker - REQUEST: Packet type: Accounting-Request Identifier: 151 Authenticator: {E6 C9 38 2C 03 B5 44 29 40 37 D2 B8 F3 20 E2 82} Attributes: User-Name=XXXXXXX NAS-IP-Address=XXX.XXX.XX.X Service-Type=1 Acct-Status-Type=1 Acct-Delay-Time=0 Acct-Session-Id=00005933 Acct-Authentic=2 Called-Station-Id=YYYYYYYYYYYYYY Calling-Station-Id=XXXXXXX cisco-avpair=call-id=4abc536072e4950938031d28796bf9a3@XXX.XXX.XX.X cisco-avpair=iphop=count:1 cisco-avpair=iphop=hop1:XXX.XXX.XX.Y cisco-avpair=h323-incoming-conf-id=F8DA7E39 44DA11E5 9D61E634 15FCFF90 cisco-avpair=subscriber=Unknown cisco-avpair=session-protocol=sipv2 cisco-avpair=gw-rxd-cdn=ton:0,npi:0,#:YYYYYYYYYYYYYY cisco-avpair=feature-vsa=fn:TWC,ft:08/18/2015 12:24:57.341,cgn:XXXXXXX,cdn:YYYYYYYYYYYYYY,frs:0,fid:2506,fcid:F8DA7E3944DA11E59D61E63415FCFF90,legID:C29 cisco-avpair=connect-progress=Call Up h323-gw-id=testtest h323-conf-id=F8DA7E39 44DA11E5 9D61E634 15FCFF90 h323-setup-time=12:24:57.341 UTC Tue Aug 18 2015 h323-call-origin=answer h323-call-type=VoIP 08-18/15:27:43 INFO [rdsLstnr-p-4-t-1] RadiusListenerWorker - RESPONSE: Packet type: Accounting-Response Identifier: 151 Authenticator: {6F 01 50 68 AE 0F DE 90 99 15 A6 52 4E 0C C6 58} Attributes: Process time start: 30 08-18/15:27:43 INFO [rdsLstnr-p-4-t-2] RadiusListenerWorker - REQUEST: Packet type: Accounting-Request Identifier: 152 Authenticator: {8B A3 68 DE F0 67 DC 87 76 57 26 48 BF 24 DE 9D} Attributes: User-Name=XXXXXXX NAS-IP-Address=XXX.XXX.XX.X NAS-Port=22837 Service-Type=1 NAS-Port-Id=ISDN 0/2/0:15:8 Acct-Status-Type=1 Acct-Delay-Time=0 Acct-Session-Id=00005935 Acct-Authentic=2 NAS-Port-Type=0 Called-Station-Id=YYYYYYYYYYYYYY Calling-Station-Id=XXXXXXX h323-gw-id=testtest cisco-avpair=h323-incoming-conf-id=F8DA7E39 44DA11E5 9D61E634 15FCFF90 cisco-avpair=subscriber=Unknown cisco-avpair=gw-rxd-cdn=ton:0,npi:0,#:YYYYYYYYYYYYYY cisco-avpair=feature-vsa=fn:TWC,ft:08/18/2015 12:24:57.361,cgn:XXXXXXX,cdn:YYYYYYYYYYYYYY,frs:0,fid:2507,fcid:F8DA7E3944DA11E59D61E63415FCFF90,legID:C2A cisco-avpair=connect-progress=Call Up h323-conf-id=F8DA7E39 44DA11E5 9D61E634 15FCFF90 h323-setup-time=12:24:57.593 UTC Tue Aug 18 2015 h323-call-origin=originate h323-call-type=Telephony 08-18/15:27:43 INFO [rdsLstnr-p-4-t-2] RadiusListenerWorker - RESPONSE: Packet type: Accounting-Response Identifier: 152 Authenticator: {D3 37 05 7C 0A 06 1F B7 64 DD EF 78 89 1F 03 54} Attributes: Process time start: 15 08-18/15:28:04 INFO [rdsLstnr-p-4-t-3] RadiusListenerWorker - REQUEST: Packet type: Accounting-Request Identifier: 153 Authenticator: {EE BE 11 9D 79 2E B1 E6 49 0F 2E 23 CD 94 4F E4} Attributes: User-Name=XXXXXXX NAS-IP-Address=XXX.XXX.XX.X Service-Type=1 Acct-Status-Type=2 Acct-Delay-Time=0 Acct-Input-Octets=167680 Acct-Output-Octets=168320 Acct-Session-Id=00005933 Acct-Authentic=2 Acct-Session-Time=13 Acct-Input-Packets=1048 Acct-Output-Packets=1052 Called-Station-Id=YYYYYYYYYYYYYY Calling-Station-Id=XXXXXXX cisco-avpair=call-id=4abc536072e4950938031d28796bf9a3@XXX.XXX.XX.X cisco-avpair=iphop=count:1 cisco-avpair=iphop=hop1:XXX.XXX.XX.Y cisco-avpair=h323-incoming-conf-id=F8DA7E39 44DA11E5 9D61E634 15FCFF90 cisco-avpair=subscriber=Unknown cisco-avpair=session-protocol=sipv2 cisco-avpair=gw-rxd-cdn=ton:0,npi:0,#:YYYYYYYYYYYYYY cisco-avpair=feature-vsa=fn:TWC,ft:08/18/2015 12:24:57.341,cgn:XXXXXXX,cdn:YYYYYYYYYYYYYY,frs:0,fid:2506,fcid:F8DA7E3944DA11E59D61E63415FCFF90,legID:C29 cisco-avpair=release-source=2 cisco-avpair=remote-media-address=XXX.XXX.XX.Y cisco-avpair=gw-rxd-cgn=ton:0,npi:0,pi:0,si:0,#:5953681 h323-gw-id=testtest h323-remote-address=XXX.XXX.XX.Y h323-conf-id=F8DA7E39 44DA11E5 9D61E634 15FCFF90 h323-setup-time=12:24:57.341 UTC Tue Aug 18 2015 h323-call-origin=answer h323-call-type=VoIP h323-connect-time=12:25:05.425 UTC Tue Aug 18 2015 h323-disconnect-time=12:25:18.875 UTC Tue Aug 18 2015 h323-disconnect-cause=10 h323-voice-quality=0 08-18/15:28:04 INFO [rdsLstnr-p-4-t-4] RadiusListenerWorker - REQUEST: Packet type: Accounting-Request Identifier: 154 Authenticator: {4C C4 35 70 BE EB 42 B6 FF F1 0C 7B D3 B1 9C 87} Attributes: User-Name=XXXXXXX NAS-IP-Address=XXX.XXX.XX.X NAS-Port=22837 Service-Type=1 Acct-Status-Type=2 Acct-Delay-Time=0 Acct-Input-Octets=176064 Acct-Output-Octets=168320 Acct-Session-Id=00005935 Acct-Authentic=2 Acct-Session-Time=13 Acct-Input-Packets=1048 Acct-Output-Packets=1052 NAS-Port-Id=ISDN 0/2/0:15:8 NAS-Port-Type=0 Called-Station-Id=YYYYYYYYYYYYYY Calling-Station-Id=XXXXXXX h323-gw-id=testtest cisco-avpair=h323-incoming-conf-id=F8DA7E39 44DA11E5 9D61E634 15FCFF90 cisco-avpair=subscriber=Unknown cisco-avpair=gw-rxd-cdn=ton:0,npi:0,#:YYYYYYYYYYYYYY cisco-avpair=feature-vsa=fn:TWC,ft:08/18/2015 12:24:57.361,cgn:XXXXXXX,cdn:YYYYYYYYYYYYYY,frs:0,fid:2507,fcid:F8DA7E3944DA11E59D61E63415FCFF90,legID:C2A cisco-avpair=h323-ivr-out=Tariff:Unknown cisco-avpair=release-source=3 cisco-avpair=alert-timepoint=12:25:02.783 UTC Tue Aug 18 2015 cisco-avpair=dsp-id=0/1:1 cisco-avpair=gw-rxd-cgn=ton:0,npi:0,pi:0,si:0,#:XXXXXXX cisco-avpair=gw-final-xlated-cdn=ton:0,npi:0,#:YYYYYYYYYYY cisco-avpair=gw-final-xlated-cgn=ton:0,npi:0,pi:0,si:0,#:XXXXXXX h323-conf-id=F8DA7E39 44DA11E5 9D61E634 15FCFF90 h323-setup-time=12:24:57.593 UTC Tue Aug 18 2015 h323-call-origin=originate h323-call-type=Telephony h323-connect-time=12:25:05.417 UTC Tue Aug 18 2015 h323-disconnect-time=*12:25:18.913 UTC Tue Aug 18 2015 h323-disconnect-cause=10 h323-voice-quality=0 08-18/15:28:04 INFO [rdsLstnr-p-4-t-3] RadiusListenerWorker - RESPONSE: Packet type: Accounting-Response Identifier: 153 Authenticator: {87 39 F0 E0 C4 5A A2 AD 98 2E FB 3C 25 84 A1 F8} Attributes: Process time stop: 123 08-18/15:28:04 INFO [rdsLstnr-p-4-t-4] RadiusListenerWorker - RESPONSE: Packet type: Accounting-Response Identifier: 154 Authenticator: {9C 8D 70 9D 29 46 C8 E0 EC DB 32 FF E4 84 5F 87} Attributes: Process time stop: 121 версия клиента 6.2.726, версия сервера 6.2.907, версия VoiceIp 6.2.165

Автор:	stark [ 14 сен 2015, 17:15 ]
Заголовок сообщения:	Re: монитор модуля VoiceIP и наработка пусты
там сессия должна появится только после stop-пакета. Включите режим логирования в debug и покажите что в логах.

Автор:	ilenka [ 17 сен 2015, 19:12 ]
Заголовок сообщения:	Re: монитор модуля VoiceIP и наработка пусты
stark, уже не актуально все заработало.

forum.bitel.ru http://forum.bitel.ru/

монитор модуля VoiceIP и наработка пусты http://forum.bitel.ru/viewtopic.php?f=6&t=10808	Страница 1 из 1

Страница 1 из 1	Часовой пояс: UTC + 5 часов [ Летнее время ]
Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/