Cisco 2901 отбой при звонке в группу

All Activity

Reply to this topic

uvaxut

Posted February 8, 2022

Добрый день.

Имею Cisco 2901, подключенную по sip к avaya. На циске заерегены телефоны csico 7941 по sccp и 7841 по sip. Имеется voice hunt-group parallel. Есть куча телефонов, зареганых на avaya. Чтобы понять логи и конфу напишу пояснение:

1. Номер 6930 - это номер, которым циска подключена к авайе как UA . Этот номер матчится на voice hunt-group с пилотом 1780

2. Номер 1012 - это номер sccp телефона на циске

3. Номер 1107 - это номер sip телефона на циске

4.Номер 7097 - это номер с которого я звоню на 6930

5. Номер 7299 - это номер, которым циска подключена к авайе как UA . Этот номер матчится на 1107

При наборе с определенных телефонов на номер 6930, подключенных к авайе происходит отбой звонка. Если звонить с 7097 мимо хант группы на номер 7299, то звонок проходит нормально.

Если из хант группы убрать sip телефон, то на оставшиеся sccp телефоны звонок проходит нормально. Вопрос: как подружить этот винегрет ?

Конфигурация:

voice service voip
 ip address trusted list
  ipv4 192.168.0.0 255.255.240.0
  ipv4 192.168.30.0 255.255.255.0
 allow-connections h323 to h323
 allow-connections h323 to sip
 allow-connections sip to h323
 allow-connections sip to sip
 supplementary-service h450.12
 no supplementary-service sip moved-temporarily
 no supplementary-service sip refer
 fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback none
 h323
 sip
  bind control source-interface GigabitEthernet0/1
  bind media source-interface GigabitEthernet0/1
  min-se 3600 session-expires 3600
  session refresh
  registrar server expires max 1200 min 300
  nat auto
  conn-reuse
  early-offer forced
  sip-profiles inbound
  no call service stop
!
voice class codec 3
 codec preference 1 g711alaw
 codec preference 2 g711ulaw
 codec preference 3 g729br8
!
------
!
voice translation-rule 112
 rule 1 /1004/ /7099/
 rule 2 /1005/ /7199/
 rule 3 /1006/ /7399/
 rule 4 /1007/ /7299/
 rule 5 /1104/ /6930/
 rule 6 /1105/ /6930/
 rule 7 /1106/ /6930/
 rule 8 /1107/ /6930/
 rule 9 /1087/ /7299/
!

!
voice translation-rule 114
 rule 1 /\(^..........$\)/ /8\1/

voice translation-rule 6930
 rule 1 /^6930/ /1780/
!
!
voice translation-profile International_from_AVAYA
 translate called 110
!
voice translation-profile from_AVAYA
 translate calling 112
!
voice translation-profile to6930
 translate calling 114
 translate called 6930
!
voice translation-profile to7299
 translate calling 114
 translate called 7299
---------------
dial-peer voice 7299 voip
 description -- Incoming to 7299 --
 translation-profile incoming to7299
 incoming called-number 7299
 voice-class codec 3  
 ip qos dscp cs5 media
 no vad
!
dial-peer voice 6930 voip
 description -- Incoming to 6930 --
 translation-profile incoming to6930
 incoming called-number 6930
 voice-class codec 3  
 dtmf-relay rtp-nte
 ip qos dscp cs5 media
 no vad
 ------------------------
 sip-ua 
 credentials username 7099 password 7 хххххххххххххххххххх realm domain.ru
 credentials username 7199 password 7 хххххххххххххххххххх realm domain.ru
 credentials username 7399 password 7 хххххххххххххххххххх realm domain.ru
 credentials username 6047 password 7 хххххххххххххххххххх realm domain.ru
 credentials username 6930 password 7 хххххххххххххххххххх realm domain.ru
 credentials username 7299 password 7 хххххххххххххххххххх realm domain.ru
 no redirection
 registrar ipv4:192.168.0.62 expires 3600
 sip-server ipv4:192.168.0.62
 ------------------

debug ccsip messages

Feb  7 12:49:16.419: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:6930@192.168.0.209:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.62;rport;branch=z9hG4bK167461622886810-AP;ft=192.168.0.62~13c4
Via: SIP/2.0/UDP 127.0.0.2:15060;rport=15060;ibmsid=local.1637930747707_25330028_26281937;branch=z9hG4bK167461622886810
Via: SIP/2.0/UDP 127.0.0.2:15060;rport;ibmsid=local.1637930747707_25330027_26281936;branch=z9hG4bK845132396616759
Record-Route: <sip:avaya-sm1@192.168.0.62;transport=udp;lr;av-asset-uid=3a8c41c2>
Record-Route: <sip:127.0.0.2:15060;transport=udp;ibmsid=local.1637930747707_25330027_26281936;lr;ibmdrr>
Record-Route: <sips:127.0.0.2:15061;ibmsid=local.1637930747707_25330027_26281936;lr;ibmdrr>
Allow-Events: conference,hold,refer,talk
Supported: histinfo,join,replaces,sdp-anat,timer
Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,INFO,PRACK,PUBLISH,UPDATE
Accept: application/sdp
Max-Breadth: 60
Endpoint-View: <sip:7097@domain.ru;gr=2bb6ce2662dd10d9e8f85b3f3a0965b8>;local-tag=199320124;call-id=2_1607818665@192.168.2.247
P-Charging-Vector: icid-value="5be65d30-8814-11ec-9596-00505682b692"
Session-Expires: 1200;refresher=uac
P-Asserted-Identity: "PP0P?QP0P2P:P0 P:P0QQQP8P4P6P5P9 P:-Q 15-1, P&P5Q 68" <sip:7097@domain.ru>
Min-SE: 1200
History-Info: <sip:6930@domain.ru>;index=1
History-Info: "6930" <sip:6930@domain.ru>;index=1.1
Alert-Info: <cid:internal@domain.ru>;avaya-cm-alert-type=internal
Accept-Contact: *;+avaya-cm-line=1
Accept-Language: uk
Contact: "PP0P?QP0P2P:P0 P:P0QQQP8P4P6P5P9 P:-Q 15-1, P&P5Q 68" <sip:7097@192.168.0.70:5063;transport=tls;gsid=5be65d30-8814-11ec-9596-00505682b692;asm=1;epv=%3Csip:7097%40domain.ru%3Bgr%3D2bb6ce2662dd10d9e8f85b3f3a0965b8%3E>;+avaya-cm-keep-mpro=no
User-Agent: Yealink W52P 25.80.14.1 AVAYA-SM-8.0.1.2.801204 Avaya CM/R018x.00.0.822.0 AVAYA-SM-8.0.1.2.801204
From: "PP0P?QP0P2P:P0 P:P0QQQP8P4P6P5P9 P:-Q 15-1, P&P5Q 68" <sip:7097@domain.ru>;tag=5be8cba6881441ec93900505682cf53
To: <sip:6930@domain.ru>
Call-ID: 5be8cbd8881441ec93910505682cf53
Max-Forwards: 56
CSeq: 1 INVITE
Content-Type: application/sdp
Content-Length: 164
Av-Global-Session-ID: 5be65d30-8814-11ec-9596-00505682b692
P-Location: SM;origlocname="Main";origmedialocname="Main";orighomelocname="Main";termlocname="Main";termhomelocname="Main";smaccounting="true"

v=0
o=- 1644238156 1 IN IP4 192.168.0.70
s=-
c=IN IP4 192.168.2.247
b=AS:64
t=0 0
m=audio 12108 RTP/AVP 8 101
a=sendrecv
a=rtpmap:101 telephone-event/8000

Feb  7 12:49:16.427: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 422 Session Timer too small
Via: SIP/2.0/UDP 192.168.0.62;rport;branch=z9hG4bK167461622886810-AP;ft=192.168.0.62~13c4,SIP/2.0/UDP 127.0.0.2:15060;rport=15060;ibmsid=local.1637930747707_25330028_26281937;branch=z9hG4bK167461622886810,SIP/2.0/UDP 127.0.0.2:15060;rport;ibmsid=local.1637930747707_25330027_26281936;branch=z9hG4bK845132396616759
From: "PP0P?QP0P2P:P0 P:P0QQQP8P4P6P5P9 P:-Q 15-1, P&P5Q 68" <sip:7097@domain.ru>;tag=5be8cba6881441ec93900505682cf53
To: <sip:6930@domain.ru>;tag=15EE6F8C-1DDD
Date: Mon, 07 Feb 2022 12:49:16 GMT
Call-ID: 5be8cbd8881441ec93910505682cf53
CSeq: 1 INVITE
Allow-Events: telephone-event
Min-SE:  3600
Server: Cisco-SIPGateway/IOS-15.4.3.M4
Content-Length: 0


Feb  7 12:49:16.431: //-1/317D4ECCA8A7/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:6930@192.168.0.209:5060 SIP/2.0
Call-ID: 5be8cbd8881441ec93910505682cf53
From: "PP0P?QP0P2P:P0 P:P0QQQP8P4P6P5P9 P:-Q 15-1, P&P5Q 68" <sip:7097@domain.ru>;tag=5be8cba6881441ec93900505682cf53
To: <sip:6930@domain.ru>;tag=15EE6F8C-1DDD
Via: SIP/2.0/UDP 192.168.0.62;rport;branch=z9hG4bK167461622886810-AP;ft=192.168.0.62~13c4
Via: SIP/2.0/UDP 127.0.0.2:15060;rport=15060;ibmsid=local.1637930747707_25330028_26281937;branch=z9hG4bK167461622886810
CSeq: 1 ACK
Max-Forwards: 56
Content-Length: 0


