Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
cancel

Collaboration, Voice and Video Blogs

12 Views
0 Comments

hello,

we have a sip trunk from ITSP 

the authentication is only by IP

we have a cucm >>>> cube >>>>>ITSP

the cube configuration as following:


version 15.4
service timestamps debug datetime msec
service timestamps log datetime msec
service password-encryption
no service password-recovery
!
hostname XXXXXX
!
boot-start-marker
boot-end-marker
!
aqm-register-fnf
!
enable secret 5 XXXXXXXX
enable password 7 XXXXXXXX
!
no aaa new-model
!
!
!
!
!
!
ip vrf vrf1
!
!
!
!
ip domain name XXXXXX.local
ip cef
no ipv6 cef
!
!
multilink bundle-name authenticated
!
!
!
!
!
voice-card 0
!
!
!
voice service voip
ip address trusted list
ipv4 10.123.101.162
ipv4 192.168.1.10
ipv4 192.168.1.21
ipv4 10.198.13.86
ipv4 10.198.13.85
allow-connections h323 to h323
allow-connections h323 to sip
allow-connections sip to h323
allow-connections sip to sip
supplementary-service media-renegotiate
sip
min-se 86400 session-expires 86400
header-passing
registrar server
early-offer forced
midcall-signaling passthru
!
!
voice class uri 200 sip
host ipv4:10.123.101.162
voice class codec 1
codec preference 2 clear-channel
codec preference 3 g711alaw
codec preference 4 g711ulaw
codec preference 5 g723r53
codec preference 6 g723r63
codec preference 7 g726r16
codec preference 8 g726r24
codec preference 9 g726r32
codec preference 10 g728
codec preference 11 g729br8
codec preference 12 g729r8
codec preference 13 ilbc
!
!
!
!
voice translation-rule 1
rule 1 /0212022..../ /8999999/
rule 2 /212022..../ /8999999/
rule 3 /2022..../ /8999999/
!
voice translation-rule 2
rule 1 /^9/ //
!
!
voice translation-profile 100
translate called 1
!
voice translation-profile OUT
translate called 2
!
!
license udi pid C3900-SPE150/K9 sn XXXXXX
license boot module c3900 technology-package uck9
!
!
archive
log config
logging enable
username xxx
!
redundancy
!
!
!
!
interface GigabitEthernet0/0.1
encapsulation dot1Q 11
ip address 192.168.1.10 255.255.255.0
ip nat inside
ip virtual-reassembly in


interface GigabitEthernet0/2.2
encapsulation dot1Q 900
ip address 10.198.13.86 255.255.255.252
ip virtual-reassembly in

ip forward-protocol nd

mgcp behavior rsip-range tgcp-only
mgcp behavior comedia-role none
mgcp behavior comedia-check-media-src disable
mgcp behavior comedia-sdp-force disable
!
mgcp profile default
!
!
!
!
dial-peer voice 2 voip
description cube to cucm
destination-pattern [1,8].T
session protocol sipv2
session target ipv4:192.168.1.21
voice-class codec 1
dtmf-relay h245-alphanumeric rtp-nte
!
dial-peer voice 200 voip
description pstn to cube
translation-profile incoming 100
session protocol sipv2
session transport udp
voice-class codec 1
dtmf-relay rtp-nte sip-kpml sip-notify
fax protocol pass-through g711alaw
no vad
!
dial-peer voice 250 voip
description cube tp pstn
translation-profile outgoing OUT
destination-pattern 9T
session protocol sipv2
session target ipv4:10.123.101.162
session transport udp
voice-class codec 1
voice-class sip options-keepalive up-interval 100 down-interval 50 retry 6
dtmf-relay rtp-nte sip-kpml sip-notify
fax protocol pass-through g711alaw
no vad
!
dial-peer voice 321 voip
translation-profile incoming 100
translation-profile outgoing 100
destination-pattern 2022....
session protocol sipv2
session target ipv4:192.168.1.21
no vad
!
!
sip-ua
retry invite 3
retry response 3
retry bye 3
retry cancel 3
retry rel1xx 3
timers connect 100
timers connection aging 30
registrar ipv4:10.123.101.162 expires 3600
host-registrar
!
!
!
gatekeeper
shutdown
!
!
telephony-service
max-ephones 20
max-dn 20
ip source-address 192.168.1.10 port 2000
max-conferences 8 gain -6
transfer-system full-consult
create cnf-files version-stamp Jan 01 2002 00:00:00
!
!
ephone-dn 20
number 20220000
!
!
ephone 1
device-security-mode none
mac-address D8CB.8AFC.0B70
button 2:20

 

 

when I call from the phone registered on cme to cucm its OK but trying ITSP no chance

 

debug ccsip message output is as follows:

 

 

*Apr 22 15:34:27.388: //1719/000000000000/SIP/Msg/ccsipDisplayMsg:
Sent:
OPTIONS sip:10.123.101.162:5060 SIP/2.0

Via: SIP/2.0/UDP 10.198.13.86:5060;branch=z9hG4bK6511DA

From: <sip:10.198.13.86>;tag=1B0E9A74-79F

To: <sip:10.123.101.162>

Date: Sun, 22 Apr 2018 15:34:27 GMT

Call-ID: 79EF5266-457911E8-89B38B84-9C99BF5E@10.198.13.86

User-Agent: Cisco-SIPGateway/IOS-15.4.1.T3

Max-Forwards: 70

CSeq: 101 OPTIONS

Contact: <sip:10.198.13.86:5060>

Content-Length: 0

 


*Apr 22 15:34:32.748: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:10.123.101.162:5060 SIP/2.0

Via: SIP/2.0/UDP 10.198.13.86:5060;branch=z9hG4bK6521FAA

From: <sip:20220000@10.123.101.162>;tag=1B0EAF64-2246

To: <sip:20220000@10.123.101.162>

Date: Sun, 22 Apr 2018 15:34:32 GMT

Call-ID: 9FF20FD3-456A11E8-88BF8B84-9C99BF5E

User-Agent: Cisco-SIPGateway/IOS-15.4.1.T3

Max-Forwards: 70

Timestamp: 1524411272

CSeq: 34 REGISTER

Contact: <sip:20220000@10.198.13.86:5060>

Expires: 3600

Supported: path

Content-Length: 0

 


*Apr 22 15:34:33.248: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:10.123.101.162:5060 SIP/2.0

Via: SIP/2.0/UDP 10.198.13.86:5060;branch=z9hG4bK6521FAA

From: <sip:20220000@10.123.101.162>;tag=1B0EAF64-2246

To: <sip:20220000@10.123.101.162>

Date: Sun, 22 Apr 2018 15:34:33 GMT

Call-ID: 9FF20FD3-456A11E8-88BF8B84-9C99BF5E

User-Agent: Cisco-SIPGateway/IOS-15.4.1.T3

Max-Forwards: 70

Timestamp: 1524411273

CSeq: 34 REGISTER

Contact: <sip:20220000@10.198.13.86:5060>

Expires: 3600

Supported: path

Content-Length: 0

 


*Apr 22 15:34:34.248: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:10.123.101.162:5060 SIP/2.0

Via: SIP/2.0/UDP 10.198.13.86:5060;branch=z9hG4bK6521FAA

From: <sip:20220000@10.123.101.162>;tag=1B0EAF64-2246

To: <sip:20220000@10.123.101.162>

Date: Sun, 22 Apr 2018 15:34:34 GMT

Call-ID: 9FF20FD3-456A11E8-88BF8B84-9C99BF5E

User-Agent: Cisco-SIPGateway/IOS-15.4.1.T3

Max-Forwards: 70

Timestamp: 1524411274

CSeq: 34 REGISTER

Contact: <sip:20220000@10.198.13.86:5060>

Expires: 3600

Supported: path

Content-Length: 0

 


*Apr 22 15:34:36.248: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:10.123.101.162:5060 SIP/2.0

Via: SIP/2.0/UDP 10.198.13.86:5060;branch=z9hG4bK6521FAA

From: <sip:20220000@10.123.101.162>;tag=1B0EAF64-2246

To: <sip:20220000@10.123.101.162>

Date: Sun, 22 Apr 2018 15:34:36 GMT

Call-ID: 9FF20FD3-456A11E8-88BF8B84-9C99BF5E

User-Agent: Cisco-SIPGateway/IOS-15.4.1.T3

Max-Forwards: 70

Timestamp: 1524411276

CSeq: 34 REGISTER

Contact: <sip:20220000@10.198.13.86:5060>

Expires: 3600

Supported: path

Content-Length: 0

 


ZH-TCI-Floor3-3945-R1#
ZH-TCI-Floor3-3945-R1#
ZH-TCI-Floor3-3945-R1#
ZH-TCI-Floor3-3945-R1#
ZH-TCI-Floor3-3945-R1#
ZH-TCI-Floor3-3945-R1#
ZH-TCI-Floor3-3945-R1#
ZH-TCI-Floor3-3945-R1#
ZH-TCI-Floor3-3945-R1#
ZH-TCI-Floor3-3945-R1#
ZH-TCI-Floor3-3945-R1#
ZH-TCI-Floor3-3945-R1#
*Apr 22 15:34:40.248: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:10.123.101.162:5060 SIP/2.0

Via: SIP/2.0/UDP 10.198.13.86:5060;branch=z9hG4bK6521FAA

From: <sip:20220000@10.123.101.162>;tag=1B0EAF64-2246

To: <sip:20220000@10.123.101.162>

Date: Sun, 22 Apr 2018 15:34:40 GMT

Call-ID: 9FF20FD3-456A11E8-88BF8B84-9C99BF5E

User-Agent: Cisco-SIPGateway/IOS-15.4.1.T3

Max-Forwards: 70

Timestamp: 1524411280

CSeq: 34 REGISTER

Contact: <sip:20220000@10.198.13.86:5060>

Expires: 3600

Supported: path

Content-Length: 0

 


*Apr 22 15:34:41.112: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:20225858@10.198.13.86:5060;user=phone SIP/2.0

Via: SIP/2.0/UDP 10.123.101.162:5060;branch=z9hG4bKvp4ubervx4xxwuppr44ubpttt;Role=3;Hpt=8ec8_16

Record-Route: <sip:10.123.101.162:5060;transport=udp;lr;Hpt=8ec8_16;CxtId=4;TRC=ffffffff-ffffffff;X-HwB2bUaCookie=300>

Call-ID: isbcv222jmm6ejm8n4ssteenqz6nne6qq10t@SoftX3000

From: <sip:9128574118@10.198.13.86;user=phone>;tag=vtn11qv2-CC-31

To: <sip:20225858@10.198.13.86;user=phone>

CSeq: 1 INVITE

Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,REGISTER,INFO,PRACK,SUBSCRIBE,NOTIFY,UPDATE,MESSAGE,REFER

Contact: <sip:9128574118@10.123.101.162:5060;transport=udp;Hpt=8ec8_16;CxtId=4;TRC=ffffffff-ffffffff>

Max-Forwards: 69

Supported: 100rel,timer

User-Agent: Huawei SoftX3000 V300R010

Session-Expires: 300

Min-SE: 90

Content-Length: 271

Content-Type: application/sdp

 

v=0

o=- 16260238 16260238 IN IP4 10.123.101.162

s=SBC call

c=IN IP4 10.123.101.162

t=0 0

m=audio 11334 RTP/AVP 8 3 97 96

a=rtpmap:8 PCMA/8000

a=rtpmap:3 GSM/8000

a=rtpmap:97 telephone-event/8000

a=rtpmap:96 RED/8000

a=ptime:20

a=fmtp:97 0-15

a=fmtp:96 97/97


