forum.bitel.ru http://forum.bitel.ru/ |
|
Неизвестное направление http://forum.bitel.ru/viewtopic.php?f=6&t=10860 |
Страница 1 из 1 |
Автор: | ilenka [ 04 сен 2015, 17:33 ] |
Заголовок сообщения: | Неизвестное направление |
Добрый день! версия клиента 6.2.726, версия сервера 6.2.907, версия VoiceIp 6.2.165 Настроен аккаунтинг, без авторизации. Настройка NAS. acct.out=voip/answer acct.in=voip/originate service=12 find.order=1,4 В договоре заведен логин с алиасом равным телефону, режим поиска ACCT OUT по User-Name=Alias, ACCT IN по Called-Station-Id=ALIAS. В географических кодах модуля voice ip создала 2 направления: 1. all с кодом 0207 2. russia с кодом 7. завела простой тарифный план Вложение: tarif.jpeg [ 36.52 КБ | Просмотров: 2504 ] в наработке везде неизвестное направление. лог радиуса ниже Код: 09-04/14:28:26 INFO [main] DefaultServerSetup - Binding javax.jms.ConnectionFactory[org.apache.activemq.ActiveMQConnectionFactory@480bdb19] to java:comp/env/mq/connectionFactory 09-04/14:28:26 INFO [main] DefaultServerSetup - Init DB connection pools 09-04/14:28:26 INFO [main] DefaultServerSetup - Binding JDBC pool "master" to java:comp/env/jdbc/master 09-04/14:28:26 INFO [main] AnnotatedMBean - Register MBean ru.bitel.bgbilling.server.util:type=DatabaseConnectionPool,name=master 09-04/14:28:28 INFO [main] DefaultServerSetup - Init trash pools.. 09-04/14:28:30 INFO [main] DefaultServerSetup - Init trash pools.. 09-04/14:28:36 INFO [main] Radius - Starting radius auth_port:1822 acct_port:1823 admin_port:2056 09-04/14:28:37 INFO [main] Radius - Init processor class: ru.bitel.bgbilling.modules.voiceip.radius.VoiceIpRadiusProcessor mid: 5 09-04/14:28:37 INFO [main] radius - Eap not enabled (keystore file not loaded). 09-04/14:28:38 INFO [main] Radius - Starting authentication listener... 09-04/14:28:38 INFO [main] Setup - Load config for mid=5 09-04/14:28:38 INFO [main] DatagramChannelListener - Open socket [0.0.0.0/0.0.0.0:1822] 09-04/14:28:38 INFO [main] DatagramChannelListener - ru.bitel.bgbilling.kernel.network.radius.RadiusListener socket init ok. 09-04/14:28:38 INFO [main] Radius - Starting accounting listener... 09-04/14:28:38 INFO [main] DatagramChannelListener - Open socket [0.0.0.0/0.0.0.0:1823] 09-04/14:28:38 INFO [main] DatagramChannelListener - ru.bitel.bgbilling.kernel.network.radius.RadiusListener socket init ok. 09-04/14:28:38 INFO [Thread-13] AdminPortListener - Starting AdminPortListener on 2056 09-04/14:28:47 INFO [rdsLstnr-p-4-t-1] RadiusListenerWorker - REQUEST: Packet type: Accounting-Request Identifier: 206 Authenticator: {46 BB 3C 7A 1D 1C 4C 98 59 A9 13 5F F9 B7 32 E8} Attributes: User-Name=595XXXX NAS-IP-Address=1.1.1.1 NAS-Port=33775 Service-Type=1 NAS-Port-Id=ISDN 0/2/0:15:8 Acct-Status-Type=1 Acct-Delay-Time=18 Acct-Session-Id=000083EF Acct-Authentic=2 NAS-Port-Type=0 Called-Station-Id=0207921XXXXXXX Calling-Station-Id=595XXXX h323-gw-id=YA_NE cisco-avpair=h323-incoming-conf-id=D88BDC2A 522E11E5 AE43E634 15FCFF90 cisco-avpair=subscriber=Unknown cisco-avpair=gw-rxd-cdn=ton:0,npi:0,#:0207921XXXXXXX cisco-avpair=feature-vsa=fn:TWC,ft:09/04/2015 11:28:05.992,cgn:595XXXX,cdn:0207921XXXXXXX,frs:0,fid:3948,fcid:D88BDC2A522E11E5AE43E63415FCFF90,legID:1334 cisco-avpair=connect-progress=Call Up h323-conf-id=D88BDC2A 522E11E5 AE43E634 15FCFF90 h323-setup-time=*11:28:06.172 UTC Fri Sep 4 2015 h323-call-origin=originate h323-call-type=Telephony 09-04/14:28:47 INFO [rdsLstnr-p-4-t-1] RadiusListenerWorker - RESPONSE: Packet type: Accounting-Response Identifier: 206 Authenticator: {75 79 95 4C 96 00 9D 95 0D 71 B0 87 06 1F 9A C6} Attributes: Process time start: 35 09-04/14:28:48 INFO [rdsLstnr-p-4-t-2] RadiusListenerWorker - REQUEST: Packet type: Accounting-Request Identifier: 207 Authenticator: {D4 C7 30 1C 56 96 CF A9 CD 66 91 A7 7B 36 3D 7F} Attributes: User-Name=595XXXX NAS-IP-Address=1.1.1.1 Service-Type=1 Acct-Status-Type=1 Acct-Delay-Time=19 Acct-Session-Id=000083ED Acct-Authentic=2 Called-Station-Id=0207921XXXXXXX Calling-Station-Id=595XXXX cisco-avpair=call-id=23df45cb77210fb222fa479d5f8f4b23@1.1.1.1 cisco-avpair=iphop=count:1 cisco-avpair=iphop=hop1:1.1.1.2 cisco-avpair=h323-incoming-conf-id=D88BDC2A 522E11E5 AE43E634 15FCFF90 cisco-avpair=subscriber=Unknown cisco-avpair=session-protocol=sipv2 cisco-avpair=gw-rxd-cdn=ton:0,npi:0,#:0207921XXXXXXX cisco-avpair=feature-vsa=fn:TWC,ft:09/04/2015 11:28:05.976,cgn:595XXXX,cdn:0207921XXXXXXX,frs:0,fid:3947,fcid:D88BDC2A522E11E5AE43E63415FCFF90,legID:1333 cisco-avpair=connect-progress=Call Up h323-gw-id=YA_NE h323-conf-id=D88BDC2A 522E11E5 AE43E634 15FCFF90 h323-setup-time=*11:28:05.980 UTC Fri Sep 4 2015 h323-call-origin=answer h323-call-type=VoIP 09-04/14:28:48 INFO [rdsLstnr-p-4-t-2] RadiusListenerWorker - RESPONSE: Packet type: Accounting-Response Identifier: 207 Authenticator: {47 1A 1A CB 13 0C 39 A9 FE 16 99 7A 92 AA 16 6B} Attributes: Process time start: 10 09-04/14:28:50 INFO [rdsLstnr-p-4-t-3] RadiusListenerWorker - REQUEST: Packet type: Accounting-Request Identifier: 208 Authenticator: {C6 12 9F 6F FD A0 B2 85 0D C5 F1 BB 65 52 B5 F3} Attributes: User-Name=595XXXX NAS-IP-Address=1.1.1.1 Service-Type=1 Acct-Status-Type=2 Acct-Delay-Time=0 Acct-Input-Octets=125600 Acct-Output-Octets=126400 Acct-Session-Id=000083ED Acct-Authentic=2 Acct-Session-Time=13 Acct-Input-Packets=785 Acct-Output-Packets=790 Called-Station-Id=0207921XXXXXXX Calling-Station-Id=595XXXX cisco-avpair=call-id=23df45cb77210fb222fa479d5f8f4b23@1.1.1.1 cisco-avpair=iphop=count:1 cisco-avpair=iphop=hop1:1.1.1.2 cisco-avpair=h323-incoming-conf-id=D88BDC2A 522E11E5 AE43E634 15FCFF90 cisco-avpair=subscriber=Unknown cisco-avpair=session-protocol=sipv2 cisco-avpair=gw-rxd-cdn=ton:0,npi:0,#:0207921XXXXXXX cisco-avpair=feature-vsa=fn:TWC,ft:09/04/2015 11:28:05.976,cgn:595XXXX,cdn:0207921XXXXXXX,frs:0,fid:3947,fcid:D88BDC2A522E11E5AE43E63415FCFF90,legID:1333 cisco-avpair=release-source=2 cisco-avpair=remote-media-address=1.1.1.106 cisco-avpair=gw-rxd-cgn=ton:0,npi:0,pi:0,si:0,#:595XXXX h323-gw-id=YA_NE h323-remote-address=1.1.1.106 h323-conf-id=D88BDC2A 522E11E5 AE43E634 15FCFF90 h323-setup-time=*11:28:05.980 UTC Fri Sep 4 2015 h323-call-origin=answer h323-call-type=VoIP h323-connect-time=*11:28:14.732 UTC Fri Sep 4 2015 h323-disconnect-time=*11:28:27.614 UTC Fri Sep 4 2015 h323-disconnect-cause=10 h323-voice-quality=0 09-04/14:28:50 INFO [rdsLstnr-p-4-t-4] RadiusListenerWorker - REQUEST: Packet type: Accounting-Request Identifier: 209 Authenticator: {03 FE 96 1B 97 7E 1D 25 1D 1E 49 8F 50 8E 9E DA} Attributes: User-Name=595XXXX NAS-IP-Address=1.1.1.1 NAS-Port=33775 Service-Type=1 Acct-Status-Type=2 Acct-Delay-Time=0 Acct-Input-Octets=131880 Acct-Output-Octets=126400 Acct-Session-Id=000083EF Acct-Authentic=2 Acct-Session-Time=13 Acct-Input-Packets=785 Acct-Output-Packets=790 NAS-Port-Id=ISDN 0/2/0:15:8 NAS-Port-Type=0 Called-Station-Id=0207921XXXXXXX Calling-Station-Id=595XXXX h323-gw-id=YA_NE cisco-avpair=h323-incoming-conf-id=D88BDC2A 522E11E5 AE43E634 15FCFF90 cisco-avpair=subscriber=Unknown cisco-avpair=gw-rxd-cdn=ton:0,npi:0,#:0207921XXXXXXX cisco-avpair=feature-vsa=fn:TWC,ft:09/04/2015 11:28:05.992,cgn:595XXXX,cdn:0207921XXXXXXX,frs:0,fid:3948,fcid:D88BDC2A522E11E5AE43E63415FCFF90,legID:1334 cisco-avpair=h323-ivr-out=Tariff:Unknown cisco-avpair=release-source=3 cisco-avpair=alert-timepoint=*11:28:11.790 UTC Fri Sep 4 2015 cisco-avpair=dsp-id=0/1:1 cisco-avpair=gw-rxd-cgn=ton:0,npi:0,pi:0,si:0,#:595XXXX cisco-avpair=gw-final-xlated-cdn=ton:0,npi:0,#:8921XXXXXXX cisco-avpair=gw-final-xlated-cgn=ton:0,npi:0,pi:0,si:0,#:595XXXX h323-conf-id=D88BDC2A 522E11E5 AE43E634 15FCFF90 h323-setup-time=*11:28:06.172 UTC Fri Sep 4 2015 h323-call-origin=originate h323-call-type=Telephony h323-connect-time=*11:28:14.724 UTC Fri Sep 4 2015 h323-disconnect-time=*11:28:27.640 UTC Fri Sep 4 2015 h323-disconnect-cause=10 h323-voice-quality=0 09-04/14:28:50 ERROR [rdsLstnr-p-4-t-4] VoiceIpRadiusProcessor - Call type not recognized Packet type: Accounting-Request Identifier: 209 Authenticator: {03 FE 96 1B 97 7E 1D 25 1D 1E 49 8F 50 8E 9E DA} Attributes: User-Name=595XXXX NAS-IP-Address=1.1.1.1 NAS-Port=33775 Service-Type=1 Acct-Status-Type=2 Acct-Delay-Time=0 Acct-Input-Octets=131880 Acct-Output-Octets=126400 Acct-Session-Id=000083EF Acct-Authentic=2 Acct-Session-Time=13 Acct-Input-Packets=785 Acct-Output-Packets=790 NAS-Port-Id=ISDN 0/2/0:15:8 NAS-Port-Type=0 Called-Station-Id=0207921XXXXXXX Calling-Station-Id=595XXXX h323-gw-id=YA_NE cisco-avpair=h323-incoming-conf-id=D88BDC2A 522E11E5 AE43E634 15FCFF90 cisco-avpair=subscriber=Unknown cisco-avpair=gw-rxd-cdn=ton:0,npi:0,#:0207921XXXXXXX cisco-avpair=feature-vsa=fn:TWC,ft:09/04/2015 11:28:05.992,cgn:595XXXX,cdn:0207921XXXXXXX,frs:0,fid:3948,fcid:D88BDC2A522E11E5AE43E63415FCFF90,legID:1334 cisco-avpair=h323-ivr-out=Tariff:Unknown cisco-avpair=release-source=3 cisco-avpair=alert-timepoint=*11:28:11.790 UTC Fri Sep 4 2015 cisco-avpair=dsp-id=0/1:1 cisco-avpair=gw-rxd-cgn=ton:0,npi:0,pi:0,si:0,#:595XXXX cisco-avpair=gw-final-xlated-cdn=ton:0,npi:0,#:8921XXXXXXX cisco-avpair=gw-final-xlated-cgn=ton:0,npi:0,pi:0,si:0,#:595XXXX h323-conf-id=D88BDC2A 522E11E5 AE43E634 15FCFF90 h323-setup-time=*11:28:06.172 UTC Fri Sep 4 2015 h323-call-origin=originate h323-call-type=Telephony h323-connect-time=*11:28:14.724 UTC Fri Sep 4 2015 h323-disconnect-time=*11:28:27.640 UTC Fri Sep 4 2015 h323-disconnect-cause=10 h323-voice-quality=0 09-04/14:28:50 INFO [rdsLstnr-p-4-t-4] RadiusListenerWorker - RESPONSE: Packet type: Accounting-Response Identifier: 209 Authenticator: {52 E2 A3 12 33 1C FB 1F DA C5 D7 A6 02 07 09 72} Attributes: Process time stop: 73 09-04/14:28:50 INFO [rdsLstnr-p-4-t-3] CostMapCache - (Re)loading costMap cache and geo codes for mid 5 09-04/14:28:50 INFO [rdsLstnr-p-4-t-3] RadiusListenerWorker - RESPONSE: Packet type: Accounting-Response Identifier: 208 Authenticator: {8C F6 E6 6F 39 4E 71 15 90 27 A9 CF EB B7 9F B9} Attributes: Process time stop: 428 Что не так настроено?? ![]() |
Автор: | Amir [ 04 сен 2015, 20:39 ] |
Заголовок сообщения: | Re: Неизвестное направление |
Эта ветка устанавливает направление, только если внутри нее есть ветка часть префикса, к которой подойдет звонок. Вместо нее можно попробовать просто ветку часть префикса, внутри которой установлено направление. Значение части префикса можно оставить пустым или указать . (т.к. там можно указывать regexp). |
Автор: | ilenka [ 07 сен 2015, 14:42 ] |
Заголовок сообщения: | Re: Неизвестное направление |
Amir, сделала как вы написали. В географических кодах модуля voice ip добавила Питер. 1. all с кодом 0207 2. russia с кодом 7. 2a. spb 7812 Тариф сделала следующий Вложение: 1.jpeg [ 34.32 КБ | Просмотров: 2483 ] По-прежнему неизвестное направление. отбой, заработало ![]() |
Страница 1 из 1 | Часовой пояс: UTC + 5 часов [ Летнее время ] |
Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/ |