Feb  7 12:49:16.519: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:6930@192.168.0.209:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.62;rport;branch=z9hG4bK235785421988044-AP;ft=192.168.0.62~13c4
Via: SIP/2.0/UDP 127.0.0.2:15060;rport=15060;ibmsid=local.1637930747707_25330032_26281941;branch=z9hG4bK235785421988044
Via: SIP/2.0/UDP 127.0.0.2:15060;rport;ibmsid=local.1637930747707_25330031_26281940;branch=z9hG4bK17505808043722
Record-Route: <sip:avaya-sm1@192.168.0.62;transport=udp;lr;av-asset-uid=3a8c41c2>
Record-Route: <sip:127.0.0.2:15060;transport=udp;ibmsid=local.1637930747707_25330031_26281940;lr;ibmdrr>
Record-Route: <sips:127.0.0.2:15061;ibmsid=local.1637930747707_25330031_26281940;lr;ibmdrr>
Allow-Events: conference,hold,refer,talk
Supported: histinfo,join,replaces,sdp-anat,timer
Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,INFO,PRACK,PUBLISH,UPDATE
Accept: application/sdp
Max-Breadth: 60
Endpoint-View: <sip:7097@domain.ru;gr=2bb6ce2662dd10d9e8f85b3f3a0965b8>;local-tag=199320124;call-id=2_1607818665@192.168.2.247
P-Charging-Vector: icid-value="5be65d30-8814-11ec-9596-00505682b692"
Session-Expires: 3600;refresher=uac
P-Asserted-Identity: "PP0P?QP0P2P:P0 P:P0QQQP8P4P6P5P9 P:-Q 15-1, P&P5Q 68" <sip:7097@domain.ru>
Min-SE: 3600
History-Info: <sip:6930@domain.ru>;index=1
History-Info: "6930" <sip:6930@domain.ru>;index=1.1
Alert-Info: <cid:internal@domain.ru>;avaya-cm-alert-type=internal
Accept-Contact: *;+avaya-cm-line=1
Accept-Language: uk
Contact: "PP0P?QP0P2P:P0 P:P0QQQP8P4P6P5P9 P:-Q 15-1, P&P5Q 68" <sip:7097@192.168.0.70:5063;transport=tls;gsid=5be65d30-8814-11ec-9596-00505682b692;asm=1;epv=%3Csip:7097%40domain.ru%3Bgr%3D2bb6ce2662dd10d9e8f85b3f3a0965b8%3E>;+avaya-cm-keep-mpro=no
User-Agent: Yealink W52P 25.80.14.1 AVAYA-SM-8.0.1.2.801204 Avaya CM/R018x.00.0.822.0 AVAYA-SM-8.0.1.2.801204
From: "PP0P?QP0P2P:P0 P:P0QQQP8P4P6P5P9 P:-Q 15-1, P&P5Q 68" <sip:7097@domain.ru>;tag=5be8cba6881441ec93900505682cf53
To: <sip:6930@domain.ru>
Call-ID: 5be8cbd8881441ec93910505682cf53
Max-Forwards: 56
CSeq: 2 INVITE
Content-Type: application/sdp
Content-Length: 164
Av-Global-Session-ID: 5be65d30-8814-11ec-9596-00505682b692
P-Location: SM;origlocname="Main";origmedialocname="Main";orighomelocname="Main";termlocname="Main";termhomelocname="Main";smaccounting="true"

v=0
o=- 1644238156 1 IN IP4 192.168.0.70
s=-
c=IN IP4 192.168.2.247
b=AS:64
t=0 0
m=audio 12108 RTP/AVP 8 101
a=sendrecv
a=rtpmap:101 telephone-event/8000

Feb  7 12:49:16.527: //-1/318BF455A8A8/CCAPI/cc_api_display_ie_subfields:
   cc_api_call_setup_ind_common:
   cisco-username=7097
   ----- ccCallInfo IE subfields -----
   cisco-ani=7097
   cisco-anitype=0
   cisco-aniplan=0
   cisco-anipi=0
   cisco-anisi=0
   dest=6930
   cisco-desttype=0
   cisco-destplan=0
   cisco-rdie=FFFFFFFF
   cisco-rdn=
   cisco-rdntype=0
   cisco-rdnplan=0
   cisco-rdnpi=-1
   cisco-rdnsi=-1
   cisco-redirectreason=-1   fwd_final_type =0
   final_redirectNumber =
   hunt_group_timeout =0

Feb  7 12:49:16.527: //-1/318BF455A8A8/CCAPI/cc_api_call_setup_ind_common:
   Interface=0x41215340, Call Info(
   Calling Number=7097,(Calling Name=)(TON=Unknown, NPI=Unknown, Screening=Not Screened, Presentation=Allowed),
   Called Number=6930(TON=Unknown, NPI=Unknown),
   Calling Translated=FALSE, Subscriber Type Str=Unknown, FinalDestinationFlag=TRUE,
   Incoming Dial-peer=6930, Progress Indication=NULL(0), Calling IE Present=TRUE,
   Source Trkgrp Route Label=, Target Trkgrp Route Label=, CLID Transparent=FALSE), Call Id=8441
Feb  7 12:49:16.527: //-1/318BF455A8A8/CCAPI/ccCheckClipClir:
   In: Calling Number=7097(TON=Unknown, NPI=Unknown, Screening=Not Screened, Presentation=Allowed)
Feb  7 12:49:16.527: //-1/318BF455A8A8/CCAPI/ccCheckClipClir:
   Out: Calling Number=7097(TON=Unknown, NPI=Unknown, Screening=Not Screened, Presentation=Allowed)
Feb  7 12:49:16.527: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:

Feb  7 12:49:16.527: :cc_get_feature_vsa malloc success
Feb  7 12:49:16.527: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:

Feb  7 12:49:16.527:  cc_get_feature_vsa count is 3
Feb  7 12:49:16.527: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:

Feb  7 12:49:16.527: :FEATURE_VSA attributes are: feature_name:0,feature_time:972393480,feature_id:1301
Feb  7 12:49:16.527: //8441/318BF455A8A8/CCAPI/cc_api_call_setup_ind_common:
   Set Up Event Sent;
   Call Info(Calling Number=7097(TON=Unknown, NPI=Unknown, Screening=Not Screened, Presentation=Allowed),
   Called Number=6930(TON=Unknown, NPI=Unknown))
Feb  7 12:49:16.527: //8441/318BF455A8A8/CCAPI/cc_process_call_setup_ind:
   Event=0x415143F0
Feb  7 12:49:16.527: //-1/xxxxxxxxxxxx/CCAPI/cc_setupind_match_search:
   Try with the demoted called number 6930
Feb  7 12:49:16.527: //8441/318BF455A8A8/CCAPI/ccCallSetContext:
   Context=0x2361CB98
Feb  7 12:49:16.527: //8441/318BF455A8A8/CCAPI/cc_process_call_setup_ind:
   >>>>CCAPI handed cid 8441 with tag 6930 to app "_ManagedAppProcess_Default"
Feb  7 12:49:16.535: //8441/318BF455A8A8/CCAPI/ccCallProceeding:
   Progress Indication=NULL(0)
Feb  7 12:49:16.539: //8441/318BF455A8A8/CCAPI/ccCallSetupRequest:
   Destination=, Calling IE Present=TRUE, Mode=0,
   Outgoing Dial-peer=40001, Params=0x23618AF0, Progress Indication=NULL(0)
Feb  7 12:49:16.539: //8441/318BF455A8A8/CCAPI/ccCheckClipClir:
   In: Calling Number=7097(TON=Unknown, NPI=Unknown, Screening=Not Screened, Presentation=Allowed)
Feb  7 12:49:16.539: //8441/318BF455A8A8/CCAPI/ccCheckClipClir:
   Out: Calling Number=7097(TON=Unknown, NPI=Unknown, Screening=Not Screened, Presentation=Allowed)
Feb  7 12:49:16.539: //8441/318BF455A8A8/CCAPI/ccCallSetupRequest:
   Destination Pattern=1107$, Called Number=1107, Digit Strip=FALSE
Feb  7 12:49:16.539: //8441/318BF455A8A8/CCAPI/ccCallSetupRequest:
   Calling Number=7097(TON=Unknown, NPI=Unknown, Screening=Not Screened, Presentation=Allowed),
   Called Number=1107(TON=Unknown, NPI=Unknown),
   Redirect Number=, Display Info=PP0P?QP0P2P:P0 P:P0QQQP8P4P6P5P9 P:-Q 15-1, P&P5Q 68
   Account Number=7097, Final Destination Flag=TRUE,
   Guid=318BF455-874B-11EC-A8A8-EAA50FD78FDC, Outgoing Dial-peer=40001