*Apr 22 15:34:41.112: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
Calling Number=20225858, Called Number=20225858, Peer Info Type=DIALPEER_INFO_SPEECH
*Apr 22 15:34:41.112: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=20225858
*Apr 22 15:34:41.112: //-1/xxxxxxxxxxxx/DPM/dpMatchCore:
Dial String=20225858, Expanded String=20225858, Calling Number=20225858T
Timeout=TRUE, Is Incoming=FALSE, Peer Info Type=DIALPEER_INFO_SPEECH
*Apr 22 15:34:41.112: //-1/xxxxxxxxxxxx/DPM/MatchNextPeer:
Result=Success(0); Outgoing Dial-peer=321 Is Matched
*Apr 22 15:34:41.112: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
Result=Success(0) after DP_MATCH_DEST
*Apr 22 15:34:41.112: //-1/xxxxxxxxxxxx/DPM/dpMatchSafModulePlugin:
dialstring=20225858, saf_enabled=1, saf_dndb_lookup=1, dp_result=0
*Apr 22 15:34:41.112: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersMoreArg:
Result=SUCCESS(0)
List of Matched Outgoing Dial-peer(s):
1: Dial-peer Tag=321
*Apr 22 15:34:41.112: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Calling Number=9128574118, Called Number=, Voice-Interface=0x0,
Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,
Peer Info Type=DIALPEER_INFO_SPEECH
*Apr 22 15:34:41.112: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Match Rule=DP_MATCH_ANSWER; Calling Number=9128574118
*Apr 22 15:34:41.112: //-1/xxxxxxxxxxxx/DPM/dpMatchPeertype:
Is Incoming=TRUE, Number Expansion=FALSE
*Apr 22 15:34:41.112: //-1/xxxxxxxxxxxx/DPM/dpMatchCore:
Dial String=, Expanded String=, Calling Number=9128574118T
Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_SPEECH
*Apr 22 15:34:41.112: //-1/xxxxxxxxxxxx/DPM/dpMatchCore:
Result=-1
*Apr 22 15:34:41.112: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Match Rule=DP_MATCH_ORIGINATE; Calling Number=9128574118
*Apr 22 15:34:41.112: //-1/xxxxxxxxxxxx/DPM/dpMatchPeertype:
Is Incoming=TRUE, Number Expansion=FALSE
*Apr 22 15:34:41.112: //-1/xxxxxxxxxxxx/DPM/dpMatchCore:
Dial String=, Expanded String=, Calling Number=9128574118T
Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_SPEECH
*Apr 22 15:34:41.112: //-1/xxxxxxxxxxxx/DPM/MatchNextPeer:
Result=Success(0); Incoming Dial-peer=250 Is Matched
*Apr 22 15:34:41.112: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Result=Success(0) after DP_MATCH_ORIGINATE; Incoming Dial-peer=250
*Apr 22 15:34:41.112: //-1/xxxxxxxxxxxx/DPM/dpMatchSafModulePlugin:
dialstring=NULL, saf_enabled=0, saf_dndb_lookup=0, dp_result=0
*Apr 22 15:34:41.112: //-1/821D70AB89B4/DPM/dpAssociateIncomingPeerCore:
Calling Number=9128574118, Called Number=20225858, Voice-Interface=0x0,
Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,
Peer Info Type=DIALPEER_INFO_SPEECH
*Apr 22 15:34:41.112: //-1/821D70AB89B4/DPM/dpAssociateIncomingPeerCore:
Match Rule=DP_MATCH_VIA_URI; URI=sip:10.123.101.162:5060
*Apr 22 15:34:41.112: //-1/821D70AB89B4/DPM/dpMatchPeertype:
Is Incoming=TRUE, Number Expansion=FALSE
*Apr 22 15:34:41.112: //-1/821D70AB89B4/DPM/dpMatchCore:
Dial String=, Expanded String=, Calling Number=
Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_SPEECH
*Apr 22 15:34:41.112: //-1/821D70AB89B4/DPM/dpMatchCore:
Result=-1
*Apr 22 15:34:41.112: //-1/821D70AB89B4/DPM/dpAssociateIncomingPeerCore:
Match Rule=DP_MATCH_REQUEST_URI; URI=sip:20225858@10.198.13.86:5060;user=phone
*Apr 22 15:34:41.112: //-1/821D70AB89B4/DPM/dpMatchPeertype:
Is Incoming=TRUE, Number Expansion=FALSE
*Apr 22 15:34:41.112: //-1/821D70AB89B4/DPM/dpMatchCore:
Dial String=, Expanded String=, Calling Number=
Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_SPEECH
*Apr 22 15:34:41.112: //-1/821D70AB89B4/DPM/dpMatchCore:
Result=-1
*Apr 22 15:34:41.112: //-1/821D70AB89B4/DPM/dpAssociateIncomingPeerCore:
Match Rule=DP_MATCH_TO_URI; URI=sip:20225858@10.198.13.86;user=phone
*Apr 22 15:34:41.112: //-1/821D70AB89B4/DPM/dpMatchPeertype:
Is Incoming=TRUE, Number Expansion=FALSE
*Apr 22 15:34:41.112: //-1/821D70AB89B4/DPM/dpMatchCore:
Dial String=, Expanded String=, Calling Number=
Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_SPEECH
*Apr 22 15:34:41.112: //-1/821D70AB89B4/DPM/dpMatchCore:
Result=-1
*Apr 22 15:34:41.112: //-1/821D70AB89B4/DPM/dpAssociateIncomingPeerCore:
Match Rule=DP_MATCH_FROM_URI; URI=sip:9128574118@10.198.13.86;user=phone
*Apr 22 15:34:41.112: //-1/821D70AB89B4/DPM/dpMatchPeertype:
Is Incoming=TRUE, Number Expansion=FALSE
*Apr 22 15:34:41.112: //-1/821D70AB89B4/DPM/dpMatchCore:
Dial String=, Expanded String=, Calling Number=
Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_SPEECH
*Apr 22 15:34:41.112: //-1/821D70AB89B4/DPM/dpMatchCore:
Result=-1
*Apr 22 15:34:41.112: //-1/821D70AB89B4/DPM/dpAssociateIncomingPeerCore:
Match Rule=DP_MATCH_INCOMING_DNIS; Called Number=20225858
*Apr 22 15:34:41.112: //-1/821D70AB89B4/DPM/dpMatchPeertype:
Is Incoming=TRUE, Number Expansion=FALSE
*Apr 22 15:34:41.112: //-1/821D70AB89B4/DPM/dpMatchCore:
Dial String=20225858, Expanded String=20225858, Calling Number=
Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_SPEECH
*Apr 22 15:34:41.112: //-1/821D70AB89B4/DPM/dpMatchCore:
Result=-1
*Apr 22 15:34:41.112: //-1/821D70AB89B4/DPM/dpAssociateIncomingPeerCore:
Match Rule=DP_MATCH_ANSWER; Calling Number=9128574118
*Apr 22 15:34:41.112: //-1/821D70AB89B4/DPM/dpMatchPeertype:
Is Incoming=TRUE, Number Expansion=FALSE
*Apr 22 15:34:41.112: //-1/821D70AB89B4/DPM/dpMatchCore:
Dial String=, Expanded String=, Calling Number=9128574118T
Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_SPEECH
*Apr 22 15:34:41.112: //-1/821D70AB89B4/DPM/dpMatchCore:
Result=-1
*Apr 22 15:34:41.112: //-1/821D70AB89B4/DPM/dpAssociateIncomingPeerCore:
Match Rule=DP_MATCH_ORIGINATE; Calling Number=9128574118
*Apr 22 15:34:41.112: //-1/821D70AB89B4/DPM/dpMatchPeertype:
Is Incoming=TRUE, Number Expansion=FALSE
*Apr 22 15:34:41.112: //-1/821D70AB89B4/DPM/dpMatchCore:
Dial String=, Expanded String=, Calling Number=9128574118T
Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_SPEECH
*Apr 22 15:34:41.112: //-1/821D70AB89B4/DPM/MatchNextPeer:
Result=Success(0); Incoming Dial-peer=250 Is Matched
*Apr 22 15:34:41.112: //-1/821D70AB89B4/DPM/dpAssociateIncomingPeerCore:
Result=Success(0) after DP_MATCH_ORIGINATE; Incoming Dial-peer=250
*Apr 22 15:34:41.112: //-1/821D70AB89B4/DPM/dpMatchSafModulePlugin:
dialstring=NULL, saf_enabled=0, saf_dndb_lookup=0, dp_result=0
*Apr 22 15:34:41.112: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 422 Session Timer too small

Via: SIP/2.0/UDP 10.123.101.162:5060;branch=z9hG4bKvp4ubervx4xxwuppr44ubpttt;Role=3;Hpt=8ec8_16

From: <sip:9128574118@10.198.13.86;user=phone>;tag=vtn11qv2-CC-31

To: <sip:20225858@10.198.13.86;user=phone>;tag=1B0ED010-20A6

Date: Sun, 22 Apr 2018 15:34:41 GMT

Call-ID: isbcv222jmm6ejm8n4ssteenqz6nne6qq10t@SoftX3000

CSeq: 1 INVITE

Allow-Events: kpml, telephone-event

Min-SE: 86400

Server: Cisco-SIPGateway/IOS-15.4.1.T3

Content-Length: 0

 


*Apr 22 15:34:41.212: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 422 Session Timer too small

Via: SIP/2.0/UDP 10.123.101.162:5060;branch=z9hG4bKvp4ubervx4xxwuppr44ubpttt;Role=3;Hpt=8ec8_16

From: <sip:9128574118@10.198.13.86;user=phone>;tag=vtn11qv2-CC-31

To: <sip:20225858@10.198.13.86;user=phone>;tag=1B0ED010-20A6

Call-ID: isbcv222jmm6ejm8n4ssteenqz6nne6qq10t@SoftX3000

Min-SE: 86400

CSeq: 1 INVITE

Content-Length: 0

 


*Apr 22 15:34:41.412: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 422 Session Timer too small

Via: SIP/2.0/UDP 10.123.101.162:5060;branch=z9hG4bKvp4ubervx4xxwuppr44ubpttt;Role=3;Hpt=8ec8_16

From: <sip:9128574118@10.198.13.86;user=phone>;tag=vtn11qv2-CC-31

To: <sip:20225858@10.198.13.86;user=phone>;tag=1B0ED010-20A6

Call-ID: isbcv222jmm6ejm8n4ssteenqz6nne6qq10t@SoftX3000

Min-SE: 86400

CSeq: 1 INVITE

Content-Length: 0

 


*Apr 22 15:34:41.608: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:20225858@10.198.13.86:5060;user=phone SIP/2.0

Via: SIP/2.0/UDP 10.123.101.162:5060;branch=z9hG4bKvp4ubervx4xxwuppr44ubpttt;Role=3;Hpt=8ec8_16

Record-Route: <sip:10.123.101.162:5060;transport=udp;lr;Hpt=8ec8_16;CxtId=4;TRC=ffffffff-ffffffff;X-HwB2bUaCookie=300>

Call-ID: isbcv222jmm6ejm8n4ssteenqz6nne6qq10t@SoftX3000

From: <sip:9128574118@10.198.13.86;user=phone>;tag=vtn11qv2-CC-31

To: <sip:20225858@10.198.13.86;user=phone>

CSeq: 1 INVITE

Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,REGISTER,INFO,PRACK,SUBSCRIBE,NOTIFY,UPDATE,MESSAGE,REFER

Contact: <sip:9128574118@10.123.101.162:5060;transport=udp;Hpt=8ec8_16;CxtId=4;TRC=ffffffff-ffffffff>

Max-Forwards: 69

Supported: 100rel,timer

User-Agent: Huawei SoftX3000 V300R010

Session-Expires: 300

Min-SE: 90

Content-Length: 271

Content-Type: application/sdp

 

v=0

o=- 16260238 16260238 IN IP4 10.123.101.162

s=SBC call

c=IN IP4 10.123.101.162

t=0 0

m=audio 11334 RTP/AVP 8 3 97 96

a=rtpmap:8 PCMA/8000

a=rtpmap:3 GSM/8000

a=rtpmap:97 telephone-event/8000

a=rtpmap:96 RED/8000

a=ptime:20

a=fmtp:97 0-15

a=fmtp:96 97/97


*Apr 22 15:34:41.608: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:

SIP/2.0 422 Session Timer too small

Via: SIP/2.0/UDP 10.123.101.162:5060;branch=z9hG4bKvp4ubervx4xxwuppr44ubpttt;Role=3;Hpt=8ec8_16

From: <sip:9128574118@10.198.13.86;user=phone>;tag=vtn11qv2-CC-31

To: <sip:20225858@10.198.13.86;user=phone>;tag=1B0ED010-20A6

Date: Sun, 22 Apr 2018 15:34:41 GMT

Call-ID: isbcv222jmm6ejm8n4ssteenqz6nne6qq10t@SoftX3000

CSeq: 1 INVITE

Allow-Events: kpml, telephone-event

Min-SE: 86400

Server: Cisco-SIPGateway/IOS-15.4.1.T3

Content-Length: 0

 


*Apr 22 15:34:41.812: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 422 Session Timer too small

Via: SIP/2.0/UDP 10.123.101.162:5060;branch=z9hG4bKvp4ubervx4xxwuppr44ubpttt;Role=3;Hpt=8ec8_16

From: <sip:9128574118@10.198.13.86;user=phone>;tag=vtn11qv2-CC-31

To: <sip:20225858@10.198.13.86;user=phone>;tag=1B0ED010-20A6

Call-ID: isbcv222jmm6ejm8n4ssteenqz6nne6qq10t@SoftX3000

Min-SE: 86400

CSeq: 1 INVITE

Content-Length: 0

 


*Apr 22 15:34:42.604: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:20225858@10.198.13.86:5060;user=phone SIP/2.0

Via: SIP/2.0/UDP 10.123.101.162:5060;branch=z9hG4bKvp4ubervx4xxwuppr44ubpttt;Role=3;Hpt=8ec8_16

Record-Route: <sip:10.123.101.162:5060;transport=udp;lr;Hpt=8ec8_16;CxtId=4;TRC=ffffffff-ffffffff;X-HwB2bUaCookie=300>

Call-ID: isbcv222jmm6ejm8n4ssteenqz6nne6qq10t@SoftX3000

From: <sip:9128574118@10.198.13.86;user=phone>;tag=vtn11qv2-CC-31

To: <sip:20225858@10.198.13.86;user=phone>

CSeq: 1 INVITE

Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,REGISTER,INFO,PRACK,SUBSCRIBE,NOTIFY,UPDATE,MESSAGE,REFER

Contact: <sip:9128574118@10.123.101.162:5060;transport=udp;Hpt=8ec8_16;CxtId=4;TRC=ffffffff-ffffffff>

Max-Forwards: 69

Supported: 100rel,timer

User-Agent: Huawei SoftX3000 V300R010

Session-Expires: 300

Min-SE: 90

Content-Length: 271

Content-Type: application/sdp

 

v=0

o=- 16260238 16260238 IN IP4 10.123.101.162

s=SBC call

c=IN IP4 10.123.101.162

t=0 0

m=audio 11334 RTP/AVP 8 3 97 96

a=rtpmap:8 PCMA/8000

a=rtpmap:3 GSM/8000

a=rtpmap:97 telephone-event/8000

a=rtpmap:96 RED/8000

a=ptime:20

a=fmtp:97 0-15

a=fmtp:96 97/97


*Apr 22 15:34:42.604: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 422 Session Timer too small

Via: SIP/2.0/UDP 10.123.101.162:5060;branch=z9hG4bKvp4ubervx4xxwuppr44ubpttt;Role=3;Hpt=8ec8_16

From: <sip:9128574118@10.198.13.86;user=phone>;tag=vtn11qv2-CC-31

To: <sip:20225858@10.198.13.86;user=phone>;tag=1B0ED010-20A6

Date: Sun, 22 Apr 2018 15:34:42 GMT

Call-ID: isbcv222jmm6ejm8n4ssteenqz6nne6qq10t@SoftX3000

CSeq: 1 INVITE

Allow-Events: kpml, telephone-event

Min-SE: 86400

Server: Cisco-SIPGateway/IOS-15.4.1.T3

Content-Length: 0

 


*Apr 22 15:34:44.248: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:10.123.101.162:5060 SIP/2.0

Via: SIP/2.0/UDP 10.198.13.86:5060;branch=z9hG4bK6521FAA

From: <sip:20220000@10.123.101.162>;tag=1B0EAF64-2246

To: <sip:20220000@10.123.101.162>

Date: Sun, 22 Apr 2018 15:34:44 GMT

Call-ID: 9FF20FD3-456A11E8-88BF8B84-9C99BF5E

User-Agent: Cisco-SIPGateway/IOS-15.4.1.T3

Max-Forwards: 70

Timestamp: 1524411284

CSeq: 34 REGISTER

Contact: <sip:20220000@10.198.13.86:5060>

Expires: 3600

Supported: path

