cisco-isdn-troubleshooting
====================================================================================
Не работает перевод звонка SIP абонента C3945 между Panasonic-1 и Panasonic-2
Две АТС Panasonic-1, Panasonic-2 с установленными PRI платами подключены к C3945 с двумя потоками E1.
1 2 3 |
---Panasonic-1--- ----CISCO---- ---Panasonic-2--- |KXTDA-100 PRI30| --qsig-- |E1 C3945 E1| --qsig-- |PRI30 KXTDA-100| ----------------- ------------- ----------------- |
Тип сигнализации используется QSIG
Описание проблемы:
1. Абонент Panasonic-1 звонит SIP абоненту C3945 — телефонный разговор установлен.
2. Абонент Panasonic-1 переводит звонок (кнопка Transfer) на абонента Panasonic-2 — телефонный разговор между абонентами Panasonic-1 и Panasonic-2 установлен , SIP абонент на удержании (музыка играет)
3. Абонент Panasonic-1 кладет трубку: абонент Panasonic-2 тишина, SIP абонент продолжает слушать музыку.
На пункте 3 следующие логи:
1 2 3 4 5 6 7 8 9 10 11 12 13 |
Feb 13 17:46:42.066: ISDN Se0/3/1:15 Q931: RX <- FACILITY pd = 8 callref = 0x002E Facility i = 0x91AA06800100820100A10B02016006042B0C09070500 Feb 13 17:46:42.066: ISDN Se0/3/1:15 **ERROR**: isdn_init_fac_data: No Opval 0 Feb 13 17:46:42.066: ISDN Se0/2/1:15 Q931: TX -> FACILITY pd = 8 callref = 0x00A1 Facility i = 0x91AA06800100820100A10B02016006042B0C09070500 Feb 13 17:46:42.098: ISDN Se0/2/1:15 Q931: RX <- FACILITY pd = 8 callref = 0x80A1 Facility i = 0x91AA06800100820100A217020160301206042B0C0907300A12023736800432303030 netdd01-gwint1# Feb 13 17:46:42.102: ISDN Se0/3/1:15 Q931: TX -> FACILITY pd = 8 callref = 0x802E Facility i = 0x91AA06800100820100A217020160301206042B0C0907300A12023736800432303030 Feb 13 17:46:42.138: ISDN Se0/3/1:15 Q931: RX <- FACILITY pd = 8 callref = 0x002D Facility i = 0x91AA06800100820100A11502016106042B0C0909300A12023736800432303030 Feb 13 17:46:42.138: ISDN Se0/3/1:15 **ERROR**: isdn_init_fac_data: No Opval 0 |
Декодим Facility ошибки http://decoder.telemak.org/
1 2 |
Feb 13 17:46:42.138: ISDN Se0/3/1:15 Q931: RX <- FACILITY pd = 8 callref = 0x002D Facility i = 0x91AA06800100820100A11502016106042B0C0909300A12023736800432303030 |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 |
Q.931 Facility INV: callTransferInitiate Type: Facility (0x1c) Length: 32 ...1 0001 = Protocol profile: Remote Operations Protocol (0x11) NetworkFacilityExtension sourceEntity: endPINX (0) destinationEntity: endPINX (0) ROS: invoke (1) invoke invokeId: present (0) present: 97 opcode: global (1) global: 1.3.12.9.9 (iso.3.12.9.9) - callTransferInitiate argument: 300a12023736800432303030 QSIG: callTransferInitiate Operation: callTransferInitiate (9) Service: QSIG-CT (13869) - Call-Transfer-Operations CTInitiateArg callIdentity: 76 rerouteingNumber: unknownPartyNumber (0) unknownPartyNumber: 2000 |
CISCO не понимает supplementary service приходящий от Panasonic когда требуется перевести звонок «Service: QSIG-CT (13869) — Call-Transfer-Operations».
Решение: в настройках PRI платы, вкладке «supplementary service» отключить «CT»
====================================================================================
Не работает поток E1
Не поднимается Serial0/2/0:15 соответственно поток E1 не работает.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 |
#sh ip interface Serial0/2/0:15 Interface IP-Address OK? Method Status Protocol Serial0/2/0:15 unassigned YES unset down down netdd01-gwint1#sh controllers e1 0/2/0 br E1 0/2/0 is down. Applique type is Channelized E1 - balanced Transmitter is sending TS16 LOMF Alarm. Receiver has loss of multi-frame in TS16. alarm-trigger is not set Version info FPGA Rev: 08121917, FPGA Type: PRK4 Framing is CRC4, Line Code is HDB3, Clock Source is Internal. International Bit: 1, National Bits: 11111 Data in current interval (347 seconds elapsed): 0 Line Code Violations, 6 Path Code Violations 0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins 0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 347 Unavail Secs Total Data (last 24 hours) 4391 Line Code Violations, 0 Path Code Violations, 0 Slip Secs, 0 Fr Loss Secs, 1 Line Err Secs, 0 Degraded Mins, 0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 86400 Unavail Secs # sh isdn status Serial 0/2/0:15 ISDN Serial0/2/0:15 interface ******* Network side configuration ******* dsl 1, interface ISDN Switchtype = primary-net5 Layer 1 Status: DEACTIVATED Layer 2 Status: TEI = 0, Ces = 1, SAPI = 0, State = TEI_ASSIGNED Layer 3 Status: 0 Active Layer 3 Call(s) Active dsl 1 CCBs = 0 The Free Channel Mask: 0x00000000 Number of L2 Discards = 0, L2 Session ID = 0 Total Allocated ISDN CCBs = 0 # |
Решение:
1 2 3 4 5 6 7 8 |
(config)# controller e1 0/2/0 (config-controller)# framing no-crc4 Проверяем #show ip interface brief Serial 0/2/0:15 Interface IP-Address OK? Method Status Protocol Serial0/2/0:15 unassigned YES unset up up |
====================================================================================
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 |
#sh controllers e1 0/2/0 br E1 0/2/0 is up. Applique type is Channelized E1 - balanced Description: **ISDN_E1*** Far End Block Errors Detected No alarms detected. alarm-trigger is not set Version info FPGA Rev: 08121917, FPGA Type: PRK4 Framing is CRC4, Line Code is HDB3, Clock Source is Line. International Bit: 1, National Bits: 11111 Data in current interval (823 seconds elapsed): 0 Line Code Violations, 72335 Path Code Violations 0 Slip Secs, 823 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins 0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 823 Unavail Secs Total Data (last 24 hours) 0 Line Code Violations, 3835271 Path Code Violations, 0 Slip Secs, 33006 Fr Loss Secs, 0 Line Err Secs, 248 Degraded Mins, 15187 Errored Secs, 15056 Bursty Err Secs, 120 Severely Err Secs, 32886 Unavail Secs |
Cisco говорит:
Path Code Violations Increasing
http://www.cisco.com/c/en/us/support/docs/wan/t1-e1-t3-e3/14171-T1-error.html
A Path code violation error event is a frame synchronization bit error in the D4 (SF) format, or a CRC error in the ESF format. Path code violations and line code violations are typically present simultaneously. Always verify that your line coding is correct.Ensure the line coding configured on the port matches the line coding of the line. Look for «Line Code is {B8ZS|AMI}» in the show controller t1 output.
To change the line coding, use the linecode {ami | b8zs} command in controller configuration mode. For example:
maui-nas-03(config-controlle)#linecode b8zs
Change the line build-out using the cablelength long or cablelength short command.Contact your Service Provider and consult the T1/E1 Controller Commands documentation for details on build-out settings.
===============================================================
CME SIP-телефоны перерегистрируются каждые 10 минут
1 2 3 4 5 6 7 8 |
#sh sip timers SIP UA Timer Values (millisecs unless noted) trying 500, expires 180000, connect 500, disconnect 500 prack 500, rel1xx 500, notify 500, update 500 refer 500, register 500, info 500, options 500, hold 2880 minutes , registrar-dns-cache 3600 seconds tcp/udp aging 5 minutes tls aging 60 minutes |
В логах телефона наблюдаем:
2299 DEB 20:20:52.408601 JAVA: SIPCC-SIP_TCP_MSG: sip_tcp_read_socket: CUCM closed TCP connection.
2300 ERR 20:20:52.408769 JAVA: SIP : sip_tcp_read_socket : socket error=2
re-registration_after_10_min_messages.3
Смотрим время последней регистрации телефона
1 2 3 4 5 |
sh voice regi pool 3 Last register request time : 20:20:54.909 SMR Sat Mar 21 2015 Last unregister request time : 21:10:58.111 SMR Sat Mar 21 2015 Register success time : 20:20:54.909 SMR Sat Mar 21 2015 Unregister success time : 21:10:58.111 SMR Sat Mar 21 2015 |
Необходимо установить значение voice service voip -> sip -> registrar server expires max 300 min 150 , которое ниже значения sip таймера = 500
1 2 3 4 5 6 7 8 9 10 11 12 13 14 |
#sh run | s voice ser voice service pots voice service voip ip address trusted list ipv4 0.0.0.0 allow-connections h323 to h323 allow-connections h323 to sip allow-connections sip to h323 allow-connections sip to sip fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback none sip registrar server expires max 300 min 150 no call service stop voice service saf |
===============================================================
SIP-абонент не слышит PBX-абонента за потоком E1
При использовании кодека g729 с установленным параметром bytes свыше 120, SIP-абонент не слышит PBX-абонент, а PBX-абонент слышит.
Решение: использовать кодек g729 с установленным параметром bytes <= 120.
voice register pool 3
busy-trigger-per-button 2
id mac F09E.636E.A8D5
session-transport tcp
type 7841
number 1 dn 3
presence call-list
dtmf-relay sip-notify
voice-class codec 10
username 2372 password 2372
no vad
voice class codec 10
codec preference 1 g729r8 bytes 120
codec preference 3 g711ulaw bytes 240
Добавить комментарий