Feb  7 12:49:16.539: //8441/318BF455A8A8/CCAPI/cc_api_display_ie_subfields:
   ccCallSetupRequest:
   cisco-username=7097
   ----- ccCallInfo IE subfields -----
   cisco-ani=7097
   cisco-anitype=0
   cisco-aniplan=0
   cisco-anipi=0
   cisco-anisi=0
   dest=1107
   cisco-desttype=0
   cisco-destplan=0
   cisco-rdie=FFFFFFFF
   cisco-rdn=
   cisco-rdntype=0
   cisco-rdnplan=0
   cisco-rdnpi=-1
   cisco-rdnsi=-1
   cisco-redirectreason=-1   fwd_final_type =0
   final_redirectNumber =
   hunt_group_timeout =0

Feb  7 12:49:16.539: //8441/318BF455A8A8/CCAPI/ccIFCallSetupRequestPrivate:
   Interface=0x41215340, Interface Type=3, Destination=, Mode=0x0,
   Call Params(Calling Number=7097,(Calling Name=PP0P?QP0P2P:P0 P:P0QQQP8P4P6P5P9 P:-Q 15-1, )(TON=Unknown, NPI=Unknown, Screening=Not Screened, Presentation=Allowed),
   Called Number=1107(TON=Unknown, NPI=Unknown), Calling Translated=FALSE,
   Subscriber Type Str=Unknown, FinalDestinationFlag=TRUE, Outgoing Dial-peer=40001, Call Count On=FALSE,
   Source Trkgrp Route Label=, Target Trkgrp Route Label=, tg_label_flag=0, Application Call Id=)
Feb  7 12:49:16.539: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:

Feb  7 12:49:16.539: :cc_get_feature_vsa malloc success
Feb  7 12:49:16.539: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:

Feb  7 12:49:16.539:  cc_get_feature_vsa count is 4
Feb  7 12:49:16.539: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:

Feb  7 12:49:16.539: :FEATURE_VSA attributes are: feature_name:0,feature_time:972394600,feature_id:1302
Feb  7 12:49:16.539: //8441/318BF455A8A8/CCAPI/cc_api_event_indication:
   Event=101, Call Id=8441
Feb  7 12:49:16.539: //8441/318BF455A8A8/CCAPI/cc_api_event_indication:
   Event Is Sent To Conferenced SPI(s) Directly
Feb  7 12:49:16.543: //8442/318BF455A8A8/CCAPI/ccIFCallSetupRequestPrivate:
   SPI Call Setup Request Is Success; Interface Type=3, FlowMode=1
Feb  7 12:49:16.543: //8442/318BF455A8A8/CCAPI/ccCallSetContext:
   Context=0x23618AA0
Feb  7 12:49:16.543: //8441/318BF455A8A8/CCAPI/ccSaveDialpeerTag:
   Outgoing Dial-peer=40001
Feb  7 12:49:16.543: //8441/318BF455A8A8/CCAPI/ccCallSetupRequest:
   Destination=, Calling IE Present=TRUE, Mode=0,
   Outgoing Dial-peer=20012, Params=0x23617548, Progress Indication=ORIGINATING SIDE IS NON ISDN(3)
Feb  7 12:49:16.543: //8441/318BF455A8A8/CCAPI/ccCheckClipClir:
   In: Calling Number=7097(TON=Unknown, NPI=Unknown, Screening=Not Screened, Presentation=Allowed)
Feb  7 12:49:16.543: //8441/318BF455A8A8/CCAPI/ccCheckClipClir:
   Out: Calling Number=7097(TON=Unknown, NPI=Unknown, Screening=Not Screened, Presentation=Allowed)
Feb  7 12:49:16.543: //8441/318BF455A8A8/CCAPI/ccCallSetupRequest:
   Destination Pattern=1012$, Called Number=1012, Digit Strip=TRUE
Feb  7 12:49:16.543: //8441/318BF455A8A8/CCAPI/ccCallSetupRequest:
   Calling Number=7097(TON=Unknown, NPI=Unknown, Screening=Not Screened, Presentation=Allowed),
   Called Number=1012(TON=Unknown, NPI=Unknown),
   Redirect Number=, Display Info=PP0P?QP0P2P:P0 P:P0QQQP8P4P6P5P9 P:-Q 15-1, P&P5Q 68
   Account Number=7097, Final Destination Flag=TRUE,
   Guid=318F9DDD-874B-11EC-A8AE-EAA50FD78FDC, Outgoing Dial-peer=20012
Feb  7 12:49:16.543: //8441/318BF455A8A8/CCAPI/cc_api_display_ie_subfields:
   ccCallSetupRequest:
   cisco-username=7097
   ----- ccCallInfo IE subfields -----
   cisco-ani=7097
   cisco-anitype=0
   cisco-aniplan=0
   cisco-anipi=0
   cisco-anisi=0
   dest=1012
   cisco-desttype=0
   cisco-destplan=0
   cisco-rdie=FFFFFFFF
   cisco-rdn=
   cisco-rdntype=0
   cisco-rdnplan=0
   cisco-rdnpi=-1
   cisco-rdnsi=-1
   cisco-redirectreason=-1   fwd_final_type =0
   final_redirectNumber =
   hunt_group_timeout =0

Feb  7 12:49:16.543: //8441/318BF455A8A8/CCAPI/ccIFCallSetupRequestPrivate:
   Interface=0x3FD37768, Interface Type=6, Destination=, Mode=0x0,
   Call Params(Calling Number=7097,(Calling Name=PP0P?QP0P2P:P0 P:P0QQQP8P4P6P5P9 P:-Q 15-1, )(TON=Unknown, NPI=Unknown, Screening=Not Screened, Presentation=Allowed),
   Called Number=1012(TON=Unknown, NPI=Unknown), Calling Translated=FALSE,
   Subscriber Type Str=Unknown, FinalDestinationFlag=TRUE, Outgoing Dial-peer=20012, Call Count On=FALSE,
   Source Trkgrp Route Label=, Target Trkgrp Route Label=, tg_label_flag=0, Application Call Id=)
Feb  7 12:49:16.543: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:

Feb  7 12:49:16.543: :cc_get_feature_vsa malloc success
Feb  7 12:49:16.543: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:

Feb  7 12:49:16.543:  cc_get_feature_vsa count is 5
Feb  7 12:49:16.543: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:

Feb  7 12:49:16.543: :FEATURE_VSA attributes are: feature_name:0,feature_time:972392808,feature_id:1303
Feb  7 12:49:16.543: //8443/318BF455A8A8/CCAPI/ccIFCallSetupRequestPrivate:
   SPI Call Setup Request Is Success; Interface Type=6, FlowMode=1
Feb  7 12:49:16.543: //8443/318BF455A8A8/CCAPI/ccCallSetContext:
   Context=0x236174F8
Feb  7 12:49:16.543: //8441/318BF455A8A8/CCAPI/ccSaveDialpeerTag:
   Outgoing Dial-peer=20012
Feb  7 12:49:16.547: //8442/318BF455A8A8/CCAPI/cc_api_call_proceeding:
   Interface=0x41215340, Progress Indication=NULL(0)
Feb  7 12:49:16.551: //8443/318BF455A8A8/CCAPI/cc_api_update_call_info:
   Interface=0x3FD37768, Call Id=0x20FB
Feb  7 12:49:16.555: //8443/318BF455A8A8/CCAPI/cc_api_call_proceeding:
   Interface=0x3FD37768, Progress Indication=NULL(0)
Feb  7 12:49:16.567: //8443/318BF455A8A8/CCAPI/cc_api_call_alert:
   Interface=0x3FD37768, Progress Indication=NULL(0), Signal Indication=SIGNAL RINGBACK(1)
Feb  7 12:49:16.567: //8443/318BF455A8A8/CCAPI/cc_api_call_alert:
   Call Entry(Retry Count=0, Responsed=TRUE)
Feb  7 12:49:16.571: //8441/318BF455A8A8/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.0.62;rport;branch=z9hG4bK235785421988044-AP;ft=192.168.0.62~13c4,SIP/2.0/UDP 127.0.0.2:15060;rport=15060;ibmsid=local.1637930747707_25330032_26281941;branch=z9hG4bK235785421988044,SIP/2.0/UDP 127.0.0.2:15060;rport;ibmsid=local.1637930747707_25330031_26281940;branch=z9hG4bK17505808043722
From: "PP0P?QP0P2P:P0 P:P0QQQP8P4P6P5P9 P:-Q 15-1, P&P5Q 68" <sip:7097@domain.ru>;tag=5be8cba6881441ec93900505682cf53
To: <sip:6930@domain.ru>
Date: Mon, 07 Feb 2022 12:49:16 GMT
Call-ID: 5be8cbd8881441ec93910505682cf53
CSeq: 2 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-15.4.3.M4
Content-Length: 0


Feb  7 12:49:16.571: //8442/318BF455A8A8/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:1107@192.168.2.195:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.209:5060;branch=z9hG4bK93E95F
Remote-Party-ID: "PP0P?QP0P2P:P0 P:P0QQQP8P4P6P5P9 P:-Q 15-1, P&P5Q 68" <sip:7097@192.168.0.209>;party=calling;screen=no;privacy=off
From: "PP0P?QP0P2P:P0 P:P0QQQP8P4P6P5P9 P:-Q 15-1, P&P5Q 68" <sip:7097@192.168.0.62>;tag=15EE7004-FC2
To: <sip:1107@192.168.2.195>
Date: Mon, 07 Feb 2022 12:49:16 GMT
Call-ID: 31903A05-874B11EC-A8B1EAA5-FD78FDC@192.168.0.209
Supported: 100rel,timer,resource-priority,replaces
Min-SE:  3600
Cisco-Guid: 0831255637-2269843948-2829642405-0265785308
User-Agent: Cisco-SIPGateway/IOS-15.4.3.M4
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Timestamp: 1644238156
Contact: <sip:7097@192.168.0.209:5060>
Expires: 180
Allow-Events: telephone-event
Max-Forwards: 55
Alert-Info: <cid:internal@domain.ru>;avaya-cm-alert-type=internal
Session-Expires:  3600;refresher=uac
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 322