Content-Length: 0

 


*Apr 22 15:34:44.608: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:20225858@10.198.13.86:5060;user=phone SIP/2.0

Via: SIP/2.0/UDP 10.123.101.162:5060;branch=z9hG4bKvp4ubervx4xxwuppr44ubpttt;Role=3;Hpt=8ec8_16

Record-Route: <sip:10.123.101.162:5060;transport=udp;lr;Hpt=8ec8_16;CxtId=4;TRC=ffffffff-ffffffff;X-HwB2bUaCookie=300>

Call-ID: isbcv222jmm6ejm8n4ssteenqz6nne6qq10t@SoftX3000

From: <sip:9128574118@10.198.13.86;user=phone>;tag=vtn11qv2-CC-31

To: <sip:20225858@10.198.13.86;user=phone>

CSeq: 1 INVITE

Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,REGISTER,INFO,PRACK,SUBSCRIBE,NOTIFY,UPDATE,MESSAGE,REFER

Contact: <sip:9128574118@10.123.101.162:5060;transport=udp;Hpt=8ec8_16;CxtId=4;TRC=ffffffff-ffffffff>

Max-Forwards: 69

Supported: 100rel,timer

User-Agent: Huawei SoftX3000 V300R010

Session-Expires: 300

Min-SE: 90

Content-Length: 271

Content-Type: application/sdp

 

v=0

o=- 16260238 16260238 IN IP4 10.123.101.162

s=SBC call

c=IN IP4 10.123.101.162

t=0 0

m=audio 11334 RTP/AVP 8 3 97 96

a=rtpmap:8 PCMA/8000

a=rtpmap:3 GSM/8000

a=rtpmap:97 telephone-event/8000

a=rtpmap:96 RED/8000

a=ptime:20

a=fmtp:97 0-15

a=fmtp:96 97/97


*Apr 22 15:34:44.608: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
Calling Number=20225858, Called Number=20225858, Peer Info Type=DIALPEER_INFO_SPEECH
*Apr 22 15:34:44.608: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=20225858
*Apr 22 15:34:44.608: //-1/xxxxxxxxxxxx/DPM/dpMatchCore:
Dial String=20225858, Expanded String=20225858, Calling Number=20225858T
Timeout=TRUE, Is Incoming=FALSE, Peer Info Type=DIALPEER_INFO_SPEECH
*Apr 22 15:34:44.608: //-1/xxxxxxxxxxxx/DPM/MatchNextPeer:
Result=Success(0); Outgoing Dial-peer=321 Is Matched
*Apr 22 15:34:44.608: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
Result=Success(0) after DP_MATCH_DEST
*Apr 22 15:34:44.608: //-1/xxxxxxxxxxxx/DPM/dpMatchSafModulePlugin:
dialstring=20225858, saf_enabled=1, saf_dndb_lookup=1, dp_result=0
*Apr 22 15:34:44.608: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersMoreArg:
Result=SUCCESS(0)
List of Matched Outgoing Dial-peer(s):
1: Dial-peer Tag=321
*Apr 22 15:34:44.608: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Calling Number=9128574118, Called Number=, Voice-Interface=0x0,
Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,
Peer Info Type=DIALPEER_INFO_SPEECH
*Apr 22 15:34:44.608: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Match Rule=DP_MATCH_ANSWER; Calling Number=9128574118
*Apr 22 15:34:44.608: //-1/xxxxxxxxxxxx/DPM/dpMatchPeertype:
Is Incoming=TRUE, Number Expansion=FALSE
*Apr 22 15:34:44.608: //-1/xxxxxxxxxxxx/DPM/dpMatchCore:
Dial String=, Expanded String=, Calling Number=9128574118T
Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_SPEECH
*Apr 22 15:34:44.608: //-1/xxxxxxxxxxxx/DPM/dpMatchCore:
Result=-1
*Apr 22 15:34:44.608: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Match Rule=DP_MATCH_ORIGINATE; Calling Number=9128574118
*Apr 22 15:34:44.608: //-1/xxxxxxxxxxxx/DPM/dpMatchPeertype:
Is Incoming=TRUE, Number Expansion=FALSE
*Apr 22 15:34:44.608: //-1/xxxxxxxxxxxx/DPM/dpMatchCore:
Dial String=, Expanded String=, Calling Number=9128574118T
Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_SPEECH
*Apr 22 15:34:44.608: //-1/xxxxxxxxxxxx/DPM/MatchNextPeer:
Result=Success(0); Incoming Dial-peer=250 Is Matched
*Apr 22 15:34:44.608: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Result=Success(0) after DP_MATCH_ORIGINATE; Incoming Dial-peer=250
*Apr 22 15:34:44.608: //-1/xxxxxxxxxxxx/DPM/dpMatchSafModulePlugin:
dialstring=NULL, saf_enabled=0, saf_dndb_lookup=0, dp_result=0
*Apr 22 15:34:44.608: //-1/8432E24189B5/DPM/dpAssociateIncomingPeerCore:
Calling Number=9128574118, Called Number=20225858, Voice-Interface=0x0,
Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,
Peer Info Type=DIALPEER_INFO_SPEECH
*Apr 22 15:34:44.608: //-1/8432E24189B5/DPM/dpAssociateIncomingPeerCore:
Match Rule=DP_MATCH_VIA_URI; URI=sip:10.123.101.162:5060
*Apr 22 15:34:44.608: //-1/8432E24189B5/DPM/dpMatchPeertype:
Is Incoming=TRUE, Number Expansion=FALSE
*Apr 22 15:34:44.608: //-1/8432E24189B5/DPM/dpMatchCore:
Dial String=, Expanded String=, Calling Number=
Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_SPEECH
*Apr 22 15:34:44.608: //-1/8432E24189B5/DPM/dpMatchCore:
Result=-1
*Apr 22 15:34:44.608: //-1/8432E24189B5/DPM/dpAssociateIncomingPeerCore:
Match Rule=DP_MATCH_REQUEST_URI; URI=sip:20225858@10.198.13.86:5060;user=phone
*Apr 22 15:34:44.608: //-1/8432E24189B5/DPM/dpMatchPeertype:
Is Incoming=TRUE, Number Expansion=FALSE
*Apr 22 15:34:44.608: //-1/8432E24189B5/DPM/dpMatchCore:
Dial String=, Expanded String=, Calling Number=
Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_SPEECH
*Apr 22 15:34:44.608: //-1/8432E24189B5/DPM/dpMatchCore:
Result=-1
*Apr 22 15:34:44.608: //-1/8432E24189B5/DPM/dpAssociateIncomingPeerCore:
Match Rule=DP_MATCH_TO_URI; URI=sip:20225858@10.198.13.86;user=phone
*Apr 22 15:34:44.608: //-1/8432E24189B5/DPM/dpMatchPeertype:
Is Incoming=TRUE, Number Expansion=FALSE
*Apr 22 15:34:44.608: //-1/8432E24189B5/DPM/dpMatchCore:
Dial String=, Expanded String=, Calling Number=
Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_SPEECH
*Apr 22 15:34:44.608: //-1/8432E24189B5/DPM/dpMatchCore:
Result=-1
*Apr 22 15:34:44.608: //-1/8432E24189B5/DPM/dpAssociateIncomingPeerCore:
Match Rule=DP_MATCH_FROM_URI; URI=sip:9128574118@10.198.13.86;user=phone
*Apr 22 15:34:44.608: //-1/8432E24189B5/DPM/dpMatchPeertype:
Is Incoming=TRUE, Number Expansion=FALSE
*Apr 22 15:34:44.608: //-1/8432E24189B5/DPM/dpMatchCore:
Dial String=, Expanded String=, Calling Number=
Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_SPEECH
*Apr 22 15:34:44.608: //-1/8432E24189B5/DPM/dpMatchCore:
Result=-1
*Apr 22 15:34:44.608: //-1/8432E24189B5/DPM/dpAssociateIncomingPeerCore:
Match Rule=DP_MATCH_INCOMING_DNIS; Called Number=20225858
*Apr 22 15:34:44.608: //-1/8432E24189B5/DPM/dpMatchPeertype:
Is Incoming=TRUE, Number Expansion=FALSE
*Apr 22 15:34:44.608: //-1/8432E24189B5/DPM/dpMatchCore:
Dial String=20225858, Expanded String=20225858, Calling Number=
Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_SPEECH
*Apr 22 15:34:44.608: //-1/8432E24189B5/DPM/dpMatchCore:
Result=-1
*Apr 22 15:34:44.608: //-1/8432E24189B5/DPM/dpAssociateIncomingPeerCore:
Match Rule=DP_MATCH_ANSWER; Calling Number=9128574118
*Apr 22 15:34:44.608: //-1/8432E24189B5/DPM/dpMatchPeertype:
Is Incoming=TRUE, Number Expansion=FALSE
*Apr 22 15:34:44.608: //-1/8432E24189B5/DPM/dpMatchCore:
Dial String=, Expanded String=, Calling Number=9128574118T
Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_SPEECH
*Apr 22 15:34:44.608: //-1/8432E24189B5/DPM/dpMatchCore:
Result=-1
*Apr 22 15:34:44.608: //-1/8432E24189B5/DPM/dpAssociateIncomingPeerCore:
Match Rule=DP_MATCH_ORIGINATE; Calling Number=9128574118
*Apr 22 15:34:44.608: //-1/8432E24189B5/DPM/dpMatchPeertype:
Is Incoming=TRUE, Number Expansion=FALSE
*Apr 22 15:34:44.608: //-1/8432E24189B5/DPM/dpMatchCore:
Dial String=, Expanded String=, Calling Number=9128574118T
Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_SPEECH
*Apr 22 15:34:44.608: //-1/8432E24189B5/DPM/MatchNextPeer:
Result=Success(0); Incoming Dial-peer=250 Is Matched
*Apr 22 15:34:44.608: //-1/8432E24189B5/DPM/dpAssociateIncomingPeerCore:
Result=Success(0) after DP_MATCH_ORIGINATE; Incoming Dial-peer=250
*Apr 22 15:34:44.608: //-1/8432E24189B5/DPM/dpMatchSafModulePlugin:
dialstring=NULL, saf_enabled=0, saf_dndb_lookup=0, dp_result=0
*Apr 22 15:34:44.608: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 422 Session Timer too small

Via: SIP/2.0/UDP 10.123.101.162:5060;branch=z9hG4bKvp4ubervx4xxwuppr44ubpttt;Role=3;Hpt=8ec8_16

From: <sip:9128574118@10.198.13.86;user=phone>;tag=vtn11qv2-CC-31

To: <sip:20225858@10.198.13.86;user=phone>;tag=1B0EDDB8-108F

Date: Sun, 22 Apr 2018 15:34:44 GMT

Call-ID: isbcv222jmm6ejm8n4ssteenqz6nne6qq10t@SoftX3000

CSeq: 1 INVITE

Allow-Events: kpml, telephone-event

Min-SE: 86400

Server: Cisco-SIPGateway/IOS-15.4.1.T3

Content-Length: 0

 


*Apr 22 15:34:44.708: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 422 Session Timer too small

Via: SIP/2.0/UDP 10.123.101.162:5060;branch=z9hG4bKvp4ubervx4xxwuppr44ubpttt;Role=3;Hpt=8ec8_16

From: <sip:9128574118@10.198.13.86;user=phone>;tag=vtn11qv2-CC-31

To: <sip:20225858@10.198.13.86;user=phone>;tag=1B0EDDB8-108F

Call-ID: isbcv222jmm6ejm8n4ssteenqz6nne6qq10t@SoftX3000

Min-SE: 86400

CSeq: 1 INVITE

Content-Length: 0

 


*Apr 22 15:34:44.908: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 422 Session Timer too small

Via: SIP/2.0/UDP 10.123.101.162:5060;branch=z9hG4bKvp4ubervx4xxwuppr44ubpttt;Role=3;Hpt=8ec8_16

From: <sip:9128574118@10.198.13.86;user=phone>;tag=vtn11qv2-CC-31

To: <sip:20225858@10.198.13.86;user=phone>;tag=1B0EDDB8-108F

Call-ID: isbcv222jmm6ejm8n4ssteenqz6nne6qq10t@SoftX3000

Min-SE: 86400

CSeq: 1 INVITE

Content-Length: 0

 


*Apr 22 15:34:45.308: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 422 Session Timer too small

Via: SIP/2.0/UDP 10.123.101.162:5060;branch=z9hG4bKvp4ubervx4xxwuppr44ubpttt;Role=3;Hpt=8ec8_16

From: <sip:9128574118@10.198.13.86;user=phone>;tag=vtn11qv2-CC-31

To: <sip:20225858@10.198.13.86;user=phone>;tag=1B0EDDB8-108F

Call-ID: isbcv222jmm6ejm8n4ssteenqz6nne6qq10t@SoftX3000

Min-SE: 86400

CSeq: 1 INVITE

Content-Length: 0

 


*Apr 22 15:34:48.248: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:10.123.101.162:5060 SIP/2.0

Via: SIP/2.0/UDP 10.198.13.86:5060;branch=z9hG4bK6521FAA

From: <sip:20220000@10.123.101.162>;tag=1B0EAF64-2246

To: <sip:20220000@10.123.101.162>

Date: Sun, 22 Apr 2018 15:34:48 GMT

Call-ID: 9FF20FD3-456A11E8-88BF8B84-9C99BF5E

User-Agent: Cisco-SIPGateway/IOS-15.4.1.T3

Max-Forwards: 70

Timestamp: 1524411288

CSeq: 34 REGISTER

Contact: <sip:20220000@10.198.13.86:5060>

Expires: 3600

Supported: path

Content-Length: 0

 


*Apr 22 15:34:48.604: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:20225858@10.198.13.86:5060;user=phone SIP/2.0

Via: SIP/2.0/UDP 10.123.101.162:5060;branch=z9hG4bKvp4ubervx4xxwuppr44ubpttt;Role=3;Hpt=8ec8_16

Record-Route: <sip:10.123.101.162:5060;transport=udp;lr;Hpt=8ec8_16;CxtId=4;TRC=ffffffff-ffffffff;X-HwB2bUaCookie=300>

Call-ID: isbcv222jmm6ejm8n4ssteenqz6nne6qq10t@SoftX3000

From: <sip:9128574118@10.198.13.86;user=phone>;tag=vtn11qv2-CC-31

To: <sip:20225858@10.198.13.86;user=phone>

CSeq: 1 INVITE

Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,REGISTER,INFO,PRACK,SUBSCRIBE,NOTIFY,UPDATE,MESSAGE,REFER

Contact: <sip:9128574118@10.123.101.162:5060;transport=udp;Hpt=8ec8_16;CxtId=4;TRC=ffffffff-ffffffff>

Max-Forwards: 69

Supported: 100rel,timer

User-Agent: Huawei SoftX3000 V300R010

Session-Expires: 300

Min-SE: 90

Content-Length: 271

Content-Type: application/sdp

 

v=0

o=- 16260238 16260238 IN IP4 10.123.101.162

s=SBC call

c=IN IP4 10.123.101.162

t=0 0

m=audio 11334 RTP/AVP 8 3 97 96

a=rtpmap:8 PCMA/8000

a=rtpmap:3 GSM/8000

a=rtpmap:97 telephone-event/8000

a=rtpmap:96 RED/8000

a=ptime:20

a=fmtp:97 0-15

a=fmtp:96 97/97


*Apr 22 15:34:48.604: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
Calling Number=20225858, Called Number=20225858, Peer Info Type=DIALPEER_INFO_SPEECH
*Apr 22 15:34:48.604: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=20225858
*Apr 22 15:34:48.604: //-1/xxxxxxxxxxxx/DPM/dpMatchCore:
Dial String=20225858, Expanded String=20225858, Calling Number=20225858T
Timeout=TRUE, Is Incoming=FALSE, Peer Info Type=DIALPEER_INFO_SPEECH
*Apr 22 15:34:48.604: //-1/xxxxxxxxxxxx/DPM/MatchNextPeer:
Result=Success(0); Outgoing Dial-peer=321 Is Matched
*Apr 22 15:34:48.604: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
Result=Success(0) after DP_MATCH_DEST
*Apr 22 15:34:48.604: //-1/xxxxxxxxxxxx/DPM/dpMatchSafModulePlugin:
dialstring=20225858, saf_enabled=1, saf_dndb_lookup=1, dp_result=0
*Apr 22 15:34:48.604: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersMoreArg:
Result=SUCCESS(0)
List of Matched Outgoing Dial-peer(s):
1: Dial-peer Tag=321
*Apr 22 15:34:48.604: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Calling Number=9128574118, Called Number=, Voice-Interface=0x0,
Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,
Peer Info Type=DIALPEER_INFO_SPEECH
*Apr 22 15:34:48.604: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Match Rule=DP_MATCH_ANSWER; Calling Number=9128574118
*Apr 22 15:34:48.604: //-1/xxxxxxxxxxxx/DPM/dpMatchPeertype:
Is Incoming=TRUE, Number Expansion=FALSE
*Apr 22 15:34:48.604: //-1/xxxxxxxxxxxx/DPM/dpMatchCore:
Dial String=, Expanded String=, Calling Number=9128574118T
Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_SPEECH
*Apr 22 15:34:48.604: //-1/xxxxxxxxxxxx/DPM/dpMatchCore:
Result=-1
*Apr 22 15:34:48.604: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Match Rule=DP_MATCH_ORIGINATE; Calling Number=9128574118
*Apr 22 15:34:48.604: //-1/xxxxxxxxxxxx/DPM/dpMatchPeertype:
Is Incoming=TRUE, Number Expansion=FALSE
*Apr 22 15:34:48.604: //-1/xxxxxxxxxxxx/DPM/dpMatchCore:
Dial String=, Expanded String=, Calling Number=9128574118T
Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_SPEECH
*Apr 22 15:34:48.604: //-1/xxxxxxxxxxxx/DPM/MatchNextPeer:
Result=Success(0); Incoming Dial-peer=250 Is Matched
*Apr 22 15:34:48.604: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Result=Success(0) after DP_MATCH_ORIGINATE; Incoming Dial-peer=250
*Apr 22 15:34:48.604: //-1/xxxxxxxxxxxx/DPM/dpMatchSafModulePlugin:
dialstring=NULL, saf_enabled=0, saf_dndb_lookup=0, dp_result=0
*Apr 22 15:34:48.604: //-1/8694A01989B6/DPM/dpAssociateIncomingPeerCore:
Calling Number=9128574118, Called Number=20225858, Voice-Interface=0x0,
Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,
Peer Info Type=DIALPEER_INFO_SPEECH
*Apr 22 15:34:48.604: //-1/8694A01989B6/DPM/dpAssociateIncomingPeerCore:
Match Rule=DP_MATCH_VIA_URI; URI=sip:10.123.101.162:5060
*Apr 22 15:34:48.604: //-1/8694A01989B6/DPM/dpMatchPeertype:
Is Incoming=TRUE, Number Expansion=FALSE
*Apr 22 15:34:48.604: //-1/8694A01989B6/DPM/dpMatchCore:
Dial String=, Expanded String=, Calling Number=
Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_SPEECH
*Apr 22 15:34:48.604: //-1/8694A01989B6/DPM/dpMatchCore:
Result=-1
*Apr 22 15:34:48.604: //-1/8694A01989B6/DPM/dpAssociateIncomingPeerCore:
Match Rule=DP_MATCH_REQUEST_URI; URI=sip:20225858@10.198.13.86:5060;user=phone
*Apr 22 15:34:48.604: //-1/8694A01989B6/DPM/dpMatchPeertype:
Is Incoming=TRUE, Number Expansion=FALSE
*Apr 22 15:34:48.604: //-1/8694A01989B6/DPM/dpMatchCore:
Dial String=, Expanded String=, Calling Number=
Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_SPEECH
*Apr 22 15:34:48.604: //-1/8694A01989B6/DPM/dpMatchCore:
Result=-1
*Apr 22 15:34:48.604: //-1/8694A01989B6/DPM/dpAssociateIncomingPeerCore:
Match Rule=DP_MATCH_TO_URI; URI=sip:20225858@10.198.13.86;user=phone
*Apr 22 15:34:48.604: //-1/8694A01989B6/DPM/dpMatchPeertype:
Is Incoming=TRUE, Number Expansion=FALSE
*Apr 22 15:34:48.604: //-1/8694A01989B6/DPM/dpMatchCore:
Dial String=, Expanded String=, Calling Number=
Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_SPEECH
*Apr 22 15:34:48.604: //-1/8694A01989B6/DPM/dpMatchCore:
Result=-1
*Apr 22 15:34:48.604: //-1/8694A01989B6/DPM/dpAssociateIncomingPeerCore:
Match Rule=DP_MATCH_FROM_URI; URI=sip:9128574118@10.198.13.86;user=phone
*Apr 22 15:34:48.604: //-1/8694A01989B6/DPM/dpMatchPeertype:
Is Incoming=TRUE, Number Expansion=FALSE
*Apr 22 15:34:48.604: //-1/8694A01989B6/DPM/dpMatchCore:
Dial String=, Expanded String=, Calling Number=
Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_SPEECH
*Apr 22 15:34:48.604: //-1/8694A01989B6/DPM/dpMatchCore:
Result=-1
*Apr 22 15:34:48.604: //-1/8694A01989B6/DPM/dpAssociateIncomingPeerCore:
Match Rule=DP_MATCH_INCOMING_DNIS; Called Number=20225858
*Apr 22 15:34:48.604: //-1/8694A01989B6/DPM/dpMatchPeertype:
Is Incoming=TRUE, Number Expansion=FALSE
*Apr 22 15:34:48.604: //-1/8694A01989B6/DPM/dpMatchCore:
Dial String=20225858, Expanded String=20225858, Calling Number=
Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_SPEECH
*Apr 22 15:34:48.604: //-1/8694A01989B6/DPM/dpMatchCore:
Result=-1
*Apr 22 15:34:48.604: //-1/8694A01989B6/DPM/dpAssociateIncomingPeerCore:
Match Rule=DP_MATCH_ANSWER; Calling Number=9128574118
*Apr 22 15:34:48.604: //-1/8694A01989B6/DPM/dpMatchPeertype:
Is Incoming=TRUE, Number Expansion=FALSE
*Apr 22 15:34:48.604: //-1/8694A01989B6/DPM/dpMatchCore:
Dial String=, Expanded String=, Calling Number=9128574118T
Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_SPEECH
*Apr 22 15:34:48.604: //-1/8694A01989B6/DPM/dpMatchCore:
Result=-1
*Apr 22 15:34:48.604: //-1/8694A01989B6/DPM/dpAssociateIncomingPeerCore:
Match Rule=DP_MATCH_ORIGINATE; Calling Number=9128574118
*Apr 22 15:34:48.604: //-1/8694A01989B6/DPM/dpMatchPeertype:
Is Incoming=TRUE, Number Expansion=FALSE
*Apr 22 15:34:48.604: //-1/8694A01989B6/DPM/dpMatchCore:
Dial String=, Expanded String=, Calling Number=9128574118T
Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_SPEECH
*Apr 22 15:34:48.604: //-1/8694A01989B6/DPM/MatchNextPeer:
Result=Success(0); Incoming Dial-peer=250 Is Matched
*Apr 22 15:34:48.604: //-1/8694A01989B6/DPM/dpAssociateIncomingPeerCore:
Result=Success(0) after DP_MATCH_ORIGINATE; Incoming Dial-peer=250
*Apr 22 15:34:48.604: //-1/8694A01989B6/DPM/dpMatchSafModulePlugin:
dialstring=NULL, saf_enabled=0, saf_dndb_lookup=0, dp_result=0
*Apr 22 15:34:48.604: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 422 Session Timer too small

Via: SIP/2.0/UDP 10.123.101.162:5060;branch=z9hG4bKvp4ubervx4xxwuppr44ubpttt;Role=3;Hpt=8ec8_16

From: <sip:9128574118@10.198.13.86;user=phone>;tag=vtn11qv2-CC-31

To: <sip:20225858@10.198.13.86;user=phone>;tag=1B0EED54-10AD

Date: Sun, 22 Apr 2018 15:34:48 GMT

Call-ID: isbcv222jmm6ejm8n4ssteenqz6nne6qq10t@SoftX3000

CSeq: 1 INVITE

Allow-Events: kpml, telephone-event

Min-SE: 86400

Server: Cisco-SIPGateway/IOS-15.4.1.T3

Content-Length: 0

 


*Apr 22 15:34:48.704: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 422 Session Timer too small

Via: SIP/2.0/UDP 10.123.101.162:5060;branch=z9hG4bKvp4ubervx4xxwuppr44ubpttt;Role=3;Hpt=8ec8_16

From: <sip:9128574118@10.198.13.86;user=phone>;tag=vtn11qv2-CC-31

To: <sip:20225858@10.198.13.86;user=phone>;tag=1B0EED54-10AD

Call-ID: isbcv222jmm6ejm8n4ssteenqz6nne6qq10t@SoftX3000

Min-SE: 86400

CSeq: 1 INVITE

Content-Length: 0

 


*Apr 22 15:34:48.904: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 422 Session Timer too small

Via: SIP/2.0/UDP 10.123.101.162:5060;branch=z9hG4bKvp4ubervx4xxwuppr44ubpttt;Role=3;Hpt=8ec8_16

From: <sip:9128574118@10.198.13.86;user=phone>;tag=vtn11qv2-CC-31

To: <sip:20225858@10.198.13.86;user=phone>;tag=1B0EED54-10AD

Call-ID: isbcv222jmm6ejm8n4ssteenqz6nne6qq10t@SoftX3000

Min-SE: 86400

CSeq: 1 INVITE

Content-Length: 0

 


*Apr 22 15:34:49.304: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 422 Session Timer too small

Via: SIP/2.0/UDP 10.123.101.162:5060;branch=z9hG4bKvp4ubervx4xxwuppr44ubpttt;Role=3;Hpt=8ec8_16

From: <sip:9128574118@10.198.13.86;user=phone>;tag=vtn11qv2-CC-31

To: <sip:20225858@10.198.13.86;user=phone>;tag=1B0EED54-10AD

Call-ID: isbcv222jmm6ejm8n4ssteenqz6nne6qq10t@SoftX3000

Min-SE: 86400

CSeq: 1 INVITE

Content-Length: 0

 


*Apr 22 15:34:56.604: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:20225858@10.198.13.86:5060;user=phone SIP/2.0

Via: SIP/2.0/UDP 10.123.101.162:5060;branch=z9hG4bKvp4ubervx4xxwuppr44ubpttt;Role=3;Hpt=8ec8_16

Record-Route: <sip:10.123.101.162:5060;transport=udp;lr;Hpt=8ec8_16;CxtId=4;TRC=ffffffff-ffffffff;X-HwB2bUaCookie=300>

Call-ID: isbcv222jmm6ejm8n4ssteenqz6nne6qq10t@SoftX3000

From: <sip:9128574118@10.198.13.86;user=phone>;tag=vtn11qv2-CC-31

To: <sip:20225858@10.198.13.86;user=phone>

CSeq: 1 INVITE

Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,REGISTER,INFO,PRACK,SUBSCRIBE,NOTIFY,UPDATE,MESSAGE,REFER

Contact: <sip:9128574118@10.123.101.162:5060;transport=udp;Hpt=8ec8_16;CxtId=4;TRC=ffffffff-ffffffff>

Max-Forwards: 69

Supported: 100rel,timer

User-Agent: Huawei SoftX3000 V300R010

Session-Expires: 300

Min-SE: 90

Content-Length: 271

Content-Type: application/sdp

 

v=0

o=- 16260238 16260238 IN IP4 10.123.101.162

s=SBC call

c=IN IP4 10.123.101.162

t=0 0

m=audio 11334 RTP/AVP 8 3 97 96

a=rtpmap:8 PCMA/8000

a=rtpmap:3 GSM/8000

a=rtpmap:97 telephone-event/8000

a=rtpmap:96 RED/8000

a=ptime:20

a=fmtp:97 0-15

a=fmtp:96 97/97