v=0
o=CiscoSystemsSIP-GW-UserAgent 3581 8881 IN IP4 192.168.0.209
s=SIP Call
c=IN IP4 192.168.0.209
t=0 0
m=audio 17340 RTP/AVP 8 0 18 101
c=IN IP4 192.168.0.209
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=yes
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20

Feb  7 12:49:16.571: //8441/318BF455A8A8/CCAPI/ccSaveDialpeerTag:
   Outgoing Dial-peer=20012
Feb  7 12:49:16.571: //8443/318BF455A8A8/CCAPI/ccSaveDialpeerTag:
   Incoming Dial-peer=6930
Feb  7 12:49:16.571: //8441/318BF455A8A8/CCAPI/ccCallAlert:
   Progress Indication=NULL(0), Signal Indication=SIGNAL RINGBACK(1)
Feb  7 12:49:16.571: //8441/318BF455A8A8/CCAPI/ccCallAlert:
   Call Entry(Responsed=TRUE, Alert Sent=TRUE)
Feb  7 12:49:16.571: //8443/318BF455A8A8/CCAPI/ccCallFeature:
   Feature Type=25, Call Id=8443
Feb  7 12:49:16.571: //8441/318BF455A8A8/CCAPI/ccCallNotify:
   Data Bitmask=0x7, Call Id=8441
Feb  7 12:49:16.575: //8441/318BF455A8A8/CCAPI/ccCallAlert:
   Progress Indication=NULL(0), Signal Indication=SIGNAL RINGBACK(1)
Feb  7 12:49:16.575: //8441/318BF455A8A8/CCAPI/ccCallAlert:
   Call Entry(Responsed=TRUE, Alert Sent=TRUE)
Feb  7 12:49:16.575: //8441/318BF455A8A8/CCAPI/ccCallNotify:
   Data Bitmask=0x7, Call Id=8441
Feb  7 12:49:16.575: //-1/xxxxxxxxxxxx/CCAPI/cc_setupind_match_search:
   Try with the demoted called number 1012
Feb  7 12:49:16.579: //8441/318BF455A8A8/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 192.168.0.62;rport;branch=z9hG4bK235785421988044-AP;ft=192.168.0.62~13c4,SIP/2.0/UDP 127.0.0.2:15060;rport=15060;ibmsid=local.1637930747707_25330032_26281941;branch=z9hG4bK235785421988044,SIP/2.0/UDP 127.0.0.2:15060;rport;ibmsid=local.1637930747707_25330031_26281940;branch=z9hG4bK17505808043722
From: "PP0P?QP0P2P:P0 P:P0QQQP8P4P6P5P9 P:-Q 15-1, P&P5Q 68" <sip:7097@domain.ru>;tag=5be8cba6881441ec93900505682cf53
To: <sip:6930@domain.ru>;tag=15EE7020-26B5
Date: Mon, 07 Feb 2022 12:49:16 GMT
Call-ID: 5be8cbd8881441ec93910505682cf53
CSeq: 2 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Remote-Party-ID: <sip:1780@192.168.0.209>;party=called;screen=no;privacy=off
Contact: <sip:6930@192.168.0.209:5060>
Record-Route: <sip:avaya-sm1@192.168.0.62;transport=udp;lr;av-asset-uid=3a8c41c2>,<sip:127.0.0.2:15060;transport=udp;ibmsid=local.1637930747707_25330031_26281940;lr;ibmdrr>,<sips:127.0.0.2:15061;ibmsid=local.1637930747707_25330031_26281940;lr;ibmdrr>
Server: Cisco-SIPGateway/IOS-15.4.3.M4
Content-Length: 0


Feb  7 12:49:16.579: //8441/318BF455A8A8/SIP/Msg/ccsipDisplayMsg:
Sent:
UPDATE sip:7097@192.168.0.70:5063;transport=tls;gsid=5be65d30-8814-11ec-9596-00505682b692;asm=1;epv=%3Csip:7097%40domain.ru%3Bgr%3D2bb6ce2662dd10d9e8f85b3f3a0965b8%3E SIP/2.0
Via: SIP/2.0/UDP 192.168.0.209:5060;branch=z9hG4bK93F2259
From: <sip:6930@domain.ru>;tag=15EE7020-26B5
To: "PP0P?QP0P2P:P0 P:P0QQQP8P4P6P5P9 P:-Q 15-1, P&P5Q 68" <sip:7097@domain.ru>;tag=5be8cba6881441ec93900505682cf53
Date: Mon, 07 Feb 2022 12:49:16 GMT
Call-ID: 5be8cbd8881441ec93910505682cf53
User-Agent: Cisco-SIPGateway/IOS-15.4.3.M4
Max-Forwards: 70
Route: <sip:avaya-sm1@192.168.0.62;transport=udp;lr;av-asset-uid=3a8c41c2>,<sip:127.0.0.2:15060;transport=udp;ibmsid=local.1637930747707_25330031_26281940;lr;ibmdrr>,<sips:127.0.0.2:15061;ibmsid=local.1637930747707_25330031_26281940;lr;ibmdrr>
Supported: timer,resource-priority,replaces,sdp-anat
Timestamp: 1644238156
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 UPDATE
Contact: <sip:6930@192.168.0.209:5060>
Min-SE:  3600
Remote-Party-ID: <sip:1012@192.168.0.209>;party=called;screen=no;privacy=off
Content-Length: 0


Feb  7 12:49:16.579: //-1/xxxxxxxxxxxx/CCAPI/cc_setupind_match_search:
   Try with the demoted called number 1780
Feb  7 12:49:16.583: //8441/318BF455A8A8/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 481 Call/Transaction Does Not Exist
Call-ID: 5be8cbd8881441ec93910505682cf53
CSeq: 101 UPDATE
From: <sip:6930@domain.ru>;tag=15EE7020-26B5
To: "PP0P?QP0P2P:P0 P:P0QQQP8P4P6P5P9 P:-Q 15-1, P&P5Q 68" <sip:7097@domain.ru>;tag=5be8cba6881441ec93900505682cf53
Via: SIP/2.0/UDP 192.168.0.209:5060;branch=z9hG4bK93F2259
Content-Length: 0


Feb  7 12:49:16.583: //8441/318BF455A8A8/CCAPI/cc_api_call_disconnected:
   Cause Value=127, Interface=0x41215340, Call Id=8441
Feb  7 12:49:16.583: //8441/318BF455A8A8/CCAPI/cc_api_call_disconnected:
   Call Entry(Responsed=TRUE, Cause Value=127, Retry Count=0)
Feb  7 12:49:16.583: //8443/318BF455A8A8/CCAPI/ccCallDisconnect:
   Cause Value=127, Tag=0x0, Call Entry(Previous Disconnect Cause=0, Disconnect Cause=0)
Feb  7 12:49:16.583: //8443/318BF455A8A8/CCAPI/ccCallDisconnect:
   Cause Value=127, Call Entry(Responsed=TRUE, Cause Value=127)
Feb  7 12:49:16.583: //8443/318BF455A8A8/CCAPI/cc_api_get_transfer_info:
   Transfer Number=NULL
Feb  7 12:49:16.583: //8442/318BF455A8A8/CCAPI/ccCallDisconnect:
   Cause Value=0, Tag=0x0, Call Entry(Previous Disconnect Cause=0, Disconnect Cause=0)
Feb  7 12:49:16.583: //8442/318BF455A8A8/CCAPI/ccCallDisconnect:
   Cause Value=0, Call Entry(Responsed=FALSE, Cause Value=0)
Feb  7 12:49:16.587: //8441/318BF455A8A8/CCAPI/ccCallDisconnect:
   Cause Value=127, Tag=0x0, Call Entry(Previous Disconnect Cause=0, Disconnect Cause=127)
Feb  7 12:49:16.587: //8441/318BF455A8A8/CCAPI/ccCallDisconnect:
   Cause Value=127, Call Entry(Responsed=TRUE, Cause Value=127)
Feb  7 12:49:16.595: //8443/318BF455A8A8/CCAPI/cc_api_call_disconnect_done:
   Disposition=0, Interface=0x3FD37768, Tag=0x0, Call Id=8443,
   Call Entry(Disconnect Cause=127, Voice Class Cause Code=0, Retry Count=0)
Feb  7 12:49:16.595: //8443/318BF455A8A8/CCAPI/cc_api_call_disconnect_done:
   Call Disconnect Event Sent
Feb  7 12:49:16.595: //-1/xxxxxxxxxxxx/CCAPI/cc_free_feature_vsa:

Feb  7 12:49:16.595: :cc_free_feature_vsa freeing 39F58960
Feb  7 12:49:16.595: //-1/xxxxxxxxxxxx/CCAPI/cc_free_feature_vsa:

Feb  7 12:49:16.595:  vsacount in free is 4
Feb  7 12:49:16.595: //8441/318BF455A8A8/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 487 Request Cancelled
Via: SIP/2.0/UDP 192.168.0.62;rport;branch=z9hG4bK235785421988044-AP;ft=192.168.0.62~13c4,SIP/2.0/UDP 127.0.0.2:15060;rport=15060;ibmsid=local.1637930747707_25330032_26281941;branch=z9hG4bK235785421988044,SIP/2.0/UDP 127.0.0.2:15060;rport;ibmsid=local.1637930747707_25330031_26281940;branch=z9hG4bK17505808043722
From: "PP0P?QP0P2P:P0 P:P0QQQP8P4P6P5P9 P:-Q 15-1, P&P5Q 68" <sip:7097@domain.ru>;tag=5be8cba6881441ec93900505682cf53
To: <sip:6930@domain.ru>;tag=15EE7020-26B5
Call-ID: 5be8cbd8881441ec93910505682cf53
CSeq: 2 INVITE
Reason: Q.850;cause=127
Content-Length: 0


Feb  7 12:49:16.599: //8442/318BF455A8A8/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.0.209:5060;branch=z9hG4bK93E95F
From: "PP0P?QP0P2P:P0 P:P0QQQP8P4P6P5P9 P:-Q 15-1, P&P5Q 68" <sip:7097@192.168.0.62>;tag=15EE7004-FC2
To: <sip:1107@192.168.2.195>
Call-ID: 31903A05-874B11EC-A8B1EAA5-FD78FDC@192.168.0.209
Session-ID: 75715ef200105000a00000562b6304ee;remote=00000000000000000000000000000000
Date: Mon, 07 Feb 2022 12:49:19 GMT
CSeq: 101 INVITE
Server: Cisco-CP7841/12.7.1
Contact: <sip:A170-E0@192.168.2.195:5060;transport=udp>;+u.sip!devicename.ccm.cisco.com="SEP00562B6304EE"
Allow: ACK,BYE,CANCEL,INVITE,NOTIFY,OPTIONS,REFER,REGISTER,UPDATE,SUBSCRIBE,INFO
Supported: replaces,join,sdp-anat,norefersub,resource-priority,extended-refer,X-cisco-callinfo,X-cisco-serviceuri,X-cisco-escapecodes,X-cisco-service-control,X-cisco-srtp-fallback,X-cisco-monrec,X-cisco-config,X-cisco-sis-7.0.0,X-cisco-xsi-8.5.1
Allow-Events: kpml,dialog
Content-Length: 0
Recv-Info: conference
Recv-Info: x-cisco-conference


Feb  7 12:49:16.599: //8442/318BF455A8A8/SIP/Msg/ccsipDisplayMsg:
Sent:
CANCEL sip:1107@192.168.2.195:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.209:5060;branch=z9hG4bK93E95F
From: "PP0P?QP0P2P:P0 P:P0QQQP8P4P6P5P9 P:-Q 15-1, P&P5Q 68" <sip:7097@192.168.0.62>;tag=15EE7004-FC2
To: <sip:1107@192.168.2.195>
Date: Mon, 07 Feb 2022 12:49:16 GMT
Call-ID: 31903A05-874B11EC-A8B1EAA5-FD78FDC@192.168.0.209
CSeq: 101 CANCEL
Max-Forwards: 70
Timestamp: 1644238156
Reason: Q.850;cause=0
Content-Length: 0


Feb  7 12:49:16.603: //8441/318BF455A8A8/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:6930@192.168.0.209:5060 SIP/2.0
Call-ID: 5be8cbd8881441ec93910505682cf53
From: "PP0P?QP0P2P:P0 P:P0QQQP8P4P6P5P9 P:-Q 15-1, P&P5Q 68" <sip:7097@domain.ru>;tag=5be8cba6881441ec93900505682cf53
To: <sip:6930@domain.ru>;tag=15EE7020-26B5
Via: SIP/2.0/UDP 192.168.0.62;rport;branch=z9hG4bK235785421988044-AP;ft=192.168.0.62~13c4
Via: SIP/2.0/UDP 127.0.0.2:15060;rport=15060;ibmsid=local.1637930747707_25330032_26281941;branch=z9hG4bK235785421988044
CSeq: 2 ACK
Max-Forwards: 56
Content-Length: 0


Feb  7 12:49:16.603: //8441/318BF455A8A8/CCAPI/cc_api_call_disconnect_done:
   Disposition=0, Interface=0x41215340, Tag=0x0, Call Id=8441,
   Call Entry(Disconnect Cause=127, Voice Class Cause Code=0, Retry Count=0)
Feb  7 12:49:16.603: //8441/318BF455A8A8/CCAPI/cc_api_call_disconnect_done:
   Call Disconnect Event Sent
Feb  7 12:49:16.603: //-1/xxxxxxxxxxxx/CCAPI/cc_free_feature_vsa:

Feb  7 12:49:16.603: :cc_free_feature_vsa freeing 39F58C00
Feb  7 12:49:16.603: //-1/xxxxxxxxxxxx/CCAPI/cc_free_feature_vsa:

Feb  7 12:49:16.603:  vsacount in free is 3
Feb  7 12:49:16.687: //8442/318BF455A8A8/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.0.209:5060;branch=z9hG4bK93E95F
From: "PP0P?QP0P2P:P0 P:P0QQQP8P4P6P5P9 P:-Q 15-1, P&P5Q 68" <sip:7097@192.168.0.62>;tag=15EE7004-FC2
To: <sip:1107@192.168.2.195>;tag=00562b6304ee13a213c8db57-0e11c170
Call-ID: 31903A05-874B11EC-A8B1EAA5-FD78FDC@192.168.0.209
Session-ID: 75715ef200105000a00000562b6304ee;remote=00000000000000000000000000000000
Date: Mon, 07 Feb 2022 12:49:19 GMT
CSeq: 101 CANCEL
Server: Cisco-CP7841/12.7.1
Content-Length: 0


Feb  7 12:49:16.687: //8442/318BF455A8A8/CCAPI/cc_api_call_disconnect_done:
   $uTTYPuTTYPuTTYPuTTYPuTTYPuTTYPuTTYPuTTYPuTTYPuTTYPuTTYPuTTYPuTTY
Volgograd#$uTTYPuTTYPuTTYPuTTYPuTTYPuTTYPuTTYPuTTYPuTTYPuTTYPuTTYPuTTYPuTTYDisposition=0, Interface=0x41215340, Tag=0x0, Call Id=8442,
   Call Entry(Disconnect Cause=0, Voice Class Cause Code=0, Retry Count=0)
Feb  7 12:49:16.687: //8442/318BF455A8A8/CCAPI/cc_api_call_disconnect_done:
   Call Disconnect Event Sent
Feb  7 12:49:16.687: //-1/xxxxxxxxxxxx/CCAPI/cc_free_feature_vsa:

Feb  7 12:49:16.687: :cc_free_feature_vsa freeing 39F59060
Feb  7 12:49:16.687: //-1/xxxxxxxxxxxx/CCAPI/cc_free_feature_vsa:

Feb  7 12:49:16.687:  vsacount in free is 2
Feb  7 12:49:17.435: //8442/318BF455A8A8/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 487 Request Cancelled
Via: SIP/2.0/UDP 192.168.0.209:5060;branch=z9hG4bK93E95F
From: "PP0P?QP0P2P:P0 P:P0QQQP8P4P6P5P9 P:-Q 15-1, P&P5Q 68" <sip:7097@192.168.0.62>;tag=15EE7004-FC2
To: <sip:1107@192.168.2.195>;tag=00562b6304ee13a213c8db57-0e11c170
Call-ID: 31903A05-874B11EC-A8B1EAA5-FD78FDC@192.168.0.209
Session-ID: 75715ef200105000a00000562b6304ee;remote=00000000000000000000000000000000
Date: Mon, 07 Feb 2022 12:49:19 GMT
CSeq: 101 INVITE
Server: Cisco-CP7841/12.7.1
Contact: <sip:A170-E0@192.168.2.195:5060;transport=udp>;+u.sip!devicename.ccm.cisco.com="SEP00562B6304EE"
Allow: ACK,BYE,CANCEL,INVITE,NOTIFY,OPTIONS,REFER,REGISTER,UPDATE,SUBSCRIBE,INFO
Remote-Party-ID: "1007" <sip:1007@192.168.0.209>;party=called;id-type=subscriber;privacy=off;screen=yes
Allow-Events: kpml,dialog
Content-Length: 0


Feb  7 12:49:17.455: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
ACK sip:1107@192.168.2.195:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.209:5060;branch=z9hG4bK93E95F
From: "PP0P?QP0P2P:P0 P:P0QQQP8P4P6P5P9 P:-Q 15-1, P&P5Q 68" <sip:7097@192.168.0.62>;tag=15EE7004-FC2
To: <sip:1107@192.168.2.195>;tag=00562b6304ee13a213c8db57-0e11c170
Date: Mon, 07 Feb 2022 12:49:16 GMT
Call-ID: 31903A05-874B11EC-A8B1EAA5-FD78FDC@192.168.0.209
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: telephone-event
Content-Length: 0

Share this post

Link to post

Share on other sites

SUrov_IBM

Posted February 8, 2022

Uvaxut, здравствуйте.

Как предположение – когда номер [A] 7097 вызывает групповой номер [Б] 6930, от Avaya по SIP сигнализации поступает дополнительная информация в виде «имени вызывающего абонента». В момент прохождения по hunt-group, CISCO "спотыкается" об это «имя абонента».

Попробуйте добавить запрет передачи «имени вызывающего абонента»:

dial-peer voice 6930 voip

clid strip name

Share this post

Link to post

Share on other sites

SUrov_IBM

Posted February 8, 2022

Как вариант, можно попробовать отзеркалировать на коммутаторе Ethernet порт SIP телефона с номером 1107, чтобы через Wireshark посмотреть трассировки вызовов.

При вызове через hunt-group, понять вызов дошёл до телефона с номером 1107 или "оборвался" на группе. Если дошёл до телефона с номером 1107 и "отбился" телефоном, а не группой, сравнить с трассировкой при успешном вызове телефона напрямую (при матчинге через номер 7299) .

Share this post

Link to post

Share on other sites

uvaxut

Posted February 9, 2022

@SUrov_IBM ,

приложил debug ccsip messages. При матчинге 6930 на 1107 звонок проходит, при матчинге на voice hunt-group c пилотом 1780 происходит кратковременный (даже не полноценный) звонок на групповых телефонах и отбой, а на трубе звонящего (7097) пишет занято.

7299.txt 1780.txt

Share this post

Link to post

Share on other sites

SUrov_IBM

Posted February 9, 2022

В 09.02.2022 в 09:12, uvaxut сказал:

при матчинге на voice hunt-group c пилотом 1780 происходит кратковременный (даже не полноценный) звонок на групповых телефонах и отбой

Можете попробовать создать отдельную hunt-group с другим выделенным пилотом, например 178x и входящим групповым номером, например 693x? Поместить в неё только один SIP ТА 1107, без sccp телефонов. Произвести вызов через новую hunt-group, чтобы понять, вызов с применением только сигнализации SIP, с прохождением по hunt-group, но без участия без sccp телефона проходит - [A] 7097 ->[Б] 693x {hunt-group 178x} -> SIP ТА 1107 нормально?

Share this post

Link to post

Share on other sites

uvaxut

Posted February 9, 2022

On 2/9/2022 at 10:52 AM, SUrov_IBM said:

Можете попробовать создать отдельную hunt-group с другим выделенным пилотом, например 178x и входящим групповым номером, например 693x? Поместить в неё только один SIP ТА 1107

voice hunt-group можно с минимум 2 телефонами, поэтому я вставил второй только софтовый sip (номер 1087, который не включен). Групповой номер тот же 6930, просто в нем поменял list

Звонок проходит отлично

Feb  9 08:00:49.806: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:6930@192.168.0.209:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.62;rport;branch=z9hG4bK897573563753952-AP;ft=192.168.0.62~13c4
Via: SIP/2.0/UDP 127.0.0.2:15060;rport=15060;ibmsid=local.1637930747707_26036149_27029926;branch=z9hG4bK897573563753952
Via: SIP/2.0/UDP 127.0.0.2:15060;rport;ibmsid=local.1637930747707_26036148_27029925;branch=z9hG4bK91554003545660
Record-Route: <sip:avaya-sm1@192.168.0.62;transport=udp;lr;av-asset-uid=3a8c41c2>
Record-Route: <sip:127.0.0.2:15060;transport=udp;ibmsid=local.1637930747707_26036148_27029925;lr;ibmdrr>
Record-Route: <sips:127.0.0.2:15061;ibmsid=local.1637930747707_26036148_27029925;lr;ibmdrr>
Allow-Events: conference,hold,refer,talk
Supported: histinfo,join,replaces,sdp-anat,timer
Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,INFO,PRACK,PUBLISH,UPDATE
Accept: application/sdp
Max-Breadth: 60
Endpoint-View: <sip:7097@domain.ru;gr=2bb6ce2662dd10d9e8f85b3f3a0965b8>;local-tag=1519555758;call-id=2_1765923911@192.168.2.247
P-Charging-Vector: icid-value="652a5340-897e-11ec-9596-00505682b692"
Session-Expires: 1200;refresher=uac
P-Asserted-Identity: "PP0P?QP0P2P:P0 P:P0QQQP8P4P6P5P9 P:-Q 15-1, P&P5Q 68" <sip:7097@domain.ru>
Min-SE: 1200
History-Info: <sip:6930@domain.ru>;index=1
History-Info: "6930" <sip:6930@domain.ru>;index=1.1
Alert-Info: <cid:internal@domain.ru>;avaya-cm-alert-type=internal
Accept-Contact: *;+avaya-cm-line=1
Accept-Language: uk
Contact: "PP0P?QP0P2P:P0 P:P0QQQP8P4P6P5P9 P:-Q 15-1, P&P5Q 68" <sip:7097@192.168.0.70:5063;transport=tls;gsid=652a5340-897e-11ec-9596-00505682b692;asm=1;epv=%3Csip:7097%40domain.ru%3Bgr%3D2bb6ce2662dd10d9e8f85b3f3a0965b8%3E>;+avaya-cm-keep-mpro=no
User-Agent: Yealink W52P 25.80.14.1 AVAYA-SM-8.0.1.2.801204 Avaya CM/R018x.00.0.822.0 AVAYA-SM-8.0.1.2.801204
From: "PP0P?QP0P2P:P0 P:P0QQQP8P4P6P5P9 P:-Q 15-1, P&P5Q 68" <sip:7097@domain.ru>;tag=652c992897e41eca0400505682cf53
To: <sip:6930@domain.ru>
Call-ID: 652c9ba897e41eca0410505682cf53
Max-Forwards: 56
CSeq: 1 INVITE
Content-Type: application/sdp
Content-Length: 164
Av-Global-Session-ID: 652a5340-897e-11ec-9596-00505682b692
P-Location: SM;origlocname="Main";origmedialocname="Main";orighomelocname="Main";termlocname="Main";termhomelocname="Main";smaccounting="true"

v=0
o=- 1644393649 1 IN IP4 192.168.0.70
s=-
c=IN IP4 192.168.2.247
b=AS:64
t=0 0
m=audio 12540 RTP/AVP 8 101
a=sendrecv
a=rtpmap:101 telephone-event/8000

Feb  9 08:00:49.814: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 422 Session Timer too small
Via: SIP/2.0/UDP 192.168.0.62;rport;branch=z9hG4bK897573563753952-AP;ft=192.168.0.62~13c4,SIP/2.0/UDP 127.0.0.2:15060;rport=15060;ibmsid=local.1637930747707_26036149_27029926;branch=z9hG4bK897573563753952,SIP/2.0/UDP 127.0.0.2:15060;rport;ibmsid=local.1637930747707_26036148_27029925;branch=z9hG4bK91554003545660
From: "PP0P?QP0P2P:P0 P:P0QQQP8P4P6P5P9 P:-Q 15-1, P&P5Q 68" <sip:7097@domain.ru>;tag=652c992897e41eca0400505682cf53
To: <sip:6930@domain.ru>;tag=1F331
2B8-90D
Date: Wed, 09 Feb 2022 08:00:49 GMT
Call-ID: 652c9ba897e41eca0410505682cf53
CSeq: 1 INVITE
Allow-Events: telephone-event
Min-SE:  3600
Server: Cisco-SIPGateway/IOS-15.4.3.M4
Content-Length: 0


Feb  9 08:00:49.826: //-1/3AC53B72B8BB/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:6930@192.168.0.209:5060 SIP/2.0
Call-ID: 652c9ba897e41eca0410505682cf53
From: "PP0P?QP0P2P:P0 P:P0QQQP8P4P6P5P9 P:-Q 15-1, P&P5Q 68" <sip:7097@domain.ru>;tag=652c992897e41eca0400505682cf53
To: <sip:6930@domain.ru>;tag=1F3312B8-90D
Via: SIP/2.0/UDP 192.168.0.62;rport;branch=z9hG4bK897573563753952-AP;ft=192.168.0.62~13c4
Via: SIP/2.0/UDP 127.0.0.2:15060;rport=15060;ibmsid=local.1637930747707_26036149_27029926;branch=z9hG4bK897573563753952
CSeq: 1 ACK
Max-Forwards: 56
Content-Length: 0