*Apr 22 15:34:56.604: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
Calling Number=20225858, Called Number=20225858, Peer Info Type=DIALPEER_INFO_SPEECH
*Apr 22 15:34:56.604: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=20225858
*Apr 22 15:34:56.604: //-1/xxxxxxxxxxxx/DPM/dpMatchCore:
Dial String=20225858, Expanded String=20225858, Calling Number=20225858T
Timeout=TRUE, Is Incoming=FALSE, Peer Info Type=DIALPEER_INFO_SPEECH
*Apr 22 15:34:56.604: //-1/xxxxxxxxxxxx/DPM/MatchNextPeer:
Result=Success(0); Outgoing Dial-peer=321 Is Matched
*Apr 22 15:34:56.604: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
Result=Success(0) after DP_MATCH_DEST
*Apr 22 15:34:56.604: //-1/xxxxxxxxxxxx/DPM/dpMatchSafModulePlugin:
dialstring=20225858, saf_enabled=1, saf_dndb_lookup=1, dp_result=0
*Apr 22 15:34:56.604: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersMoreArg:
Result=SUCCESS(0)
List of Matched Outgoing Dial-peer(s):
1: Dial-peer Tag=321
*Apr 22 15:34:56.604: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Calling Number=9128574118, Called Number=, Voice-Interface=0x0,
Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,
Peer Info Type=DIALPEER_INFO_SPEECH
*Apr 22 15:34:56.604: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Match Rule=DP_MATCH_ANSWER; Calling Number=9128574118
*Apr 22 15:34:56.604: //-1/xxxxxxxxxxxx/DPM/dpMatchPeertype:
Is Incoming=TRUE, Number Expansion=FALSE
*Apr 22 15:34:56.604: //-1/xxxxxxxxxxxx/DPM/dpMatchCore:
Dial String=, Expanded String=, Calling Number=9128574118T
Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_SPEECH
*Apr 22 15:34:56.604: //-1/xxxxxxxxxxxx/DPM/dpMatchCore:
Result=-1
*Apr 22 15:34:56.604: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Match Rule=DP_MATCH_ORIGINATE; Calling Number=9128574118
*Apr 22 15:34:56.604: //-1/xxxxxxxxxxxx/DPM/dpMatchPeertype:
Is Incoming=TRUE, Number Expansion=FALSE
*Apr 22 15:34:56.604: //-1/xxxxxxxxxxxx/DPM/dpMatchCore:
Dial String=, Expanded String=, Calling Number=9128574118T
Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_SPEECH
*Apr 22 15:34:56.604: //-1/xxxxxxxxxxxx/DPM/MatchNextPeer:
Result=Success(0); Incoming Dial-peer=250 Is Matched
*Apr 22 15:34:56.604: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Result=Success(0) after DP_MATCH_ORIGINATE; Incoming Dial-peer=250
*Apr 22 15:34:56.604: //-1/xxxxxxxxxxxx/DPM/dpMatchSafModulePlugin:
dialstring=NULL, saf_enabled=0, saf_dndb_lookup=0, dp_result=0
*Apr 22 15:34:56.604: //-1/8B59541989B7/DPM/dpAssociateIncomingPeerCore:
Calling Number=9128574118, Called Number=20225858, Voice-Interface=0x0,
Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,
Peer Info Type=DIALPEER_INFO_SPEECH
*Apr 22 15:34:56.604: //-1/8B59541989B7/DPM/dpAssociateIncomingPeerCore:
Match Rule=DP_MATCH_VIA_URI; URI=sip:10.123.101.162:5060
*Apr 22 15:34:56.604: //-1/8B59541989B7/DPM/dpMatchPeertype:
Is Incoming=TRUE, Number Expansion=FALSE
*Apr 22 15:34:56.604: //-1/8B59541989B7/DPM/dpMatchCore:
Dial String=, Expanded String=, Calling Number=
Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_SPEECH
*Apr 22 15:34:56.604: //-1/8B59541989B7/DPM/dpMatchCore:
Result=-1
*Apr 22 15:34:56.604: //-1/8B59541989B7/DPM/dpAssociateIncomingPeerCore:
Match Rule=DP_MATCH_REQUEST_URI; URI=sip:20225858@10.198.13.86:5060;user=phone
*Apr 22 15:34:56.604: //-1/8B59541989B7/DPM/dpMatchPeertype:
Is Incoming=TRUE, Number Expansion=FALSE
*Apr 22 15:34:56.604: //-1/8B59541989B7/DPM/dpMatchCore:
Dial String=, Expanded String=, Calling Number=
Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_SPEECH
*Apr 22 15:34:56.604: //-1/8B59541989B7/DPM/dpMatchCore:
Result=-1
*Apr 22 15:34:56.604: //-1/8B59541989B7/DPM/dpAssociateIncomingPeerCore:
Match Rule=DP_MATCH_TO_URI; URI=sip:20225858@10.198.13.86;user=phone
*Apr 22 15:34:56.604: //-1/8B59541989B7/DPM/dpMatchPeertype:
Is Incoming=TRUE, Number Expansion=FALSE
*Apr 22 15:34:56.604: //-1/8B59541989B7/DPM/dpMatchCore:
Dial String=, Expanded String=, Calling Number=
Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_SPEECH
*Apr 22 15:34:56.604: //-1/8B59541989B7/DPM/dpMatchCore:
Result=-1
*Apr 22 15:34:56.604: //-1/8B59541989B7/DPM/dpAssociateIncomingPeerCore:
Match Rule=DP_MATCH_FROM_URI; URI=sip:9128574118@10.198.13.86;user=phone
*Apr 22 15:34:56.604: //-1/8B59541989B7/DPM/dpMatchPeertype:
Is Incoming=TRUE, Number Expansion=FALSE
*Apr 22 15:34:56.604: //-1/8B59541989B7/DPM/dpMatchCore:
Dial String=, Expanded String=, Calling Number=
Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_SPEECH
*Apr 22 15:34:56.604: //-1/8B59541989B7/DPM/dpMatchCore:
Result=-1
*Apr 22 15:34:56.604: //-1/8B59541989B7/DPM/dpAssociateIncomingPeerCore:
Match Rule=DP_MATCH_INCOMING_DNIS; Called Number=20225858
*Apr 22 15:34:56.604: //-1/8B59541989B7/DPM/dpMatchPeertype:
Is Incoming=TRUE, Number Expansion=FALSE
*Apr 22 15:34:56.604: //-1/8B59541989B7/DPM/dpMatchCore:
Dial String=20225858, Expanded String=20225858, Calling Number=
Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_SPEECH
*Apr 22 15:34:56.604: //-1/8B59541989B7/DPM/dpMatchCore:
Result=-1
*Apr 22 15:34:56.604: //-1/8B59541989B7/DPM/dpAssociateIncomingPeerCore:
Match Rule=DP_MATCH_ANSWER; Calling Number=9128574118
*Apr 22 15:34:56.604: //-1/8B59541989B7/DPM/dpMatchPeertype:
Is Incoming=TRUE, Number Expansion=FALSE
*Apr 22 15:34:56.604: //-1/8B59541989B7/DPM/dpMatchCore:
Dial String=, Expanded String=, Calling Number=9128574118T
Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_SPEECH
*Apr 22 15:34:56.604: //-1/8B59541989B7/DPM/dpMatchCore:
Result=-1
*Apr 22 15:34:56.604: //-1/8B59541989B7/DPM/dpAssociateIncomingPeerCore:
Match Rule=DP_MATCH_ORIGINATE; Calling Number=9128574118
*Apr 22 15:34:56.604: //-1/8B59541989B7/DPM/dpMatchPeertype:
Is Incoming=TRUE, Number Expansion=FALSE
*Apr 22 15:34:56.604: //-1/8B59541989B7/DPM/dpMatchCore:
Dial String=, Expanded String=, Calling Number=9128574118T
Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_SPEECH
*Apr 22 15:34:56.604: //-1/8B59541989B7/DPM/MatchNextPeer:
Result=Success(0); Incoming Dial-peer=250 Is Matched
*Apr 22 15:34:56.604: //-1/8B59541989B7/DPM/dpAssociateIncomingPeerCore:
Result=Success(0) after DP_MATCH_ORIGINATE; Incoming Dial-peer=250
*Apr 22 15:34:56.604: //-1/8B59541989B7/DPM/dpMatchSafModulePlugin:
dialstring=NULL, saf_enabled=0, saf_dndb_lookup=0, dp_result=0
*Apr 22 15:34:56.604: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 422 Session Timer too small

Via: SIP/2.0/UDP 10.123.101.162:5060;branch=z9hG4bKvp4ubervx4xxwuppr44ubpttt;Role=3;Hpt=8ec8_16

From: <sip:9128574118@10.198.13.86;user=phone>;tag=vtn11qv2-CC-31

To: <sip:20225858@10.198.13.86;user=phone>;tag=1B0F0C94-263B

Date: Sun, 22 Apr 2018 15:34:56 GMT

Call-ID: isbcv222jmm6ejm8n4ssteenqz6nne6qq10t@SoftX3000

CSeq: 1 INVITE

Allow-Events: kpml, telephone-event

Min-SE: 86400

Server: Cisco-SIPGateway/IOS-15.4.1.T3

Content-Length: 0

 


*Apr 22 15:34:56.704: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 422 Session Timer too small

Via: SIP/2.0/UDP 10.123.101.162:5060;branch=z9hG4bKvp4ubervx4xxwuppr44ubpttt;Role=3;Hpt=8ec8_16

From: <sip:9128574118@10.198.13.86;user=phone>;tag=vtn11qv2-CC-31

To: <sip:20225858@10.198.13.86;user=phone>;tag=1B0F0C94-263B

Call-ID: isbcv222jmm6ejm8n4ssteenqz6nne6qq10t@SoftX3000

Min-SE: 86400

CSeq: 1 INVITE

Content-Length: 0

 


*Apr 22 15:34:56.904: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 422 Session Timer too small

Via: SIP/2.0/UDP 10.123.101.162:5060;branch=z9hG4bKvp4ubervx4xxwuppr44ubpttt;Role=3;Hpt=8ec8_16

From: <sip:9128574118@10.198.13.86;user=phone>;tag=vtn11qv2-CC-31

To: <sip:20225858@10.198.13.86;user=phone>;tag=1B0F0C94-263B

Call-ID: isbcv222jmm6ejm8n4ssteenqz6nne6qq10t@SoftX3000

Min-SE: 86400

CSeq: 1 INVITE

Content-Length: 0

 


*Apr 22 15:34:57.304: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 422 Session Timer too small

Via: SIP/2.0/UDP 10.123.101.162:5060;branch=z9hG4bKvp4ubervx4xxwuppr44ubpttt;Role=3;Hpt=8ec8_16

From: <sip:9128574118@10.198.13.86;user=phone>;tag=vtn11qv2-CC-31

To: <sip:20225858@10.198.13.86;user=phone>;tag=1B0F0C94-263B

Call-ID: isbcv222jmm6ejm8n4ssteenqz6nne6qq10t@SoftX3000

Min-SE: 86400

CSeq: 1 INVITE

Content-Length: 0

 

 

please help asap

30 Views
0 Comments

The ILS - Intercluster Lookup Service feature enables different CUCM Cluster to exchange directory URI with other clusters in an ILS network. URI Replication provides support for intercluster URI dialing. ILS runs as a service on the Publisher node of a cluster. 

 

We can call ILS - Intercluster Lookup Service as Voice Routing Protocol because it behaves like dynamic routing protocol. Just like advertising the local route from one router to another, ILS will advertise the URIs between different CUCM cluster.

 

Each CUCM cluster node advertises its URIs and “SIP route string” to its neighbor’s (or Hubs). CUCM cluster later creates a table with URIs and associated SIP route string. Finally, SIP route strings are routed through SIP route patterns.Intercluster Lookup Service Configuration.jpg

Contents

1. ILS Configuration using Password Authentication

2. ILS Configuration using TLS Certificate Authentication

3. ILS Configuration using TLS Certificate Authentication - Common CA Signed

 

There are two types of clusters in ILS.

Hub Cluster:

  • Each ILS network must have at least one hub cluster and they are the backbone of an ILS network.
  • Hub clusters exchange ILS updates with the other hub clusters in the ILS network and then relay that information to and from their spoke clusters.
  • You can connect a hub cluster to multiple other hub clusters, or you might configure a hub cluster as the only hub cluster in the network.
  • In addition, you can connect a hub cluster to multiple spoke clusters, or you might configure the hub cluster with no spokes clusters. 

Spoke Cluster

  • A spoke cluster in an ILS network relies on the hub cluster that it is connected to in order to relay ILS updates to and from the rest of the ILS network.
  • A spoke cluster can have only one hub cluster.

 

In this document, we are going to see the step by step configurations for ILS - Intercluster Lookup Service with password authentication as well as TLS (Certificate) authentication.

 

Topology

I have 2 CUCM clusters here in the ILS network.

  • 10.106.79.71 - HQ Cluster
  • 10.106.79.83 - BR Cluster

topology.png

 

1. ILS Configurations Using Password Authentication

  • ILS password authentication configuration is pretty easy and straightforward. The HUB and SPOKE clusters will exchange some unique password to establish ILS connection.

Let's have a look at the configuration window.

Step 1.1: Activate Intercluster Lookup Service on all the CUCM Publisher

Go to Service Ability > Tools > Service Activation > Select 'Intercluster Lookup Service' and save.

 

0.png

Step1.2: Set Cluster ID for the CUCM Clusters

Cluster ID is a unique identifier for the cluster.

Go to CUCM Administration Page > System > Enterprise Parameter > Cluster ID

 

1.png

 

Note: Make sure you configure unique cluster ID for all the nodes in the ILS network.Moreover, we need to restart all services for the parameter change to take effect.

Step 1.3: HUB Cluster ILS Configuration

I'm planning 10.102.79.71 as my ILS HUB Cluster.

Go to Advanced Features > ILS Configuration > and configure as follows.


AA1.png

 

> Save

Route String: This will be a unique string that will be advertised to the other clusters. Other ILS peers use Route String to route the call.

 

Above configuration uses 'Password' based ILS authentication and synchronize the clusters every 1 minute.

 

Note: When you configure the Advertise Route String, make sure it is less complex. Sometimes the URI Call fails if we have more "-" and "Letters" in the Route String. Bug: CSCtz63687

 

The moment you click Save, it will ask for ILS Registrar Server. Since I do not have any other HUB cluster, we can leave blank and click OK

 

4.png

 

Step 1.4: Spoke Cluster ILS Configuration

10.106.79.83 is our SPOKE cluster.

Go to Advanced Features > ILS Configuration > and configure as follows.


A2.png

 