Feb  9 08:00:49.914: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:6930@192.168.0.209:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.62;rport;branch=z9hG4bK934779816164154-AP;ft=192.168.0.62~13c4
Via: SIP/2.0/UDP 127.0.0.2:15060;rport=15060;ibmsid=local.1637930747707_26036153_27029930;branch=z9hG4bK934779816164154
Via: SIP/2.0/UDP 127.0.0.2:15060;rport;ibmsid=local.1637930747707_26036152_27029929;branch=z9hG4bK480477790579343
Record-Route: <sip:avaya-sm1@192.168.0.62;transport=udp;lr;av-asset-uid=3a8c41c2>
Record-Route: <sip:127.0.0.2:15060;transport=udp;ibmsid=local.1637930747707_26036152_27029929;lr;ibmdrr>
Record-Route: <sips:127.0.0.2:15061;ibmsid=local.1637930747707_26036152_27029929;lr;ibmdrr>
Allow-Events: conference,hold,refer,talk
Supported: histinfo,join,replaces,sdp-anat,timer
Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,INFO,PRACK,PUBLISH,UPDATE
Accept: application/sdp
Max-Breadth: 60
Endpoint-View: <sip:7097@domain.ru;gr=2bb6ce2662dd10d9e8f85b3f3a0965b8>;local-tag=1519555758;call-id=2_1765923911@192.168.2.247
P-Charging-Vector: icid-value="652a5340-897e-11ec-9596-00505682b692"
Session-Expires: 3600;refresher=uac
P-Asserted-Identity: "PP0P?QP0P2P:P0 P:P0QQQP8P4P6P5P9 P:-Q 15-1, P&P5Q 68" <sip:7097@domain.ru>
Min-SE: 3600
History-Info: <sip:6930@domain.ru>;index=1
History-Info: "6930" <sip:6930@domain.ru>;index=1.1
Alert-Info: <cid:internal@domain.ru>;avaya-cm-alert-type=internal
Accept-Contact: *;+avaya-cm-line=1
Accept-Language: uk
Contact: "PP0P?QP0P2P:P0 P:P0QQQP8P4P6P5P9 P:-Q 15-1, P&P5Q 68" <sip:7097@192.168.0.70:5063;transport=tls;gsid=652a5340-897e-11ec-9596-00505682b692;asm=1;epv=%3Csip:7097%40domain.ru%3Bgr%3D2bb6ce2662dd10d9e8f85b3f3a0965b8%3E>;+avaya-cm-keep-mpro=no
User-Agent: Yealink W52P 25.80.14.1 AVAYA-SM-8.0.1.2.801204 Avaya CM/R018x.00.0.822.0 AVAYA-SM-8.0.1.2.801204
From: "PP0P?QP0P2P:P0 P:P0QQQP8P4P6P5P9 P:-Q 15-1, P&P5Q 68" <sip:7097@domain.ru>;tag=652c992897e41eca0400505682cf53
To: <sip:6930@domain.ru>
Call-ID: 652c9ba897e41eca0410505682cf53
Max-Forwards: 56
CSeq: 2 INVITE
Content-Type: application/sdp
Content-Length: 164
Av-Global-Session-ID: 652a5340-897e-11ec-9596-00505682b692
P-Location: SM;origlocname="Main";origmedialocname="Main";orighomelocname="Main";termlocname="Main";termhomelocname="Main";smaccounting="true"

v=0
o=- 1644393649 1 IN IP4 192.168.0.70
s=-
c=IN IP4 192.168.2.247
b=AS:64
t=0 0
m=audio 12540 RTP/AVP 8 101
a=sendrecv
a=rtpmap:101 telephone-event/8000

Feb  9 08:00:49.942: //11883/3AD519E3B8BC/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.0.62;rport;branch=z9hG4bK934779816164154-AP;ft=192.168.0.62~13c4,SIP/2.0/UDP 127.0.0.2:15060;rport=15060;ibmsid=local.1637930747707_26036153_27029930;branch=z9hG4bK934779816164154,SIP/2.0/UDP 127.0.0.2:15060;rport;ibmsid=local.1637930747707_26036152_27029929;branch=z9hG4bK480477790579343
From: "PP0P?QP0P2P:P0 P:P0QQQP8P4P6P5P9 P:-Q 15-1, P&P5Q 68" <sip:7097@domain.ru>;tag=652c992897e41eca0400505682cf53
To: <sip:6930@domain.ru>
Date: Wed, 09 Feb 2022 08:00:49 GMT
Call-ID: 652c9ba897e41eca0410505682cf53
CSeq: 2 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-15.4.3.M4
Content-Length: 0


Feb  9 08:00:49.942: //11884/3AD519E3B8BC/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:1107@192.168.2.195:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.209:5060;branch=z9hG4bKD16545
Remote-Party-ID: "PP0P?QP0P2P:P0 P:P0QQQP8P4P6P5P9 P:-Q 15-1, P&P5Q 68" <sip:7097@192.168.0.209>;party=calling;screen=no;privacy=off
From: "PP0P?QP0P2P:P0 P:P0QQQP8P4P6P5P9 P:-Q 15-1, P&P5Q 68" <sip:7097@192.168.0.62>;tag=1F331330-DC0
To: <sip:1107@192.168.2.195>
Date: Wed, 09 Feb 2022 08:00:49 GMT
Call-ID: 3AD826AB-88B511EC-B8C2EAA5-FD78FDC@192.168.0.209
Supported: 100rel,timer,resource-priority,replaces
Min-SE:  3600
Cisco-Guid: 0987044323-2293567980-3099388581-0265785308
User-Agent: Cisco-SIPGateway/IOS-15.4.3.M4
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Timestamp: 1644393649
Contact: <sip:7097@192.168.0.209:5060>
Expires: 180
Allow-Events: telephone-event
Max-Forwards: 55
Alert-Info: <cid:internal@domain.ru>;avaya-cm-alert-type=internal
Session-Expires:  3600;refresher=uac
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 322

v=0
o=CiscoSystemsSIP-GW-UserAgent 5485 2299 IN IP4 192.168.0.209
s=SIP Call
c=IN IP4 192.168.0.209
t=0 0
m=audio 17792 RTP/AVP 8 0 18 101
c=IN IP4 192.168.0.209
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=yes
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20

Feb  9 08:00:49.958: //11884/3AD519E3B8BC/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.0.209:5060;branch=z9hG4bKD16545
From: "PP0P?QP0P2P:P0 P:P0QQQP8P4P6P5P9 P:-Q 15-1, P&P5Q 68" <sip:7097@192.168.0.62>;tag=1F331330-DC0
To: <sip:1107@192.168.2.195>
Call-ID: 3AD826AB-88B511EC-B8C2EAA5-FD78FDC@192.168.0.209
Session-ID: 66f9104400105000a00000562b6304ee;remote=00000000000000000000000000000000
Date: Wed, 09 Feb 2022 08:00:55 GMT
CSeq: 101 INVITE
Server: Cisco-CP7841/12.7.1
Contact: <sip:A170-E0@192.168.2.195:5060;transport=udp>;+u.sip!devicename.ccm.cisco.com="SEP00562B6304EE"
Allow: ACK,BYE,CANCEL,INVITE,NOTIFY,OPTIONS,REFER,REGISTER,UPDATE,SUBSCRIBE,INFO
Supported: replaces,join,sdp-anat,norefersub,resource-priority,extended-refer,X-cisco-callinfo,X-cisco-serviceuri,X-cisco-escapecodes,X-cisco-service-control,X-cisco-srtp-fallback,X-cisco-monrec,X-cisco-config,X-cisco-sis-7.0.0,X-cisco-xsi-8.5.1
Allow-Events: kpml,dialog
Content-Length: 0
Recv-Info: conference
Recv-Info: x-cisco-conference


Feb  9 08:00:50.082: //11884/3AD519E3B8BC/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 192.168.0.209:5060;branch=z9hG4bKD16545
From: "PP0P?QP0P2P:P0 P:P0QQQP8P4P6P5P9 P:-Q 15-1, P&P5Q 68" <sip:7097@192.168.0.62>;tag=1F331330-DC0
To: <sip:1107@192.168.2.195>;tag=00562b6304ee1eac15fae255-041a4a7f
Call-ID: 3AD826AB-88B511EC-B8C2EAA5-FD78FDC@192.168.0.209
Session-ID: 66f9104400105000a00000562b6304ee;remote=00000000000000000000000000000000
Date: Wed, 09 Feb 2022 08:00:55 GMT
CSeq: 101 INVITE
Server: Cisco-CP7841/12.7.1
Contact: <sip:A170-FB5@192.168.2.195:5060;transport=udp>;+u.sip!devicename.ccm.cisco.com="SEP00562B6304EE"
Allow: ACK,BYE,CANCEL,INVITE,NOTIFY,OPTIONS,REFER,REGISTER,UPDATE,SUBSCRIBE,INFO
Remote-Party-ID: "1107" <sip:1107@192.168.0.209>;party=called;id-type=subscriber;privacy=off;screen=yes
Supported: replaces,join,sdp-anat,norefersub,resource-priority,extended-refer,X-cisco-callinfo,X-cisco-serviceuri,X-cisco-escapecodes,X-cisco-service-control,X-cisco-srtp-fallback,X-cisco-monrec,X-cisco-config,X-cisco-sis-7.0.0,X-cisco-xsi-8.5.1
Allow-Events: kpml,dialog
Content-Length: 0


Feb  9 08:00:50.086: //11883/3AD519E3B8BC/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 192.168.0.62;rport;branch=z9hG4bK934779816164154-AP;ft=192.168.0.62~13c4,SIP/2.0/UDP 127.0.0.2:15060;rport=15060;ibmsid=local.1637930747707_26036153_27029930;branch=z9hG4bK934779816164154,SIP/2.0/UDP 127.0.0.2:15060;rport;ibmsid=local.1637930747707_26036152_27029929;branch=z9hG4bK480477790579343
From: "PP0P?QP0P2P:P0 P:P0QQQP8P4P6P5P9 P:-Q 15-1, P&P5Q 68" <sip:7097@domain.ru>;tag=652c992897e41eca0400505682cf53
To: <sip:6930@domain.ru>;tag=1F3313C8-2096
Date:
 Wed, 09 Feb 2022 08:00:49 GMT
Call-ID: 652c9ba897e41eca0410505682cf53
CSeq: 2 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Remote-Party-ID: "1107" <sip:1107@192.168.0.209>;party=called;screen=yes;privacy=off
Contact: <sip:6930@192.168.0.209:5060>
Record-Route: <sip:avaya-sm1@192.168.0.62;transport=udp;lr;av-asset-uid=3a8c41c2>,<sip:127.0.0.2:15060;transport=udp;ibmsid=local.1637930747707_26036152_27029929;lr;ibmdrr>,<sips:127.0.0.2:15061;ibmsid=local.1637930747707_26036152_27029929;lr;ibmdrr>
Server: Cisco-SIPGateway/IOS-15.4.3.M4
Content-Length: 0



Feb  9 08:00:52.498: //11883/3AD519E3B8BC/SIP/Msg/ccsipDisplayMsg:
Received:
CANCEL sip:6930@192.168.0.209:5060 SIP/2.0
Record-Route: <sip:avaya-sm1@192.168.0.62;transport=udp;lr;av-asset-uid=3a8c41c2>
CSeq: 2 CANCEL
Call-ID: 652c9ba897e41eca0410505682cf53
From: "PP0P?QP0P2P:P0 P:P0QQQP8P4P6P5P9 P:-Q 15-1, P&P5Q 68" <sip:7097@domain.ru>;tag=652c992897e41eca0400505682cf53
To: <sip:6930@domain.ru>
Via: SIP/2.0/UDP 192.168.0.62;rport;branch=z9hG4bK934779816164154-AP;ft=192.168.0.62~13c4
Via: SIP/2.0/UDP 127.0.0.2:15060;rport=15060;ibmsid=local.1637930747707_26036153_27029930;branch=z9hG4bK934779816164154
Via: SIP/2.0/UDP 127.0.0.2:15060;rport;ibmsid=local.1637930747707_26036152_27029929;branch=z9hG4bK480477790579343
Max-Forwards: 69
Content-Length: 0


Feb  9 08:00:52.502: //11883/3AD519E3B8BC/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.0.62;rport;branch=z9hG4bK934779816164154-AP;ft=192.168.0.62~13c4,SIP/2.0/UDP 127.0.0.2:15060;rport=15060;ibmsid=local.1637930747707_26036153_27029930;branch=z9hG4bK934779816164154,SIP/2.0/UDP 127.0.0.2:15060;rport;ibmsid=local.1637930747707_26036152_27029929;branch=z9hG4bK480477790579343
From: "PP0P?QP0P2P:P0 P:P0QQQP8P4P6P5P9 P:-Q 15-1, P&P5Q 68" <sip:7097@domain.ru>;tag=652c992897e41eca0400505682cf53
To: <sip:6930@domain.ru>
Date: Wed, 09 Feb 2022 08:00:52 GMT
Call-ID: 652c9ba897e41eca0410505682cf53
CSeq: 2 CANCEL
Content-Length: 0


Feb  9 08:00:52.506: //11884/3AD519E3B8BC/SIP/Msg/ccsipDisplayMsg:
Sent:
CANCEL sip:1107@192.168.2.195:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.209:5060;branch=z9hG4bKD16545
From: "PP0P?QP0P2P:P0 P:P0QQQP8P4P6P5P9 P:-Q 15-1, P&P5Q 68" <sip:7097@192.168.0.62>;tag=1F331330-DC0
To: <sip:1107@192.168.2.195>
Date: Wed, 09 Feb 2022 08:00:49 GMT
Call-ID: 3AD826AB-88B511EC-B8C2EAA5-FD78FDC@192.168.0.209
CSeq: 101 CANCEL
Max-Forwards: 70
Timestamp: 1644393652
Reason: Q.850;cause=16
Content-Length: 0


Feb  9 08:00:52.506: //11883/3AD519E3B8BC/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 487 Request Cancelled
Via: SIP/2.0/UDP 192.168.0.62;rport;branch=z9hG4bK934779816164154-AP;ft=192.168.0.62~13c4,SIP/2.0/UDP 127.0.0.2:15060;rport=15060;ibmsid=local.1637930747707_26036153_27029930;branch=z9hG4bK934779816164154,SIP/2.0/UDP 127.0.0.2:15060;rport;ibmsid=local.1637930747707_26036152_27029929;branch=z9hG4bK480477790579343
From: "PP0P?QP0P2P:P0 P:P0QQQP8P4P6P5P9 P:-Q 15-1, P&P5Q 68" <sip:7097@domain.ru>;tag=652c992897e41eca0400505682cf53
To: <sip:6930@domain.ru>;tag=1F3313C8-2096
Date: Wed, 09 Feb 2022 08:00:52 GMT
Call-ID: 652c9ba897e41eca0410505682cf53
CSeq: 2 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-15.4.3.M4
Reason: Q.850;cause=16
Session-Expires:  3600
Content-Length: 0


Feb  9 08:00:52.506: //11883/3AD519E3B8BC/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:6930@192.168.0.209:5060 SIP/2.0
Call-ID: 652c9ba897e41eca0410505682cf53
From: "PP0P?QP0P2P:P0 P:P0QQQP8P4P6P5P9 P:-Q 15-1, P&P5Q 68" <sip:7097@domain.ru>;tag=652c992897e41eca0400505682cf53
To: <sip:6930@domain.ru>;tag=1F3313C8-2096
Via: SIP/2.0/UDP 192.168.0.62;rport;branch=z9hG4bK934779816164154-AP;ft=192.168.0.62~13c4
Via: SIP/2.0/UDP 127.0.0.2:15060;rport=15060;ibmsid=local.1637930747707_26036153_27029930;branch=z9hG4bK934779816164154
CSeq: 2 ACK
Max-Forwards: 56
Content-Length: 0


Feb  9 08:00:52.518: //11884/3AD519E3B8BC/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.0.209:5060;branch=z9hG4bKD16545
From: "PP0P?QP0P2P:P0 P:P0QQQP8P4P6P5P9 P:-Q 15-1, P&P5Q 68" <sip:7097@192.168.0.62>;tag=1F331330-DC0
To: <sip:1107@192.168.2.195>;tag=00562b6304ee1eac15fae255-041a4a7f
Call-ID: 3AD826AB-88B511EC-B8C2EAA5-FD78FDC@192.168.0.209
Session-ID: 66f9104400105000a00000562b6304ee;remote=00000000000000000000000000000000
Date: Wed, 09 Feb 2022 08:00:57 GMT
CSeq: 101 CANCEL
Server: Cisco-CP7841/12.7.1
Content-Length: 0


Feb  9 08:00:52.522: //11884/3AD519E3B8BC/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 487 Request Cancelled
Via: SIP/2.0/UDP 192.168.0.209:5060;branch=z9hG4bKD16545
From: "PP0P?QP0P2P:P0 P:P0QQQP8P4P6P5P9 P:-Q 15-1, P&P5Q 68" <sip:7097@192.168.0.62>;tag=1F331330-DC0
To: <sip:1107@192.168.2.195>;tag=00562b6304ee1eac15fae255-041a4a7f
Call-ID: 3AD826AB-88B511EC-B8C2EAA5-FD78FDC@192.168.0.209
Session-ID: 66f9104400105000a00000562b6304ee;remote=00000000000000000000000000000000
Date: Wed, 09 Feb 2022 08:00:57 GMT
CSeq: 101 INVITE
Server: Cisco-CP7841/12.7.1
Contact: <sip:A170-FB5@192.168.2.195:5060;transport=udp>;+u.sip!devicename.ccm.cisco.com="SEP00562B6304EE"
Allow: ACK,BYE,CANCEL,INVITE,NOTIFY,OPTIONS,REFER,REGISTER,UPDATE,SUBSCRIBE,INFO
Remote-Party-ID: "1107" <sip:1107@192.168.0.209>;party=called;id-type=subscriber;privacy=off;screen=yes
Allow-Events: kpml,dialog
Content-Length: 0


Feb  9 08:00:52.526: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:

ACK sip:1107@192.168.2.195:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.209:5060;branch=z9hG4bKD16545
From: "PP0P?QP0P2P:P0 P:P0QQQP8P4P6P5P9 P:-Q 15-1, P&P5Q 68" <sip:7097@192.168.0.62>;tag=1F331330-DC0
To: <sip:1107@192.168.2.195>;tag=00562b6304ee1eac15fae255-041a4a7f
Date: Wed, 09 Feb 2022 08:00:49 GMT
Call-ID: 3AD826AB-88B511EC-B8C2EAA5-FD78FDC@192.168.0.209
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: telephone-event
Content-Length: 0

Share this post

Link to post

Share on other sites

uvaxut

Posted February 9, 2022

Проблема решена. На вызывающих телефонах не было включено 100rel

Share this post

Link to post

Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

× Pasted as rich text. Paste as plain text instead

Only 75 emoji are allowed.

× Your link has been automatically embedded. Display as a link instead

× Your previous content has been restored. Clear editor

× You cannot paste images directly. Upload or insert images from URL.

Insert image from URL

Followers 0

Go to topic listing Телефония: классическая, IP-телефония (VoIP), NGN сети

Sign In

Share this post

Link to post

Share on other sites

Share this post

Link to post

Share on other sites

Share this post

Link to post

Share on other sites

Share this post

Link to post

Share on other sites

Share this post

Link to post

Share on other sites

Share this post

Link to post

Share on other sites

Share this post

Link to post

Share on other sites

Join the conversation