When you click Save, enter the Registrar server as the HUB cluster 10.106.79.71.

 

6.png

 

Step 1.5: Refresh the ILS Configuration 

Now refresh the ILS configuration to see the updated status.

 

A3.png

 

Step 1.6: Configure URIs for the End Users

Go to User Management > End User > and select the user you want to enable URI.

For LDAP user, make sure the URI is synced from LDAP server. For the local users, you can set a URI as shown below.CUCM End User URI Configuration.png

 

Now go to the Controlled Devices section in the same page and assign the user's desk phone as the controlled device. Also, configure the primary extension.Primary extension for URI dialing.png

 

Note: Primary extension maps the URI with the Directory number, hence it is mandatory to configure primary extension on the user page. Also, note that all the URIs will be in the 'Directory URI' partition by default.

 

Now go ahead and check the Directory number (e.g. 1002), you will be able to see the URI field.Direcory URI configuration CUCM.png

 

Similarly, you configure another URI for a test user in another cluster.

Step 1.7: Verify the Learned Directory URIs

Go to Call Routing > Global Dial Plan Replication > Learned Directory URIs9.png

 

A4.png

 

Note: Any of the URI learned via ILS will be having 2 unique values. One is the Route String and another one is Cluster ID. Route String is used to route the call back to the respective cluster via a separate SIP trunk.

 

ILS will only take care of advertising the URIs between clusters. They do not participate in call routing. For dialing the URI from one cluster to another, we need to have a separate SIP trunk.

Step 1.8: Create a SIP Trunk in Hub & Spoke Cluster and Point each other

  • Create a SIP Trunk in Hub Cluster CUCM and point the destinations to the Subscriber servers (CUCM Nodes which runs CCM Service) of the Spoke cluster.

 

  • Create a SIP Trunk in Spoke Cluster CUCM and point the destinations to the Subscriber servers (CUCM Nodes which runs CCM Service) of the Hub cluster.

11.png

  • Since configuring SIP Trunk is out the scope of this article, I have just provided above screenshot. Feel free to comment here any queries regarding the SIP trunk.

Note: By default, all the URIs will be assigned with 'Directory URI' partition. Hence you must have a CSS with Directory URI partition that is assigned as Inbound CSS at the SIP Trunks.

 

A5.png

 

A6.png

 

Step 1.9: Configure SIP Route Pattern

  • The Advertise String of other ILS node will be the SIP Route Pattern. We need to create SIP Pattern at the HQ cluster as well as BR Cluster.

Go to Call Routing > SIP Route Pattern > Add New and Point the SIP Trunk.

 

A7.png


A81.png

 

Step 1.10: LAB Testing

  • I have configured a speed dial as a URI which points to the other cluster. Calls are working fine in both directions.

URI Speed Dial in CUCM.png

 

A9.png

 

Warning: The above method is the simplest way of getting the ILS up and running. In order to read further on this article (other ways of configuring ILS), you need to have a better understanding of CUCM Certificates and Multi SAN Certificates 

2. ILS Configurations Using TLS (Certificate) Authentication (Certificate Cross Import Method)

  • To use Transport Layer Security (TLS) authentication between clusters, you must exchange Tomcat certificates between the publisher node of each cluster in the ILS network.
  • From HUB Cluster Cisco Unified Operating System Administration, download the Cisco Tomcat Certificate.
  • Upload the same as Tomcat Trust in the SPOKE cluster.
  • Similarly, download Cisco Tomcat certificate from SPOKE cluster and upload to HUB as Tomcat Trust.
  • Service activation (Step 1.1) and Cluster ID configuration (Step 1.2) are same in this section as well. Hence I haven't added those screenshots.

Step 2.1: Downloading Tomcat Certificate from HUB Cluster

  • Go to OS Administration Page of HUB Cluster Publisher Server.

Security > Certificate Management > and the search for 'Tomcat'

 

Cisco Tomcat Certificate Management.png

 

Note: In my example, I have a CA-signed Certificate, but the procedure is pretty same for Self Signed certificate as well.

  • Click on the certificate and Download it (Save in a proper place).Download CUCm Tomcat Certificate.png

     

Step 2.2: Upload the HUB Certificate to the SOPKE as Tomcat-Trust

Login to SPOKE cluster publisher OS Administration > Security > Certificate Management > Upload Certificate/Certificate chain.CUCM Upload CertificateCertificate chain.png

 

  • Now browse the certificate downloaded in Step 2.1 and then click 'Upload' button.

ILS Upload CertificateCertificate chain.png

 

Note: The system will tell you to restart Cisco Tomcat Service but it is actually not required! :)

Step 2.3 & 2.4: Upload SPOKE Certificate as Trust in HUB

Follow the same process and get the certificate from Spoke cluster and upload to HUB as Tomcat Trust.

Step 2.5: Configure ILS on the HUB & SPOKE Clusters with TLS Certificate Authentication

Go to Advanced Features > ILS Configuration > and configure as follows.ILS Configuration based on TLS Authentication.png

 

Note: When we click Save on the HUB, it will ask for the registrar server, please Skip that. But when you click Save on the SPOKE, please provide HUB IP address to the registrar server.

 

  • Also, note that we have selected 'Use TLS Certificates' as the ILS authentication mechanism.

 

Register Spoke cluster to ILS Hub.png

 

  • Refresh the configuration after few minutes.

ILS Connection established using TLS Certificates.png

 

  • ILS connection has been established. The remaining configurations like adding URIs, creating SIP Route Pattern, SIP Trunk and Speed dials (Step 1.6 to Step 1.10) is same as discussed above.

3. ILS Configurations Using TLS (Certificate) Authentication (Common CA-signed Method)

  • In the multi-cluster environment (more than 20+ clusters for example), exchanging (cross importing) certificate between all the clusters are not practical (or time-consuming).
  • When the certificate expires, you will have to cross import the certificates again.
  • In that scenario, we can use the Common CA-signed certificates to on every cluster.
  • Once we have HUB and SPOKE tomcat certificates are signed by same CA, we do not need to cross import the certificates each other.
  • But in this case, we need to use Password Authentication first and once it establishes the ILS connection, switch back to TLS.

Note: In CUCM Version 10.5, you can either select Password Authentication or TLS Authentication but not both. Whereas in CUCM Version 11.5, we can select both.

Summary:

  • Use common CA to sign the tomcat certificate of HUB and SPOKE
  • Establish ILS with Password authentication only
  • Switch the ILS authentication to TLS only.

ILS Connection comparison.png

 

Step 3.1: Download HUB and SPOKE Tomcat Certificates

There are different methods to check the Tomcat certificate. The easiest way would be opening the HUB CUCM-PUB URL on Internet Explorer and click the Security Report lock button > View Certificate.

 

View CUCM Tomcat Certificate from Internet expolorer.png

 

Go to the Details tab and click Copy to File....Cisco Tomcat Certificate details.png

 

Click Next from the Certificate export wizard window.CUCM Certificate export wizard.png

 

Select DER encoded binary X.509 (.CER)DER encoded binary X.509.png

 

Enter the directory path to Save the CUCM certificate and proceed.

 

Managing CUCM Certificates.png

 

Click Finish button to complete the certificate download process. You will be getting Export Successful message.Exporting CUCM certificate.png

 07.png

 

Repeat the same steps for downloading SPOKE CUCM-PUB tomcat certificate.

Step 3.2: Verify the HUB and SPOKE Tomcat Certificates

Once you have the HUB and SPOKE certificates downloaded, open those in side by side and compare the following. We have to perform a number of checks.

 

Check 1: Issued by

Go to the General tab of the Certificate and check the 'Issues by' field. This should be same in the HUB and SPOKE certificates. For this example, the certificate is issued by 'UCCOLLAB-CA'

 

CUCM certificate requirement for ILS configuration.png

 

Check 2: Enhanced Key Usage 

Go to the Details tab of the certificate and check the 'Enhanced Key Usage' field. There should be 'Server Authentication' and 'Client Authentication'

 

Enhanced Key Usage in CUCM Certificate.png

 

Check 3: Certification Path

Go to 'Certification Path' and check the hierarchy. It should be similar on HUB and SPOKE. 

 

CUCM Tomcat Certification Path.png

 

Note: if there is an intermediate CA, you can see that is on the path. Make sure both HUB and SPOKE follows same certification path.

Step 3.3: Check the HUB Hostname & Certificate Common Name

Check 4: Server name and Common Name of HUB

Login to the HUB cluster Publisher CLI and check the Common name of the Publisher using 'show network cluster' command.ILS Hub show network cluster.png

 

  • Here the Publisher name is 01-01-CUCM01-PUB.uccollab1.com
  • You have to see the same name on the HUB Publisher certificate Subject Name field CN.
  • Open the Certificate and go to Details tab > Subject and check the CN - Common Name.
  • In our case, it is matching to the above CLI output 01-01-CUCM01-PUB.uccollab1.com

 

CUCM Certificate Subject Name.png

 

Check 5: Server name and Common Name of SPOKE

Login to the SPOKE cluster Publisher CLI and check the Common name of the Publisher using 'show network cluster' command.ILS Spoke show network cluster.png

 

  • Here the SPOKE Publisher name is 01-13-CUCM01-PUB
  • Open the Certificate and go to Details tab > Subject and check the CN - Common Name.
  • In our case, it is matching to the above CLI output, that is 01-13-CUCM01-PUB

ILS CUCM Certificate Subject Name.png

 

Note: I do not have DSN server configured for SPOKE cluster. Hence we have only the hostname in the 'show network cluster' and in the 'Certificate'. If I would have configured DNS, this could have been an FQDN (refer the HUB certificate where I have DNS configured).

Step 3.4:  Establish ILS Connection with Password Only and Populate the Peer-vector

Go to Advanced Features > ILS Configuration > and establish the ILS connection between HUB and SPOKE using password authentication method (already explained in Step 1.3, Step 1.4)

 

ILS Password Peer.png

 

Once we have the ILS connection established, the Peer-vector table will populate automatically. Log in to the CLI of each publisher and issue 'utils ils showpeerinfo'. Make sure you have all the ILS peers in the output.

 

utils ils showpeerinfo.png

Step 3.5: Compare Peer-Vector Table with Subject Common Name

  • Basically, we establish ILS initially with Password Authentication and then switch back to TLS only.
  • Behind the scene, when we use the password to establish the ILS connection, the ILS node will update the peer-vector table, which is a DB Table that contains all the ILS peers information.
  • Use 'utils ils showpeerinfo' CLI command to see the ILS peer table.
  • Once we switch to TLS only (after establishing the ILS with password), the HUB will check the Common name of the Publisher in the Certificate to matches with peer-vector table Clustername.
  • The peer-vector table was already populated with all peers when we used password authentication.

Check 6: Peer-vector Vs Common Name

Go to HUB cluster Publisher CLI and issue this command 'utils ils showpeerinfo' and check the 'Clustername' of SPOKE. This should match the Subject CN of SOPKE's certificate.

ILS Peer info Certificate common name.png

 

Go to SPOKE cluster Publisher CLI and issue this command 'utils ils showpeerinfo' and check the 'Clustername' of HUB. This should match the Subject CN of HUB's certificate.

ILS Configuration with Certificate authentication common name.png

 

Step 3.6: Switch Back to TLS Authentication

Once the peer-vector table is updated, we can remove the password authentication and use TLS authentication only.

Go to Advanced Features > ILS Configuration > Change the authentication back to 'Use TLS Certificate'

 

ILS Connection established using TLS Certificates CA Signed.png

 

  • We noticed that the ILS connection is remains established even after removing the Password Authentication. 
  • The 6 number of Checks are mandatory to have a successful ILS connection
  • The remaining configurations like adding URIs, creating SIP Route Pattern, SIP Trunk and Speed dials (Step 1.6 to Step 1.10) is same as discussed above.

 

Note: Any time if the ILS connection is broken and if you want to re-establish, we need to do the same process again (first password and then TLS)

 

 

Comments to the Readers:

We have successfully done all possible ways of configuring ILS. If you are able to follow all the process explained above, there won't be any issues while configuring and troubleshooting ILS. I will be publishing a detailed ILS troubleshooting (with ILS traces and logs) article soon. Please rate this article if helped. Feel free to ask doubts.

 

Few of my other Support forum Documents:

You may also interested to take a look at my other articles in the support forum.

 

Regards,

Abdul Jaseem

 

16 Views
0 Comments

I have a customer that wants to migrate from expensive analog FXS lines to a SIP Provider/ITSP.  After getting multiple quotes, it seemed like Nextiva was the best fit for this small office environment.  Once we signed up for Nextiva, I was less than impressed with the amount of support they offer to get customer's SIP trunks operational.  Their Tier 4 support can basically only tell you if your connected to them or not.  They'll tell you to install a free soft phone and if your soft phone registers, they say they've proven their side is good and it's up to you to figure out your PBX configurations.  They have no example configs or recommendations for Cisco CME/CUBE/VGRs connecting to Nextiva.  I was given my Username, Password, and the domain bt.voipdnsservers.com

 

So, after hours of analyzing packet captures, debugs, and working with TAC, I was able to get a working configuration between Cisco CME/CUBE and Nextiva.  I'm posting the relevant configurations to hopefully save everyone a huge headache and a ton of time, if you choose Nextiva as a SIP trunk provider ITSP.

 

My environment includes a CME/CUBE, with all SIP traffic bound to loopback 0.  I'm using private IP space on the LAN and NAT'ing all networks at my firewall that connects to the ISP.

 

First things first, ensure that the IP of the CME/CUBE Loopback 0 is included in your NAT at the firewall and that your firewall has the proper routes to the CME/CUBE Loopback 0 address on the inside.  I did not perform any PAT inbound to the CME and I did not add ACLs permiting SIP or anything inbound.

 

Nextiva needs the SIP messages to come in a certain way.  We will be creating a SIP Profile to modify the SIP header as it is sent out.  I will include a generic dial-peer showing the SIP Profile applied.  By default, any existing pots dial-peer will try to register with the SIP Registrar, so i will include a pots dial-peer command that stops that.  Since the Nextiva IP's are not specifically configured as a SIP destination, inbound calls will be denied by default when coming from an unknown IP.  We will add ip address trusted list commands to the CUBE configuration to allow the IP's in. You can modify this to the exact IP's of the ITSP.

 

voice service voip
ip address trusted list
 ipv4 0.0.0.0 0.0.0.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 refer
fax protocol pass-through g711ulaw
h323
sip
 bind control source-interface Loopback0
 bind media source-interface Loopback0
 no call service stop

!
voice class codec 1
 codec preference 1 g711ulaw
 codec preference 2 g729r8
!

!

!***Note that the ALL_CAPS portions require your information*******

!

!
voice class sip-profiles 200
request ANY sip-header From modify "YOUR_LOOPBACK_IP_ADDRESS" "bt.voipdnsservers.com"
request ANY sip-header From modify "sip:(.*)@" "sip:NEXTIVA_USERNAME/PHONE_NUMBER@"
request INVITE sip-header SIP-Req-URI modify "bt.voipdnsservers.com:5060" "bt.voipdnsservers.com"
!
!

!

!

!

dial-peer voice 100 pots
 no sip-register

!

dial-peer voice 200 voip
description Incoming_Calls_From_ITSP
session protocol sipv2
incoming called-number YOUR PHONE NUMBER FROM ITSP
voice-class codec 1
dtmf-relay rtp-nte sip-notify
no vad
supplementary-service h450.12

!

dial-peer voice 201 voip

description Outbound_Calls_To_ITSP
destination-pattern ..........
session protocol sipv2
session target dns:bt.voipdnsservers.com
voice-class sip profiles 200
dtmf-relay rtp-nte sip-notify
voice-class codec 1
no vad
!

 

!

!

sip-ua
 credentials username YOUR_USER_NAME password YOUR_PASSWORD realm bt.voipdnsservers.com
 credentials username YOUR_USER_NAME password YOUR_PASSWORD realm nextiva.com
 authentication username YOUR_USER_NAME password YOUR_PASSWORD realm bt.voipdnsservers.com
 authentication username YOUR_USER_NAME password YOUR_PASSWORD realm nextiva.com
 no remote-party-id
 retry invite 10
 retry register 10
 retry subscribe 3
 registrar dns:bt.voipdnsservers.com expires 3600
 sip-server dns:bt.voipdnsservers.com
 host-registrar
!

 

 

To verify your registration, run the following command:

 

show sip-ua register status

 

You should see the phone number/username showing "yes" for registerd.  It may take a few test calls before calls for the ITSP to begin routing calls.

 

I hope this helps!

187 Views
1 Comment

Hello guys!

 

I am not an expert but I read and try to make it happen. This might be simple, however, I was not able to find it in many tutorials. So I said I would share it with you guys. Because I have learned a lot from you guys. So I am trying to keep passing knowledge here. Please follow the scenario and you will find the answer.   

Recently I was working on changing the Wallpaper of 8841 and 8865. I was kinda stuck on not having the new images that I uploaded. When I go to settings > wallpapers. I can only see the old images or the default images. Even though my sizes images were perfect and the directory was OK! no syntax errors in my List.xml everything was smoothly restarted my TFTP servers couple times no changes. I was like whats going on until I found the solution is by deleting a file named List.xml.sgn !!! and restarted the TFTP servers and worked! List.xml.sgn was generated again after the restart.  

 

Thank you!

 

// Moe

109 Views
0 Comments

We have struggled with an issue for more than a year related to HA over WAN. Even a brief network outage (1-2 seconds) between data centers would cause the master role to switch from the publisher to the subscriber. Mastership changed any time the nodes went into island mode. We finally found the root cause after numerous TAC cases, and I think it's worth sharing since changing the hostnames is supported.

The logic to elect the master node when recovering from island mode is:

Step 1. Check the service status of the nodes. If node 1 is IN_SERVICE and node 2 is in PARTIAL_SERVICE, node 1 becomes the master. If the states are the same (IN_SERVICE or PARTIAL_SERVICE), go to step 2.

Step 2. The hardware specification of both nodes will be checked. The server with the better specification will be handed the mastership. If the hardware specifications are the same, go to step 3.

Step 3. The publisher (i.e. node 1) will become the master if the hostname matches the PrimaryEngineComputerName in the ClusterSpecificConfig. If there is no match, go to step 4.

Step 4. Make the subscriber master.

Alright, now let's back up about 18 months. We decided to build a new cluster to migrate from version 9.0 to 10.6. The intent was to simplify the transition from CAD to Finesse. We built a new cluster on 9.0, restored from backup, changed the hostnames and IPs, and then upgraded to 10.6.  

Back to the present (now on version 11.6), we finally lucked out with a TAC engineer that explained the island mode recovery process above. The engineer used the CET (Configuration Editor Tool) to check the ClusterSpecificConfig file where we discovered the primaryEngineComputerName was the hostname of our 9.0 publisher. So now we know step 3 above always fails and the subscriber is elected master as a result.

PrimaryEngineComputerName.png

 

TAC advised this value is populated at the time of install and cannot be changed (even with root access). The 9.0 cluster had been offline for over a year. Therefore, the best solution was to rename the 11.6 publisher to match the primaryEngineComputerName.

In conclusion, changing the hostname is supported, but it will cause issues with HA. Ideally, the set network hostname command should be updated to also change the primaryEngineComputerName. I asked to have a caveat added to the appropriate section of the admin guide. It's unclear if this request reached the technical writing team – I never received confirmation.

46 Views
0 Comments

Hi folks

Recently I made a python script to aid on configuring streaming URL for a customer.

Pretty simple but pretty helpful, it saved me hours.

Cheers

 

https://gitlab.com/aocbrasil/cms-streamer.git

 

97 Views
0 Comments

Screenshot_2.png

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

no permite cargar los codec

Screenshot_3.png

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

esta si permite cargar los codec desde el cucdm

 

 

243 Views
0 Comments

Long time integrator of Cisco technologies and I was told there is an API that provides an interface to query real-time or near realtime QoS data from the actual endpoint device. If you are aware of such a mechanism can you point me to where I can read about it.

 

Information from TP and Meeting Server logs are just rolled up summary of the session. I Am looking for more time-based granularity.  Or is the only option using SNMP? 

Read more...

77 Views
0 Comments

To look at media resources and the allocated MRGs, use the sql query

 

run sql select mrg.name as mrg,d.name as resource from mediaresourcegroup mrg inner join mediaresourcegroupmember mgm on mgm.fkmediaresourcegroup=mrg.pkid   inner join device d on mgm.fkdevice=d.pkid

 

To filter specific site

 

run sql select mrg.name as mrg,d.name as resource from mediaresourcegroup mrg inner join mediaresourcegroupmember mgm on mgm.fkmediaresourcegroup=mrg.pkid   inner join device d on mgm.fkdevice=d.pkid where d.name like '%AD1%' or mrg.name like '%A01%'

 

Use this CLI command to find media resources in the default MRG (no assigned to any created MRG).

admin:run sql select d.name as resource from device as d full outer join mediaresourcegroupmember as mgm on mgm.fkdevice=d.pkid where and mgm.pkid is NULL

resource  

===========

AD1MTP-G711 

AD1XCODER

 

 

You look for specific device type such as MTP

 

admin:run sql select d.name as resource from device as d full outer join mediaresourcegroupmember as mgm on mgm.fkdevice=d.pkid where d.name like '%MTP%' and mgm.pkid is NULL

resource  

===========

AD1MTP-G711

406 Views
0 Comments

Well I am new here and not a high level professional  if anything wrong please correct me this blog is all about my own experience and challenges faces after  migration from Cisco  Agent Desktop 8.5 to Cisco Finesse Agent Desktop 11.5.

Recommendation:

I strongly recommend that you guys created a isolated environment during migration and test each and everything thing before migration in comparison  with older one.

Challenges Faced After Migration:

We had created an isolated environment and thinking wow we are up the mark and everything will work smoothly but the story began after migration we had tested prompts, scripts all other thing perfectly but when we login to Cisco Finesse Agent we shocked it's a simple gadget without Chat and other things everything is customized able. We had researched a lot and doesn't found any chat gadget up to the mark so we requested client and used Cisco Jabber instead of Cisco IP Communicator. Well Story not ended yet when we login to Cisco Finesse Supervisor and in the newer version Cisco Supervisor is not able to see Agent incoming/outgoing call status as per previous Cisco Agent Desktop again we had researched on it and doesn't found any gadget as it required customization at CTI level which will impact our reputation badly towards Client. It is requested all of you guys who is doing migration first time please keep in mind that Cisco Finesse is limited gadgets as compare to Cisco Agent Desktop(CAD). Hopefully Cisco is working on this and will create new gadgets to overcome these type of problems.

Thanks,

59 Views
0 Comments

Приветствую, коллеги. 

Есть задача заставить совершаться звонки с Jabber на внешние адреса и по SIP и по h323.

Имеем схему "Cisco Jabber - CUCM - Expressway C - ExpressWay E - внешние абоненты."

Конспективно решение выглядит следующим образом:

1. На "CUCM" (Call Routing -> SIP Route Pattern) создается маршрут используя "Domain Routing" с указанием домена на который требуется вызов и транка на "ExpressWay C".


2. На обоих серверах "ExpressWay C" и "ExpressWay E" (Configuration -> Protocols ->h323 или SIP) проверяем, что включены оба протокола SIP и H323. А также включена функция "Interworking" (Configuration -> Protocols -> Interworking) "H.323 <-> SIP interworking mode" в состоянии "On".


3. На "ExpressWay E" (Configuration -> Authentication -> Devices -> Local database) создается пользователь для аутентификации создаваемой далее зоны между "ExpressWay С" и "ExpressWay E".


4. На "ExpressWay E" (Configuration -> Zones -> Zones) создается зона с указанием: тип зоны "Traversal server", ранее созданные Логин/пароль для аутентификации, порты для протоколов SIP и H323.


5. На "ExpressWay C" (Configuration -> Zones -> Zones) создается зона с указанием: тип зоны "Traversal client", ранее созданные Логин/пароль для аутентификации, ранее указанные порты для протоколов SIP и H323, в поле "Peer 1 address" адрес "ExpressWay E". Внутренний, если у вас используется Dual Network конфигурация.


6. Проверяем, что статус зоны на обоих серверах "ExpressWay C" и "ExpressWay E" по обоим протоколам, SIP и H323, в состоянии "Active".


7. На "ExpressWay C" (Configuration -> Dial Plan -> Search rules) создается правило по маршрутизации поступившего с "CUCM" вызова на требуемый домен: оставляя структуру вызова как она была, отправлять на ранее созданную зону "ExpressWay E".


8. На "ExpressWay E" (Configuration -> Zones -> Zones) создается DNS зона, где включаются оба протокола, выбирается транспортный протокол (TSP/UDP/TLS) и самое главное в разделе "Advanced" в поле "Include address record" ставим "On"! Включение данного параметра позволяет собственно разрешать имена в адреса при помощи DNS. 


9. На "ExpressWay E" (Configuration -> Dial Plan -> Search rules) создается создается правило по маршрутизации поступившего с "ExpressWay C" вызова на требуемый домен и оставляя структуру вызова как она была отправлять на только что созданную DNS зону.


10. На "ExpressWay E" (Configuration -> Dial Plan -> Configuration) в поле "Calls to unknown IP addresses" установить параметр "Direct".


11. Проверяем работоспособность.

650 Views
0 Comments

Hello colleagues

After a difficult deployment in South Korea, I want to share with you the complete Dial Plan and Dial Peer configuration for Cisco CUBE and SIP trunking.

As some of you might have experienced, trying to find the complete dial plan for South Korea is practically impossible if you don't speak Korean (which I don't, just for the record).

South Korea uses a non standard dial plan with different length numbers, area codes and public services; preceeding zeros an local dialing within it's different provinces. In my case, I implemented this for an office in Seoul

In order to implement this dial plan, it was necessary to investigate all the possible dial patterns and transform the dialing to a fully E164 compliant dialing (Service Provider requirement).

I used a Cisco 4331 router with Cisco IOS XE Software, Version 03.16.05.S. UCk9 and CUBE licenses,

I'm also attaching the Excel file with the different patterns for CUCM and Cisco IOS Router.

Hope this is useful for anybody and a big thanks to my coworker Tae who helped me with the translation of the Excel

Best

Allan Mancera

958 Views
2 Comments

imageLike with most new technologies, beginnings can be painful.

With ITSP trunks,it is no different.

The lack of specific rules and instructions can lead to a daunting experience when trying to deal with CUBE Registration with ITSP.

We have all been there, the rough first implementation of CUBE and the bliss of overcoming the obstacles, just to find out that the next CUBE implementation will lead us through a whole new path in an uncharted territory.


And it is not our fault either! We read, we researched, we took examples and yet, the the hurdles are just getting more complicated.

The problem is, there are too many possible scenarios. Some of the main reasons for the massive variations are:

  • ITSPs has to support a wide range vendors, thus, interpretations of IETF.
  • Different ITSPs use different vendors softswitches and architectures.
  • Our own designs, products and versions vary from customer to customer.

Hence, variations in deployments are unavoidable. Fortunately, these problems are solvable, as long as we understand some basic concepts.

In this post I'll cover the CUBE Registration and CUBE Authentication concepts as they are the core of our communication with the ITSP.

Get ready

The hard truth is, more often than not, the customer mails us this poor scanned fax that he received from the ITSP, which usually includes three lines: username, password and IP address.
Well yippiee ki-yay!! Didn't I just win the lottery!!
At times, it felt like it would be easier to extract information from a spy..
So, if we don't want to spend the night chasing ghosts, we have to ask the right questions!

The bare minimum that we have to discover is the ITSP's approach to registration and it's approach to authentication. Mentally note that these are two different concepts with different roles. Let's see what they are all about.


CUBE Registration


Ever wondered what registration to ITSP is really for? Well, I did, and to be honest, too late for my own good.

Simply put, registration is there for the ITSP to know that you are alive and kicking and more importantly, where to send your incoming calls. It's just like registering your name with your home address so that your bills will come to the right place.

In most cases, ITSP does not statically configure your CUBE's IP Address in their systems to send you the SIP traffic. That's what registration is for, to dynamically manage the location of each customer's DID.

This is obviously a great advantage for the ITSP, but we can find it handy as well, as you'll notice in the troubleshooting section.

Enough said, let's get to work.

Parameters required:

  • Username
  • Password
  • Registrar server IP/FQDN
  • Realm (domain)

Do note that these are the parameters required for registration alone. For a successful cut-off, more information is needed. You can find the full list here.

Command syntax:

sip-ua
 registrar [dns:/ipv4:/ipv6:] registrar-server-address
 credentials username username password [0/7] password realm realm

For example:

  • Username: ucpros
  • Password: 123456
  • Registrar server IP/FQDN: SIP.ucpros.net
  • Realm: ucpros.net

sip-ua
  credentials username ucpros password 0 123456 realm ucpros.net
  registrar dns:SIP.ucpros.net


Verify and troubleshoot

The first step would be making sure we are not shooting blanks!
Easiest method to verify that we are indeed registered to our ITSP is running:

CUBE#show sip-ua register status
Line                             peer       expires(sec) reg survival P-Associ-URI
================================ ========== ============ === ======== ============
ucpros                           -1         56           yes normal
CUBE#


If our first attempt was unlucky we would need to understand why.
Run both of the command below to see CUBE registration attempts:

Debug ccsip messages
Debug ccsip non-call

Watch the response code from ITSP to understand the reason for the failure. It should put you back on the right track.

Remember me mentioning in the beginning that dynamic registration to ITSP can help us with our troubleshooting? We'll, I wasn't lying!

Dynamic Registration means that you can actually register to your ITSP from every device who has the right credentials. Although not the most uplifting thought security wise, it means that if everything you try fails, try and register a softphone with the ITSP using the same credentials. The advantage of it is, that usually these softphones only require the most basic info like username, password and domain. The softphone will then automatically apply this info into the SIP messages.

Personally I use MicroSIP but there are many other options.

If you manage to register with your softphone, it means that the ITSP is at least doing something right, so open your Wireshark and compare the SIP messages from CUBE registration attempts with the ones generated by your softphone. Watch the differences in the SIP headers to understand what went wrong.

Using a simple softphone is also great for troubleshooting a lot of other CUBE problems. Whenever you reach a dead end, use it to compare CUBEs behavior with another device.

 
CUBE Authentication


As opposed to registration, authentication is actually a method that ITSP uses to verify your identity.
Essentially, it uses authentication to decide whether we are allowed to make this call.
The role of authentication, from ITSP's point of view, is to allow you to make outgoing calls. Without it, every call attempt would be accepted and that's, well.. unacceptable!

In most cases, authentication should be pretty straight forward, if you pay attention to details that is (clue: skip to the troubleshooting section if you can't bear the suspense)

Parameters required:

  • Username
  • Password
  • Realm (domain)

Command syntax:

sip-ua
 authentication username username password [0/7] password realm realm

For example:

  • Username: ucpros
  • Password: 123456
  • Realm: ucpros.net

sip-ua
  authentication username ucpros password 0 123456 realm ucpros.net

 
Verify and troubleshoot

Configuring authentication seems simple enough, but whenever it poses an issue or outgoing calls are failing, open your eyes for the following common pitfalls.

Now, let's get to business and turn the debug ccsip messages on!

This is what you would usually see: (showing only communication between CUBE and ITSP to simplify the output)

Following is an Invite message sent from CUBE to ITSP.

Watch the from field. The syntax should contain either your username or a number out of your allocated DID range! Anything other than that and your call won't go through.

Do pay attention to the number of digits as different ITSPs might have different requirements for the calling number. What some of us are missing, is that the from field is actually one of the authentication parameters.

Oct 23 12:15:13.648: //44/570577000000/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:403454@iptel.org:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.20:5060;branch=z9hG4bK3AD75
Remote-Party-ID: "ucpros" <sip:100@192.168.1.20>;party=calling;screen=yes;privacy=off
From: "ucpros" <sip:ucpros@ucpros.net>;tag=345CA8-1182
To: <sip:403454@iptel.org>
Date: Sun, 23 Oct 2016 12:15:13 GMT
Call-ID: 2F3B7D9F-985111E6-8008865A-F6ED7E07@192.168.1.20
Supported: timer,resource-priority,replaces,sdp-anat
Min-SE:  1800
Cisco-Guid: 1459975936-0000065536-0000000001-0167880896
User-Agent: Cisco-SIPGateway/IOS-15.5.3.S2
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Timestamp: 1477224913
Contact: <sip:100@192.168.1.20:5060>
Call-Info: <sip:192.168.1.20:5060>;method="NOTIFY;Event=telephone-event;Duration=2000"
Expires: 180
Allow-Events: telephone-event
Max-Forwards: 68
Session-Expires:  1800
Content-Length: 0

Oct 23 12:15:13.759: //44/570577000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.1.20:5060;branch=z9hG4bK3AD75;received=87.71.31.219
From: "ucpros" <sip:ucpros@ucpros.net>;tag=345CA8-1182
To: <sip:403454@iptel.org>
Call-ID: 2F3B7D9F-985111E6-8008865A-F6ED7E07@192.168.1.20
CSeq: 101 INVITE
Content-Length: 0

Next, we can see a challenged response from ITSP

Pay attention to the Digest Realm field. That is the realm you should configure in your Authentication command under sip-ua

Oct 23 12:15:13.766: //44/570577000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP 192.168.1.20:5060;branch=z9hG4bK3AD75;received=87.71.31.219
From: "ucpros" <sip:ucpros@ucpros.net>;tag=345CA8-1182
To: <sip:403454@iptel.org>;tag=78A48057-580CA9D1000A93BC-CAD9A700
Call-ID: 2F3B7D9F-985111E6-8008865A-F6ED7E07@192.168.1.20
CSeq: 101 INVITE
Proxy-Authenticate: Digest realm="ucpros.net", nonce="WAysJlgMqc7UL30vd9AwPJsK+KVESIx/"
Server: ser (3.3.0-pre1 (i386/linux))
Warning: 392 192.168.0.85:5060 "Noisy feedback tells: pid=1812 req_src_ip=192.168.0.155 req_src_port=5060 in_uri=sip:403454@iptel.org:5060 out_uri=sip:403454@iptel.org:5060 via_cnt==1"
Content-Length: 0

Oct 23 12:15:13.767: //44/570577000000/SIP/Msg/ccsipDisplayMsg:
Sent:
ACK sip:403454@iptel.org:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.20:5060;branch=z9hG4bK3AD75
From: "ucpros" <sip:100@ucpros.net>;tag=345CA8-1182
To: <sip:403454@iptel.org>;tag=78A48057-580CA9D1000A93BC-CAD9A700
Date: Sun, 23 Oct 2016 12:15:13 GMT
Call-ID: 2F3B7D9F-985111E6-8008865A-F6ED7E07@192.168.1.20
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: telephone-event
Content-Length: 0


Here CUBE sends another invite, this time with the Authentication details:

Oct 23 12:15:13.767: //44/570577000000/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:403454@iptel.org:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.20:5060;branch=z9hG4bK3B6A8
Remote-Party-ID: "ucpros" <sip:100@192.168.1.20>;party=calling;screen=yes;privacy=off
From: "ucpros" <sip:ucpros@ucpros.net>;tag=345CA8-1182
To: <sip:403454@iptel.org>
Date: Sun, 23 Oct 2016 12:15:13 GMT
Call-ID: 2F3B7D9F-985111E6-8008865A-F6ED7E07@192.168.1.20
Supported: timer,resource-priority,replaces,sdp-anat
Min-SE: 1800
Cisco-Guid: 1459975936-0000065536-0000000001-0167880896
User-Agent: Cisco-SIPGateway/IOS-15.5.3.S2
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 102 INVITE
Timestamp: 1477224913
Contact: <sip:100@192.168.1.20:5060>
Call-Info: <sip:192.168.1.20:5060>;method="NOTIFY;Event=telephone-event;Duration=2000"
Expires: 180
Allow-Events: telephone-event
Proxy-Authorization: Digest username="ucpros",realm="ucpros.net",uri="sip:403454@iptel.org:5060",response="sad234324fsd234sadAWD12315",nonce="WAysJlgMqc7UL30vd9AwPJsK+KVESIx/",algorithm=md5
Max-Forwards: 68
Session-Expires: 1800
Content-Length: 0

Oct 23 12:15:13.875: //44/570577000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.1.20:5060;branch=z9hG4bK3B6A8;received=87.71.31.219
From: "ucpros" <sip:ucpros@ucpros.net>;tag=345CA8-1182
To: <sip:403454@iptel.org>
Call-ID: 2F3B7D9F-985111E6-8008865A-F6ED7E07@192.168.1.20
CSeq: 102 INVITE
Content-Length: 0


Wrap-Up


True, setting up CUBE registration and authentication with ITSP can be a frustrating task, but when you understand the concepts and the minimum required, to allow incoming and outgoing calls you are halfway there :)

Our spiritual father, Alexander Graham Bell said:

Before anything else, preparation is the key to success


Bell is here to remind us, that in order to make it look easy, we have to do our homework and get the max info we can from ITSP before D-day. We must show up to the cut-off, as prepared as possible.

If you encounter difficulties, follow the troubleshooting steps, they will point you in the right direction.

Don't be afraid to use a softphone if troubleshooting hits a dead end, It's like getting a second opinion. It will also help you determine, whether the problem lies with your configuration or the ITSP's.

Understand the concepts described here, and this post will be a long forgotten memory.

If you need help with other aspects of CUBE, I've written two-part, step-by-step post that covers the main concepts. You can also download the CUBE Config Utility to help you create clean, professional, resource sensitive and best practice driven CUBE configuration.

Best of luck!

Pasha.

4337 Views
24 Comments

Problem Description

When CUIC Agent Report is run, the agent report fails with the error that contains the following line:

Overflow occurred on a datetime or interval operation

 Complete Error will be similar to as as follows:

com.cisco.ccbu.cuic.businesslogic.datasource.CuicDbException: DbException: 
CuicDataSourceServiceManagerImpl.getDataSet() { Nested SQLException;
SQLState: IX000 Vendor code: -1265 Message: Overflow occurred on a
datetime or interval operation. } at
com.cisco.ccbu.cuic.businesslogic.datasource.CuicDataSourceServiceManagerImpl.getDataSetBuilder(CuicDataSourceServiceManagerImpl.java:952)
at
com.cisco.ccbu.cuic.businesslogic.engine.CuicReportEngineWorker.executeQueryUsingDatasetBuilder(CuicReportEngineWorker.java:80)
at
com.cisco.ccbu.cuic.businesslogic.engine.CuicReportEngineWorker.runReport(CuicReportEngineWorker.java:37)
at
com.cisco.ccbu.cuic.businesslogic.enginebase.Worker.run(Worker.java:329)
at
com.cisco.ccbu.infra.threads.InstrumentedRunnable.run(InstrumentedRunnable.java:92)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:724) at
com.cisco.ccbu.infra.threads.ThreadPoolThread.run(ThreadPoolThread.java:164)
Caused by: java.sql.SQLException: Overflow occurred on a datetime or
interval operation. at
com.informix.util.IfxErrMsg.getSQLException(IfxErrMsg.java:413) at
com.informix.jdbc.IfxSqli.a(IfxSqli.java:3647) at
com.informix.jdbc.IfxSqli.E(IfxSqli.java:3974) at
com.informix.jdbc.IfxSqli.dispatchMsg(IfxSqli.java:2695) at
com.informix.jdbc.IfxSqli.receiveMessage(IfxSqli.java:2611) at
com.informix.jdbc.IfxSqli.a(IfxSqli.java:1830) at
com.informix.jdbc.IfxSqli.executeStatementQuery(IfxSqli.java:1768) at
com.informix.jdbc.IfxSqli.executeStatementQuery(IfxSqli.java:1699) at
com.informix.jdbc.IfxResultSet.a(IfxResultSet.java:210) at
com.informix.jdbc.IfxStatement.executeQueryImpl(IfxStatement.java:1237) at
com.informix.jdbc.IfxPreparedStatement.executeQuery(IfxPreparedStatement.java:401)
at
com.informix.jdbc.IfxCallableStatement.executeQuery(IfxCallableStatement.java:241)
at
com.mchange.v2.c3p0.impl.NewProxyCallableStatement.executeQuery(NewProxyCallableStatement.java:2131)
at
com.cisco.ccbu.cuic.businesslogic.datasource.CuicDataSourceServiceManagerImpl.executeAndLoadDataset(CuicDataSourceServiceManagerImpl.java:1072)
at
com.cisco.ccbu.cuic.businesslogic.datasource.CuicDataSourceServiceManagerImpl.getDataSetBuilder(CuicDataSourceServiceManagerImpl.java:938)
... 8 more Caused by: java.sql.SQLException at
com.informix.util.IfxErrMsg.getSQLException(IfxErrMsg.java:413) at
com.informix.jdbc.IfxSqli.E(IfxSqli.java:3979) ... 20 more

So far, the issue has been reported on UCCX Versions 11.X, 10.X, 9.X, 8.X and can potentially impact HRC reporting as well.

The issue is filed as a defect already:

CSCvb27878   UCCX/CUIC: Overflow occurred on a datetime or interval operation

Since the defect is newly filed, it may not be visible externally at the moment. However, the fix for the defect is already available and can be installed on the affected UCCX servers without requiring any downtime.

The fix for the defect involves installing "ciscouccx.ReportFix.10.cop.sgn" file on both the UCCX Nodes. Installation of this file does not require any service restart and hence can be performed without requiring any reboot.

This should resolve your CUIC reporting issue mentioned above.

Frequently Asked Questions

Q. I have a UCCX HA environment. Do I need to install the cop file on both the nodes? 

Ans: Yes, you need to install the cop file on both the nodes.

Q. Does the installation of this cop file require any downtime or does it have any impact on service?

Ans: The cop file installation does not require any restart of service or reboot of server. Thus, it does not require any downtime and does not have any impact on service.

Q. Are there different cop files for different UCCX versions?

Ans: No, the same cop file work for any UCCX version equal to or higher than 8.x

Q. Can this cop file be installed on ES or SU version of UCCX?

Ans: Yes, it can be installed on ES or SU versions too.

Q. Can I install this cop file from GUI?

Ans: No. This cop file installation is only supported when done through the UCCX command line interface (CLI).

Q. Is there any UCCX Version available that has the fix for the defect CSCvb27878?

Ans: There is no UCCX version available at the moment that has the fix for the defect: CSCvb27878

Hope this helps!

Regards,

Saurabh