6/4/2020 https://172.23.117.18/serviceassurance/tview/print/575?

level=20&system=All+Systems&details=true

2020-04-06 23:13:23.339 - Added association marker for trail 144125970030331496 (only lower 32 bits of
trail ID shown)

Integrated Session Controller SSCC-SBC

956903035

Added association marker for trail 144125970030331496

Variable length data field 0 as hex =

6363635333323331333233303630346f626447684566437141626a404d42434c5259312e4d53532e434c41524f2e434c
Variable length data field 0 as string = [email protected]
(only lower 32 bits of trail ID shown)

2020-04-06 23:13:23.339 - Incoming SIP message received : INVITE (SDP) [email protected]

>[email protected] [email protected]

Integrated Session Controller SSCC-SBC

956903035

Incoming SIP message received from 172.23.216.5:64515 to 172.16.35.74:5060 on service network 1:

Summary: INVITE (SDP) [email protected]>[email protected] [email protected]

INVITE sip:[email protected];user=phone SIP/2.0
From: <sip:[email protected];user=phone>;tag=14011976445341
To: <sip:[email protected];user=phone>
Max-Forwards: 70
Via: SIP/2.0/TCP MBCLRY1.MSS.CLARO.CL:5060;branch=z9hG4bK00072088140142692245
Record-Route: <sip:MBCLRY1.MSS.CLARO.CL:5060;transport=UDP;lr>
Call-ID: [email protected]
CSeq: 541260929 INVITE
Accept: application/sdp
Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,PRACK,UPDATE
Supported: 100rel,precondition
Content-Type: application/sdp
Contact: <sip:MBCLRY1.MSS.CLARO.CL:5060;transport=UDP>
Content-Length: 839

v=0
o=- 9369440 9369440 IN IP4 MBCLRY1.MSS.CLARO.CL
s=-
c=IN IP4 172.23.45.35
t=0 0
a=sendrecv
m=audio 40106 RTP/AVP 96 97 98 8 99 18 100 101
c=IN IP4 172.23.45.35
b=RR:1125
b=RS:375
a=curr:qos local none
a=curr:qos remote none
a=des:qos mandatory local sendrecv
a=des:qos optional remote sendrecv
a=rtpmap:96 AMR-WB/16000
a=fmtp:96 mode-set=0,1,2;mode-change-period=2;mode-change-capability=2;mode-change-neighbor=1;max-
red=0
a=rtpmap:97 AMR/8000
a=fmtp:97 mode-set=0,2,4,7;mode-change-period=2;mode-change-capability=2;mode-change-neighbor=1;max-
red=0
a=rtpmap:98 AMR/8000
a=fmtp:98 mode-set=7;max-red=0
a=rtpmap:8 PCMA/8000
a=rtpmap:99 GSM-EFR/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=yes
a=rtpmap:100 telephone-event/16000
a=fmtp:100 0-15
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=maxptime:40

2020-04-06 23:13:23.339 - MMF editing was applied to an inbound message

Integrated Session Controller SSCC-SBC

956903035

https://172.23.117.18/serviceassurance/tview/print/575?level=20&system=All+Systems&details=true 1/29
6/4/2020 https://172.23.117.18/serviceassurance/tview/print/575?level=20&system=All+Systems&details=true
MMF editing has been applied to an inbound message. Logged below are the
edit sequence that was applied and the message after any edits were
made.
If you require more detailed SAS diagnostics showing the full set of
edit steps, you can enable them by configuring a marker-diags filter.
See the Perimeta Operations & Maintenance Guide for more information.
Edit Sequence: Hdr_Ctct_Rmt_Addr,deleteRecordRoute
Edit Sequence Truncated?: 0
Message after editing:
INVITE sip:[email protected];user=phone SIP/2.0
From: <sip:[email protected];user=phone>;tag=14011976445341
To: <sip:[email protected];user=phone>
Max-Forwards: 70
Via: SIP/2.0/TCP MBCLRY1.MSS.CLARO.CL:5060;branch=z9hG4bK00072088140142692245
Call-ID: [email protected]
CSeq: 541260929 INVITE
Accept: application/sdp
Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,PRACK,UPDATE
Supported: 100rel,precondition
Content-Type: application/sdp
Contact: <sip:172.23.216.5:5060;transport=udp>
Content-Length: 839

v=0
o=- 9369440 9369440 IN IP4 MBCLRY1.MSS.CLARO.CL
s=-
c=IN IP4 172.23.45.35
t=0 0
a=sendrecv
m=audio 40106 RTP/AVP 96 97 98 8 99 18 100 101
c=IN IP4 172.23.45.35
b=RR:1125
b=RS:375
a=curr:qos local none
a=curr:qos remote none
a=des:qos mandatory local sendrecv
a=des:qos optional remote sendrecv
a=rtpmap:96 AMR-WB/16000
a=fmtp:96 mode-set=0,1,2;mode-change-period=2;mode-change-capability=2;mode-change-neighbor=1;max-
red=0
a=rtpmap:97 AMR/8000
a=fmtp:97 mode-set=0,2,4,7;mode-change-period=2;mode-change-capability=2;mode-change-neighbor=1;max-
red=0
a=rtpmap:98 AMR/8000
a=fmtp:98 mode-set=7;max-red=0
a=rtpmap:8 PCMA/8000
a=rtpmap:99 GSM-EFR/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=yes
a=rtpmap:100 telephone-event/16000
a=fmtp:100 0-15
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=maxptime:40

2020-04-06 23:13:23.339 - Adjacency receives inbound message

Integrated Session Controller SSCC-SBC

956903035

Adjacency receives inbound message

Inbound adjacency: MBCLRY1.

Inbound interop profile: None.

2020-04-06 23:13:23.339 - Caller [email protected] is calling [email protected]

Integrated Session Controller SSCC-SBC

956903035

Incoming call attempt.

Caller: [email protected].
Callee: [email protected].
Inbound adjacency: MBCLRY1.

https://172.23.117.18/serviceassurance/tview/print/575?level=20&system=All+Systems&details=true 2/29
6/4/2020 https://172.23.117.18/serviceassurance/tview/print/575?level=20&system=All+Systems&details=true
Inbound interop profile: None.
Using TLS certificate: None.

2020-04-06 23:13:23.339 - Signaling has determined internal settings for SDP

Integrated Session Controller SSCC-SBC

956903035

Signaling has determined the following internal settings for SDP:

Offer-answer message type: 1

Offerer SDP is superfluous: 0
Requesting repeat of answer SDP: 0
SRTP fallback supported: 3
Check SIP session refresh: 0
SDP final answer: 0

2020-04-06 23:13:23.339 - Session Controller has received a SIP INVITE request

Integrated Session Controller SSCC-SBC

956903035

Session Controller has received a SIP INVITE request. The INVITE may
create a new call or renegotiate an existing call.

2020-04-06 23:13:23.339 - Adjacency sends outbound message

Integrated Session Controller SSCC-SBC

956903035

Adjacency sends outbound message

Outbound adjacency: MBCLRY1.

Outbound interop profile: None.

2020-04-06 23:13:23.339 - MMF editing was applied to an outbound message

Integrated Session Controller SSCC-SBC

956903035

MMF editing has been applied to an outbound message. Logged below are
the edit sequence that was applied and the message before any edits were
made.
If you require more detailed SAS diagnostics showing the full set of
edit steps, you can enable them by configuring a marker-diags filter.
See the Perimeta Operations & Maintenance Guide for more information.
Edit Sequence: deleteRPID,Copiar-From-a-RPID
Edit Sequence Truncated?: 0
Message before editing:
SIP/2.0 100 Trying
Call-ID: [email protected]
CSeq: 541260929 INVITE
From: <sip:[email protected];user=phone>;tag=14011976445341
To: <sip:[email protected];user=phone>;tag=sip+4+50f30005+f2fa908a
Via: SIP/2.0/TCP MBCLRY1.MSS.CLARO.CL:5060;received=172.23.216.5;branch=z9hG4bK00072088140142692245
Server: SIP/2.0
Content-Length: 0

2020-04-06 23:13:23.339 - Added association marker for trail 144125970030331496 (only lower 32 bits of
trail ID shown)

Integrated Session Controller SSCC-SBC

956903035

Added association marker for trail 144125970030331496

Variable length data field 0 as hex = 313434313235393730303330333331343936

Variable length data field 0 as string = 144125970030331496
(only lower 32 bits of trail ID shown)

2020-04-06 23:13:23.339 - Outgoing SIP message sent : 100 Trying From: <sip:[email protected]
To: <sip:[email protected]

Integrated Session Controller SSCC-SBC

956903035

Outgoing SIP message sent to 172.23.216.5:5060 from 172.16.35.74:5060 on service network 1:

https://172.23.117.18/serviceassurance/tview/print/575?level=20&system=All+Systems&details=true 3/29
6/4/2020 https://172.23.117.18/serviceassurance/tview/print/575?level=20&system=All+Systems&details=true
Summary: 100 Trying From: <sip:[email protected] To: <sip:[email protected]
SIP/2.0 100 Trying
Call-ID: [email protected]
CSeq: 541260929 INVITE
From: <sip:[email protected];user=phone>;tag=14011976445341
To: <sip:[email protected];user=phone>;tag=sip+4+50f30005+f2fa908a
Via: SIP/2.0/TCP MBCLRY1.MSS.CLARO.CL:5060;received=172.23.216.5;branch=z9hG4bK00072088140142692245
Server: SIP/2.0
Content-Length: 0
Remote-Party-ID: <sip:[email protected];user=phone>;privacy=off;screen=yes

2020-04-06 23:13:23.339 - Starting Number Analysis.

Integrated Session Controller SSCC-SBC

956903035

Starting Number Analysis.

Caller address type: Dialed digits.

Caller address: 956903035.
Callee address type: Dialed digits.
Callee address: 008887802.
Call policy set index: 2.

2020-04-06 23:13:23.339 - Number Analysis succeeds.

Integrated Session Controller SSCC-SBC

956903035

Number Analysis succeeds.

Caller address type: Dialed digits.

Caller address: 956903035.
Callee address type: Dialed digits.
Callee address: 008887802.

2020-04-06 23:13:23.340 - Starting Routing.

Integrated Session Controller SSCC-SBC

956903035

Starting Routing.

Caller address type: Dialed digits.

Caller address: 956903035.
Callee address type: Dialed digits.
Callee address: 008887802.
Call policy set index: 2.

2020-04-06 23:13:23.340 - Routing succeeds.

Integrated Session Controller SSCC-SBC

956903035

Routing succeeds.

Destination adjacency: Mobile_Carrius2

Routing history:
(Table: SourceAdjacency; entry: 7; action: lookup)
(Table: NumberValidationMBCLRY1; entry: 17; action: lookup)
(Table: Carrius_Movil_bl; entry: 1; action: complete routing)

2020-04-06 23:13:23.340 - Capacity Control permitted an in-call or out-of-dialog message

Integrated Session Controller SSCC-SBC

956903035

Capacity Control permitted an in-call or out-of-dialog message.

2020-04-06 23:13:23.340 - Privacy settings for a call were determined

Integrated Session Controller SSCC-SBC

956903035

Privacy settings for a call were determined.

https://172.23.117.18/serviceassurance/tview/print/575?level=20&system=All+Systems&details=true 4/29
6/4/2020 https://172.23.117.18/serviceassurance/tview/print/575?level=20&system=All+Systems&details=true
Call index = 52411606
Calling number = 956903035
Called number = 008887802
Legacy caller privacy enabled = 0
Caller privacy service = Boundary
Caller privacy request editing = Passthrough
Caller SIP privacy token stripping = none
Caller SIP privacy token insertion = none
Legacy callee privacy enabled = 0
Callee privacy service = Boundary
Callee privacy request editing = Passthrough
Callee SIP privacy token stripping = none
Callee SIP privacy token insertion = none

2020-04-06 23:13:23.340 - A codec has been removed from an offer due to codec restriction policy

Integrated Session Controller SSCC-SBC

956903035

A codec has been removed from an offer due to codec restriction policy.
This may be a problem if all the codecs offered for a media stream are
disallowed. Check the codec restriction profile.
Payload index: 96
Codec restriction list: access
Path index: 0

2020-04-06 23:13:23.340 - A codec has been removed from an offer due to codec restriction policy

Integrated Session Controller SSCC-SBC

956903035

A codec has been removed from an offer due to codec restriction policy.
This may be a problem if all the codecs offered for a media stream are
disallowed. Check the codec restriction profile.
Payload index: 97
Codec restriction list: access
Path index: 0

2020-04-06 23:13:23.340 - A codec has been removed from an offer due to codec restriction policy

Integrated Session Controller SSCC-SBC

956903035

A codec has been removed from an offer due to codec restriction policy.
This may be a problem if all the codecs offered for a media stream are
disallowed. Check the codec restriction profile.
Payload index: 98
Codec restriction list: access
Path index: 0

2020-04-06 23:13:23.340 - A codec has been removed from an offer due to codec restriction policy

Integrated Session Controller SSCC-SBC

956903035

A codec has been removed from an offer due to codec restriction policy.
This may be a problem if all the codecs offered for a media stream are
disallowed. Check the codec restriction profile.
Payload index: 99
Codec restriction list: access
Path index: 0

2020-04-06 23:13:23.340 - A codec has been removed from an offer due to codec restriction policy

Integrated Session Controller SSCC-SBC

956903035

A codec has been removed from an offer due to codec restriction policy.
This may be a problem if all the codecs offered for a media stream are
disallowed. Check the codec restriction profile.
Payload index: 18
Codec restriction list: access
Path index: 0

2020-04-06 23:13:23.340 - The Session Controller is locating a suitable Media Gateway

https://172.23.117.18/serviceassurance/tview/print/575?level=20&system=All+Systems&details=true 5/29
6/4/2020 https://172.23.117.18/serviceassurance/tview/print/575?level=20&system=All+Systems&details=true
Integrated Session Controller SSCC-SBC
956903035

The Session Controller is locating a suitable Media Gateway.

Required Location = 4294967295
Search type = Location search
Required capabilities = None

2020-04-06 23:13:23.340 - A media gateway has been selected in a call

Integrated Session Controller SSCC-SBC

956903035

A media gateway has been selected for this call.

Current usage: 0%
Capabilities =
Addressing: IPv4 A, IPv4 B, IPv6 A, IPv6 B
SRTP: Passthrough, A, B
DTMF: DTMFCTRL, Dual, DTMF transrate
Miscellaneous: Generic Streams, Media Capture

Extra engineering Information:

Role: 0 (role flags: 5)
MG handle = 5

2020-04-06 23:13:23.340 - GCI message sent

Integrated Session Controller SSCC-SBC

956903035

Sending gate allocation request (rc=0x00000000):

Gate id:0, flowpair_id=0x0000C001, side A flow_id=0, side B flow_id=0

2020-04-06 23:13:23.340 - Gate allocate request received

Integrated Session Controller SSCC-SBC

956903035

<< Gate allocate req BillingID (sideA)

5E8BEFD3 20202020 20202030 302B3034 30303030 063F7947 BillingID (sideB)
5E8BEFD3 20202020 20202030 302B3034 30303030 063F7948

2020-04-06 23:13:23.340 - Flow allocate request sent

Integrated Session Controller SSCC-SBC

956903035

<< Flow allocate req sent FlowPairID (GCI) 49153 Correlator 898000

2020-04-06 23:13:23.340 - Media has been allocated for a call

Integrated Session Controller SSCC-SBC

956903035

Media has been allocated for a call.

Media stream ID: 49153

Media correlator: 898000
Bandwidth flow A: 12000
Bandwidth flow B: 12000

2020-04-06 23:13:23.340 - Gate 52408987 is being allocated.

Integrated Session Controller SSCC-SBC

956903035

A gate is being allocated.

Gate ID: 52408987.

Media stream identifiers:
Media stream ID 1: 46032

2020-04-06 23:13:23.340 - Gate allocate response sent

Integrated Session Controller SSCC-SBC

956903035

https://172.23.117.18/serviceassurance/tview/print/575?level=20&system=All+Systems&details=true 6/29
6/4/2020 https://172.23.117.18/serviceassurance/tview/print/575?level=20&system=All+Systems&details=true
>> Gate allocate rsp (0) BillingID (sideA)
5E8BEFD3 20202020 20202030 302B3034 30303030 063F7947 BillingID (sideB)
5E8BEFD3 20202020 20202030 302B3034 30303030 063F7948

2020-04-06 23:13:23.340 - GCI message received

Integrated Session Controller SSCC-SBC

956903035

Receiving gate allocation response (rc=0x00000000):

Gate id:52408987, flowpair_id=0x0000C001, side A flow_id=898000, side B flow_id=898001

2020-04-06 23:13:23.340 - VQM statistics rewriting is disabled for this call

Integrated Session Controller SSCC-SBC

956903035

VQM statistics rewriting is disabled for this call. To enable it

allow VQM rewriting on the adjacency. The call continues and
VQM statistics are forwarded but the collector of VQM statistics may
not be able to be correlate reports with the call.
Adjacency name: Mobile_Carrius2
Incoming call-ID: [email protected]

2020-04-06 23:13:23.340 - The Called-Party-ID has been sent in the Request-URI

Integrated Session Controller SSCC-SBC

956903035

The Called-Party-ID for an outbound SIP request is sent in the

Request-URI.
Called-Party-ID: 008887802

2020-04-06 23:13:23.340 - A contact URI parameter will not be passed through because it would affect call
flow

Integrated Session Controller SSCC-SBC

956903035

A parameter will not be passed through because it would affect call

flow.
Parameter: transport=udp

2020-04-06 23:13:23.340 - Adjacency sends outbound message

Integrated Session Controller SSCC-SBC

956903035

Adjacency sends outbound message

Outbound adjacency: Mobile_Carrius2.

Outbound interop profile: Peer.

2020-04-06 23:13:23.340 - Sending outgoing SIP call setup request

Integrated Session Controller SSCC-SBC

956903035

Sending outgoing SIP call setup request

Outbound adjacency: Mobile_Carrius2.

Outbound interop profile: Peer.
Using TLS certificate: None.

2020-04-06 23:13:23.340 - Added association marker for trail 144125970030331496 (only lower 32 bits of
trail ID shown)

Integrated Session Controller SSCC-SBC

956903035

Added association marker for trail 144125970030331496

Variable length data field 0 as hex =

6438386434323965386339303965626235393937306165323436616665393162403137322e31362e33352e3734
Variable length data field 0 as string = [email protected]
(only lower 32 bits of trail ID shown)

https://172.23.117.18/serviceassurance/tview/print/575?level=20&system=All+Systems&details=true 7/29
6/4/2020 https://172.23.117.18/serviceassurance/tview/print/575?level=20&system=All+Systems&details=true
2020-04-06 23:13:23.341 - MMF editing was applied to an outbound message

Integrated Session Controller SSCC-SBC

956903035

MMF editing has been applied to an outbound message. Logged below are
the edit sequence that was applied and the message before any edits were
made.
If you require more detailed SAS diagnostics showing the full set of
edit steps, you can enable them by configuring a marker-diags filter.
See the Perimeta Operations & Maintenance Guide for more information.
Edit Sequence: RemoveT38
Edit Sequence Truncated?: 0
Message before editing:
INVITE sip:[email protected]:5060;user=phone SIP/2.0
From: <sip:[email protected]:5060>;tag=172.16.35.74+1+8f3897d6+7bccedd9
To: <sip:[email protected]:5060;user=phone>
CSeq: 541260929 INVITE
Expires: 180
Content-Length: 424
Call-Info: <sip:172.16.35.74:5060>;method="NOTIFY;Event=telephone-event;Duration=2000"
Supported: precondition, 100rel
Contact: <sip:[email protected]:5060>
Content-Type: application/sdp
Max-Forwards: 69
Call-ID: [email protected]
Accept: application/sdp, application/dtmf-relay
Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,PRACK,UPDATE, INFO

v=0
o=- 92595370048708 92595370048708 IN IP4 172.16.35.106
s=-
c=IN IP4 172.16.35.106
t=0 0
a=sendrecv
m=audio 16904 RTP/AVP 8 100 101
b=RR:1125
b=RS:375
a=rtpmap:8 PCMA/8000
a=rtpmap:100 telephone-event/16000
a=rtpmap:101 telephone-event/8000
a=curr:qos local none
a=curr:qos remote none
a=des:qos mandatory local sendrecv
a=des:qos optional remote sendrecv
a=fmtp:100 0-15
a=fmtp:101 0-15
a=maxptime:40

2020-04-06 23:13:23.341 - Outgoing SIP message sent : INVITE (SDP) [email protected]:5060-

>[email protected]:5060

Integrated Session Controller SSCC-SBC

956903035

Outgoing SIP message sent to 172.23.119.153:5060 from 172.16.35.74:5060 on service network 1:

Summary: INVITE (SDP) [email protected]:5060->[email protected]:5060

INVITE sip:[email protected]:5060;user=phone SIP/2.0
Via: SIP/2.0/UDP 172.16.35.74:5060;branch=z9hG4bK+033310f46d2a5045105ff003161cd95f1+sip+1+a6519c10
From: <sip:[email protected]:5060>;tag=172.16.35.74+1+8f3897d6+7bccedd9
To: <sip:[email protected]:5060;user=phone>
CSeq: 541260929 INVITE
Expires: 180
Content-Length: 424
Call-Info: <sip:172.16.35.74:5060>;method="NOTIFY;Event=telephone-event;Duration=2000"
Supported: precondition, 100rel
Contact: <sip:[email protected]:5060>
Content-Type: application/sdp
Max-Forwards: 69
Call-ID: [email protected]
Accept: application/sdp, application/dtmf-relay
Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,PRACK,UPDATE, INFO

v=0

https://172.23.117.18/serviceassurance/tview/print/575?level=20&system=All+Systems&details=true 8/29
6/4/2020 https://172.23.117.18/serviceassurance/tview/print/575?level=20&system=All+Systems&details=true
o=- 92595370048708 92595370048708 IN IP4 172.16.35.106
s=-
c=IN IP4 172.16.35.106
t=0 0
a=sendrecv
m=audio 16904 RTP/AVP 8 100 101
b=RR:1125
b=RS:375
a=rtpmap:8 PCMA/8000
a=rtpmap:100 telephone-event/16000
a=rtpmap:101 telephone-event/8000
a=curr:qos local none
a=curr:qos remote none
a=des:qos mandatory local sendrecv
a=des:qos optional remote sendrecv
a=fmtp:100 0-15
a=fmtp:101 0-15
a=maxptime:40

2020-04-06 23:13:23.341 - Incoming SIP message received : INVITE (SDP) [email protected]:5060-

>[email protected]:5060

SB_SB_
956903035

Incoming SIP message received from none:

Summary: INVITE (SDP) [email protected]:5060->[email protected]:5060

INVITE sip:[email protected]:5060;user=phone SIP/2.0
Via: SIP/2.0/UDP 172.16.35.74:5060;branch=z9hG4bK+033310f46d2a5045105ff003161cd95f1+sip+1+a6519c10
From: <sip:[email protected]:5060>;tag=172.16.35.74+1+8f3897d6+7bccedd9
To: <sip:[email protected]:5060;user=phone>
CSeq: 541260929 INVITE
Expires: 180
Content-Length: 424
Call-Info: <sip:172.16.35.74:5060>;method="NOTIFY;Event=telephone-event;Duration=2000"
Supported: precondition, 100rel
Contact: <sip:[email protected]:5060>
Content-Type: application/sdp
Max-Forwards: 69
Call-ID: [email protected]
Accept: application/sdp, application/dtmf-relay
Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,PRACK,UPDATE, INFO

v=0
o=- 92595370048708 92595370048708 IN IP4 172.16.35.106
s=-
c=IN IP4 172.16.35.106
t=0 0
a=sendrecv
m=audio 16904 RTP/AVP 8 100 101
b=RR:1125
b=RS:375
a=rtpmap:8 PCMA/8000
a=rtpmap:100 telephone-event/16000
a=rtpmap:101 telephone-event/8000
a=curr:qos local none
a=curr:qos remote none
a=des:qos mandatory local sendrecv
a=des:qos optional remote sendrecv
a=fmtp:100 0-15
a=fmtp:101 0-15
a=maxptime:40

2020-04-06 23:13:23.341 - Outgoing SIP message sent : 100 Trying From: <sip:[email protected]:5060>
To: <sip:[email protected]:5060

SB_SB_
956903035

Outgoing SIP message sent to none

Summary: 100 Trying From: <sip:[email protected]:5060> To: <sip:[email protected]:5060

SIP/2.0 100 Trying
From: <sip:[email protected]:5060>;tag=172.16.35.74+1+8f3897d6+7bccedd9

https://172.23.117.18/serviceassurance/tview/print/575?level=20&system=All+Systems&details=true 9/29
6/4/2020 https://172.23.117.18/serviceassurance/tview/print/575?level=20&system=All+Systems&details=true
To: <sip:[email protected]:5060;user=phone>
Call-ID: [email protected]
CSeq: 541260929 INVITE
Via: SIP/2.0/UDP
172.16.35.74:5060;branch=z9hG4bK+033310f46d2a5045105ff003161cd95f1+sip+1+a6519c10;received=172.16.35.74
Content-Length: 0

2020-04-06 23:13:23.342 - Added association marker for trail 1575439302436 (only lower 32 bits of trail ID
shown)

SB_SB_

Added association marker for trail 1575439302436

Static length data field 0 = 1586097989

(only lower 32 bits of trail ID shown)

2020-04-06 23:13:23.342 - Call assigned to PROTAPP-CallManager with sid=1586097989

SB_SB_

Call assignment successful to PROTAPP-CallManager with session ID 1586097989

Call assignment request was successful.

2020-04-06 23:13:23.342 - 956903035 is calling 008887802.

SB_SB_
956903035

Incoming call from 956903035 to 008887802.

2020-04-06 23:13:23.342 - Added association marker for trail 1586059265632 (only lower 32 bits of trail ID
shown)

SB_SB_
956903035

Added association marker for trail 1586059265632

Variable length data field 0 as hex =

6438386434323965386339303965626235393937306165323436616665393162403137322e31362e33352e3734
Variable length data field 0 as string = [email protected]
(only lower 32 bits of trail ID shown)

2020-04-06 23:13:23.342 - Trails 1216333408 and 1586562664 associated due to an association marker at the
VPED_ASSOC_SCOPE_BRANCH scope (only lower 32 bits of trail IDs are shown).

SB_SB_
956903035

Trails 1216333408 and 1586562664 associated due to an association marker at the

VPED_ASSOC_SCOPE_BRANCH scope (only lower 32 bits of trail IDs are shown).

2020-04-06 23:13:23.343 - Incoming SIP message received : 100 Trying From:

<sip:[email protected]:5060> To: <sip:[email protected]:5060

Integrated Session Controller SSCC-SBC

956903035

Incoming SIP message received from 172.23.119.153:5060 to 172.16.35.74:5060 on service network 1:

Summary: 100 Trying From: <sip:[email protected]:5060> To: <sip:[email protected]:5060

SIP/2.0 100 Trying
From: <sip:[email protected]:5060>;tag=172.16.35.74+1+8f3897d6+7bccedd9
To: <sip:[email protected]:5060;user=phone>
Call-ID: [email protected]
CSeq: 541260929 INVITE
Via: SIP/2.0/UDP
172.16.35.74:5060;branch=z9hG4bK+033310f46d2a5045105ff003161cd95f1+sip+1+a6519c10;received=172.16.35.74
Content-Length: 0

2020-04-06 23:13:23.343 - A 100 Provisional Response was discarded

Integrated Session Controller SSCC-SBC

956903035

https://172.23.117.18/serviceassurance/tview/print/575?level=20&system=All+Systems&details=true 10/29
6/4/2020 https://172.23.117.18/serviceassurance/tview/print/575?level=20&system=All+Systems&details=true
A 100 Provisional Response was discarded
Handles
Call = 0
Dialog = 0
Transaction = 0
Response = 0
Correlators
Call =
00000000 00000000
Dialog =
00000000 00000000
Transaction =
00000000 00000000
Response =
00000000 00000000

2020-04-06 23:13:23.343 - Added association marker for trail 1586059265633 (only lower 32 bits of trail ID
shown)

SB_SB_

Added association marker for trail 1586059265633

Static length data field 0 = 1586097989

(only lower 32 bits of trail ID shown)

2020-04-06 23:13:23.343 - Trails 1216333409 and 3481272100 associated due to an association marker at the
VPED_ASSOC_SCOPE_BRANCH scope (only lower 32 bits of trail IDs are shown).

SB_SB_

Trails 1216333409 and 3481272100 associated due to an association marker at the

VPED_ASSOC_SCOPE_BRANCH scope (only lower 32 bits of trail IDs are shown).

2020-04-06 23:13:23.345 - Added association marker for trail 1577401351455 (only lower 32 bits of trail ID
shown)

SB_SB_

Added association marker for trail 1577401351455

Static length data field 0 = 1586097989

(only lower 32 bits of trail ID shown)

2020-04-06 23:13:23.345 - Trails 1148353823 and 3481272100 associated due to an association marker at the
VPED_ASSOC_SCOPE_BRANCH scope (only lower 32 bits of trail IDs are shown).

SB_SB_

Trails 1148353823 and 3481272100 associated due to an association marker at the

VPED_ASSOC_SCOPE_BRANCH scope (only lower 32 bits of trail IDs are shown).

2020-04-06 23:13:23.435 - Added association marker for trail 144125970030331496 (only lower 32 bits of
trail ID shown)

Integrated Session Controller SSCC-SBC

Added association marker for trail 144125970030331496

Variable length data field 0 as hex = 313434313235393730303330333331343936

Variable length data field 0 as string = 144125970030331496
(only lower 32 bits of trail ID shown)

2020-04-06 23:13:23.435 - Trails 1586562664 and 1586562664 associated due to an association marker at the
VPED_ASSOC_SCOPE_TRAIL_GROUP scope (only lower 32 bits of trail IDs are shown).

Integrated Session Controller SSCC-SBC

Trails 1586562664 and 1586562664 associated due to an association marker at the

VPED_ASSOC_SCOPE_TRAIL_GROUP scope (only lower 32 bits of trail IDs are shown).

2020-04-06 23:13:23.464 - MakeCallRequest from APIAPP-ClaroApp3 received.

SB_SB_

Service Broker received MakeCallRequest from APIAPP-ClaroApp3.

https://172.23.117.18/serviceassurance/tview/print/575?level=20&system=All+Systems&details=true 11/29
6/4/2020 https://172.23.117.18/serviceassurance/tview/print/575?level=20&system=All+Systems&details=true
API Service Invocation was received from the specified entity.

2020-04-06 23:13:23.465 - Route SIPREMOTENODE-SIPIVR2[VIPER-1-1466805] selected from ROUTELIST-181-

CExacta.

SB_SB_

Route SIPREMOTENODE-SIPIVR2[VIPER-1-1466805] selected from route list ROUTELIST-181-CExacta.

Call was successfully routed using the route list shown.

2020-04-06 23:13:23.511 - Added association marker for trail 1586059265637 (only lower 32 bits of trail ID
shown)

SB_SB_

Added association marker for trail 1586059265637

Static length data field 0 = 1586097989

(only lower 32 bits of trail ID shown)

2020-04-06 23:13:23.511 - Trails 1216333413 and 3481272100 associated due to an association marker at the
VPED_ASSOC_SCOPE_BRANCH scope (only lower 32 bits of trail IDs are shown).

SB_SB_

Trails 1216333413 and 3481272100 associated due to an association marker at the

VPED_ASSOC_SCOPE_BRANCH scope (only lower 32 bits of trail IDs are shown).

2020-04-06 23:13:23.512 - Outgoing SIP message sent : INVITE (SDP) [email protected]:5060-

>[email protected]:5060

SB_SB_

Outgoing SIP message sent to none

Summary: INVITE (SDP) [email protected]:5060->[email protected]:5060

INVITE sip:[email protected]:5060;transport=udp;user=phone SIP/2.0
To: <sip:[email protected]:5060;transport=udp;user=phone>
From: <sip:[email protected]:5060;transport=udp;user=phone>;tag=55573246313536414AADDF02
X-CIC-CallID: 21586097989
XDNIS: 0000000015
Content-Type: application/sdp
Content-Length: 216
Allow:
INVITE,ACK,OPTIONS,BYE,CANCEL,REGISTER,INFO,COMET,UPDATE,PRACK,REFER,SUBSCRIBE,NOTIFY,MESSAGE,PUBLISH
Supported: 100rel,diversion
Call-ID: 0210A1A0A681400000135A36@SIPAgent
Max-Forwards: 70
CSeq: 1 INVITE
Contact: <sip:[email protected]:5060>
Via: SIP/2.0/UDP
172.23.119.153:5060;branch=z9hG4bK4FA0C49D65CAC0ABEC40D9AF5D0F4FE9;rport;SIPAgent01.com

v=0
o=apptrigger 1348770 0 IN IP4 172.23.119.153
s=apptrigger-1348770
t=0 0
m=audio 4520 RTP/AVP 8 96
c=IN IP4 172.23.119.158
a=fmtp:96 0-15
a=ptime:20
a=rtpmap:8 PCMA/8000
a=rtpmap:96 telephone-event/8000

2020-04-06 23:13:23.533 - Incoming SIP message received : 200 OK (SDP) From:

<sip:[email protected]:5060 To: <sip:[email protected]:5060

SB_SB_

Incoming SIP message received from none:

Summary: 200 OK (SDP) From: <sip:[email protected]:5060 To:

<sip:[email protected]:5060
SIP/2.0 200 OK
From: <sip:[email protected]:5060;transport=udp;user=phone>;tag=55573246313536414AADDF02

https://172.23.117.18/serviceassurance/tview/print/575?level=20&system=All+Systems&details=true 12/29
6/4/2020 https://172.23.117.18/serviceassurance/tview/print/575?level=20&system=All+Systems&details=true
To: <sip:[email protected]:5060;user=phone>;tag=139bd990-837717ac-13c4-50022-238648-1e0c21b8-
238648
Call-ID: 0210A1A0A681400000135A36@SIPAgent
CSeq: 1 INVITE
Via: SIP/2.0/UDP
172.23.119.153:5060;rport=5060;branch=z9hG4bK4FA0C49D65CAC0ABEC40D9AF5D0F4FE9;SIPAgent01.com
Session-Expires: 1800;refresher=uas
Allow: INVITE, CANCEL, ACK, BYE, OPTIONS, INFO, REFER, NOTIFY, UPDATE
Contact: <sip:[email protected]>
Content-Type: application/sdp
Content-Length: 239

v=0
o=Intervoice_Media_Server 12421499 12421500 IN IP4 172.23.119.131
s=Intervoice_SIP_3PCC
c=IN IP4 172.23.119.131
t=0 0
m=audio 49458 RTP/AVP 8 96
a=rtpmap:8 PCMA/8000
a=ptime:20
a=rtpmap:96 telephone-event/8000
a=fmtp:96 0-15

2020-04-06 23:13:23.534 - Added association marker for trail 1586059265640 (only lower 32 bits of trail ID
shown)

SB_SB_

Added association marker for trail 1586059265640

Variable length data field 0 as hex =

303231304131413041363831343030303030313335413336405349504167656e74
Variable length data field 0 as string = 0210A1A0A681400000135A36@SIPAgent
(only lower 32 bits of trail ID shown)

2020-04-06 23:13:23.534 - Call answered by Unknown User

SB_SB_

Call answered by Unknown User

Call answer event was received by the call model.

2020-04-06 23:13:23.535 - ConnectAudioTwoWayRequest from APIAPP-ClaroApp3 received.

SB_SB_

Service Broker received ConnectAudioTwoWayRequest from APIAPP-ClaroApp3.

API Service Invocation was received from the specified entity.

2020-04-06 23:13:23.535 - CallAcceptedRequest from APIAPP-ClaroApp3 received.

SB_SB_

Service Broker received CallAcceptedRequest from APIAPP-ClaroApp3.

API Service Invocation was received from the specified entity.

2020-04-06 23:13:23.536 - Call answered by Unknown User

SB_SB_

Call answered by Unknown User

Call answer event was received by the call model.

2020-04-06 23:13:23.537 - Outgoing SIP message sent : 180 Ringing From: <sip:[email protected]:5060>
To: <sip:[email protected]:5060

SB_SB_

Outgoing SIP message sent to none

Summary: 180 Ringing From: <sip:[email protected]:5060> To: <sip:[email protected]:5060

SIP/2.0 180 Ringing
Allow:

https://172.23.117.18/serviceassurance/tview/print/575?level=20&system=All+Systems&details=true 13/29
6/4/2020 https://172.23.117.18/serviceassurance/tview/print/575?level=20&system=All+Systems&details=true
INVITE,ACK,OPTIONS,BYE,CANCEL,REGISTER,INFO,COMET,UPDATE,PRACK,REFER,SUBSCRIBE,NOTIFY,MESSAGE,PUBLISH
Contact: <sip:[email protected]:5060>
From: <sip:[email protected]:5060>;tag=172.16.35.74+1+8f3897d6+7bccedd9
To: <sip:[email protected]:5060;user=phone>;tag=352F32463135364148ADDF02
Call-ID: [email protected]
CSeq: 541260929 INVITE
Via: SIP/2.0/UDP
172.16.35.74:5060;branch=z9hG4bK+033310f46d2a5045105ff003161cd95f1+sip+1+a6519c10;received=172.16.35.74
Content-Length: 0

2020-04-06 23:13:23.538 - Incoming SIP message received : 180 Ringing From:

<sip:[email protected]:5060> To: <sip:[email protected]:5060

Integrated Session Controller SSCC-SBC

956903035

Incoming SIP message received from 172.23.119.153:5060 to 172.16.35.74:5060 on service network 1:

Summary: 180 Ringing From: <sip:[email protected]:5060> To: <sip:[email protected]:5060

SIP/2.0 180 Ringing
Allow:
INVITE,ACK,OPTIONS,BYE,CANCEL,REGISTER,INFO,COMET,UPDATE,PRACK,REFER,SUBSCRIBE,NOTIFY,MESSAGE,PUBLISH
Contact: <sip:[email protected]:5060>
From: <sip:[email protected]:5060>;tag=172.16.35.74+1+8f3897d6+7bccedd9
To: <sip:[email protected]:5060;user=phone>;tag=352F32463135364148ADDF02
Call-ID: [email protected]
CSeq: 541260929 INVITE
Via: SIP/2.0/UDP
172.16.35.74:5060;branch=z9hG4bK+033310f46d2a5045105ff003161cd95f1+sip+1+a6519c10;received=172.16.35.74
Content-Length: 0

2020-04-06 23:13:23.538 - MMF editing was applied to an inbound message

Integrated Session Controller SSCC-SBC

956903035

MMF editing has been applied to an inbound message. Logged below are the
edit sequence that was applied and the message after any edits were
made.
If you require more detailed SAS diagnostics showing the full set of
edit steps, you can enable them by configuring a marker-diags filter.
See the Perimeta Operations & Maintenance Guide for more information.
Edit Sequence: FijaRut
Edit Sequence Truncated?: 0
Message after editing:
SIP/2.0 180 Ringing
Allow:
INVITE,ACK,OPTIONS,BYE,CANCEL,REGISTER,INFO,COMET,UPDATE,PRACK,REFER,SUBSCRIBE,NOTIFY,MESSAGE,PUBLISH
Contact: <sip:[email protected]:5060>
From: <sip:[email protected]:5060>;tag=172.16.35.74+1+8f3897d6+7bccedd9
To: <sip:[email protected]:5060;user=phone>;tag=352F32463135364148ADDF02
Call-ID: [email protected]
CSeq: 541260929 INVITE
Via: SIP/2.0/UDP
172.16.35.74:5060;branch=z9hG4bK+033310f46d2a5045105ff003161cd95f1+sip+1+a6519c10;received=172.16.35.74
Content-Length: 0
X-RUT:
X-ANI-Cliente: 956903035

2020-04-06 23:13:23.538 - Adjacency receives inbound message

Integrated Session Controller SSCC-SBC

956903035

Adjacency receives inbound message

Inbound adjacency: Mobile_Carrius2.

Inbound interop profile: Peer.

2020-04-06 23:13:23.538 - 100rel is not being used for this call

Integrated Session Controller SSCC-SBC

956903035

Caller supports 100rel, but callee did not support or use it.

https://172.23.117.18/serviceassurance/tview/print/575?level=20&system=All+Systems&details=true 14/29
6/4/2020 https://172.23.117.18/serviceassurance/tview/print/575?level=20&system=All+Systems&details=true
2020-04-06 23:13:23.538 - Callee 008887802 is ringing

Integrated Session Controller SSCC-SBC

956903035

Callee 008887802 is ringing.

2020-04-06 23:13:23.538 - Adjacency sends outbound message

Integrated Session Controller SSCC-SBC

956903035

Adjacency sends outbound message

Outbound adjacency: MBCLRY1.

Outbound interop profile: None.

2020-04-06 23:13:23.538 - MMF editing was applied to an outbound message

Integrated Session Controller SSCC-SBC

956903035

MMF editing has been applied to an outbound message. Logged below are
the edit sequence that was applied and the message before any edits were
made.
If you require more detailed SAS diagnostics showing the full set of
edit steps, you can enable them by configuring a marker-diags filter.
See the Perimeta Operations & Maintenance Guide for more information.
Edit Sequence: deleteRPID,Copiar-From-a-RPID
Edit Sequence Truncated?: 0
Message before editing:
SIP/2.0 180 Ringing
Call-ID: [email protected]
CSeq: 541260929 INVITE
From: <sip:[email protected];user=phone>;tag=14011976445341
To: <sip:[email protected];user=phone>;tag=sip+4+50f30005+f2fa908a
Via: SIP/2.0/TCP MBCLRY1.MSS.CLARO.CL:5060;received=172.23.216.5;branch=z9hG4bK00072088140142692245
Server: SIP/2.0
Content-Length: 0
Contact: <sip:[email protected]:5060;transport=tcp>
Allow:
INVITE,ACK,OPTIONS,BYE,CANCEL,REGISTER,INFO,COMET,UPDATE,PRACK,REFER,SUBSCRIBE,NOTIFY,MESSAGE,PUBLISH
X-RUT:
X-ANI-Cliente: 956903035

2020-04-06 23:13:23.538 - Unexpected flow media event received by Session Controller

Integrated Session Controller SSCC-SBC

956903035

A flow media event was received from the MPF stub for a flow which was
not expecting it, because the flow is not currently enabled to receive
media.
Flow side : B
Reported events : 0x00000001

2020-04-06 23:13:23.538 - Outgoing SIP message sent : 180 Ringing From:

<sip:[email protected] To: <sip:[email protected]

Integrated Session Controller SSCC-SBC

956903035

Outgoing SIP message sent to 172.23.216.5:5060 from 172.16.35.74:5060 on service network 1:

Summary: 180 Ringing From: <sip:[email protected] To: <sip:[email protected]

SIP/2.0 180 Ringing
Call-ID: [email protected]
CSeq: 541260929 INVITE
From: <sip:[email protected];user=phone>;tag=14011976445341
To: <sip:[email protected];user=phone>;tag=sip+4+50f30005+f2fa908a
Via: SIP/2.0/TCP MBCLRY1.MSS.CLARO.CL:5060;received=172.23.216.5;branch=z9hG4bK00072088140142692245
Server: SIP/2.0
Content-Length: 0
Contact: <sip:[email protected]:5060;transport=tcp>
Allow:
INVITE,ACK,OPTIONS,BYE,CANCEL,REGISTER,INFO,COMET,UPDATE,PRACK,REFER,SUBSCRIBE,NOTIFY,MESSAGE,PUBLISH

https://172.23.117.18/serviceassurance/tview/print/575?level=20&system=All+Systems&details=true 15/29
6/4/2020 https://172.23.117.18/serviceassurance/tview/print/575?level=20&system=All+Systems&details=true
X-RUT:
X-ANI-Cliente: 956903035
Remote-Party-ID: <sip:[email protected];user=phone>;privacy=off;screen=yes

2020-04-06 23:13:23.574 - CallAnswerRequest from APIAPP-ClaroApp3 received.

SB_SB_

Service Broker received CallAnswerRequest from APIAPP-ClaroApp3.

API Service Invocation was received from the specified entity.

2020-04-06 23:13:23.574 - Call answered by APIAPP-ClaroApp3

SB_SB_

Call answered by APIAPP-ClaroApp3

Call answer event was received by the call model.

2020-04-06 23:13:23.579 - Outgoing SIP message sent : 200 OK (SDP) From: <sip:[email protected]:5060>
To: <sip:[email protected]:5060

SB_SB_

Outgoing SIP message sent to none

Summary: 200 OK (SDP) From: <sip:[email protected]:5060> To: <sip:[email protected]:5060

SIP/2.0 200 OK
Content-Type: application/sdp
Content-Length: 202
Contact: <sip:[email protected]:5060>
Allow:
INVITE,ACK,OPTIONS,BYE,CANCEL,REGISTER,INFO,COMET,UPDATE,PRACK,REFER,SUBSCRIBE,NOTIFY,MESSAGE,PUBLISH
Supported: 100rel,diversion
From: <sip:[email protected]:5060>;tag=172.16.35.74+1+8f3897d6+7bccedd9
To: <sip:[email protected]:5060;user=phone>;tag=352F32463135364148ADDF02
Call-ID: [email protected]
CSeq: 541260929 INVITE
Via: SIP/2.0/UDP
172.16.35.74:5060;branch=z9hG4bK+033310f46d2a5045105ff003161cd95f1+sip+1+a6519c10;received=172.16.35.74

v=0
o=- 170114244 170114244 IN IP4 172.16.35.106
s=-
t=0 0
m=audio 5470 RTP/AVP 8 101
c=IN IP4 172.23.119.158
a=fmtp:101 0-15
a=ptime:20
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000

2020-04-06 23:13:23.580 - Added association marker for trail 144125970030331496 (only lower 32 bits of
trail ID shown)

Integrated Session Controller SSCC-SBC

Added association marker for trail 144125970030331496

Variable length data field 0 as hex = 313434313235393730303330333331343936

Variable length data field 0 as string = 144125970030331496
(only lower 32 bits of trail ID shown)

2020-04-06 23:13:23.580 - Trails 1586562664 and 1586562664 associated due to an association marker at the
VPED_ASSOC_SCOPE_TRAIL_GROUP scope (only lower 32 bits of trail IDs are shown).

Integrated Session Controller SSCC-SBC

Trails 1586562664 and 1586562664 associated due to an association marker at the

VPED_ASSOC_SCOPE_TRAIL_GROUP scope (only lower 32 bits of trail IDs are shown).

2020-04-06 23:13:23.580 - Flow allocate request sent

Integrated Session Controller SSCC-SBC

<< Flow allocate req sent FlowPairID (GCI) 49153 Correlator 898000

https://172.23.117.18/serviceassurance/tview/print/575?level=20&system=All+Systems&details=true 16/29
6/4/2020 https://172.23.117.18/serviceassurance/tview/print/575?level=20&system=All+Systems&details=true
2020-04-06 23:13:23.580 - Incoming SIP message received : 200 OK (SDP) From:
<sip:[email protected]:5060> To: <sip:[email protected]:5060

Integrated Session Controller SSCC-SBC

956903035

Incoming SIP message received from 172.23.119.153:5060 to 172.16.35.74:5060 on service network 1:

Summary: 200 OK (SDP) From: <sip:[email protected]:5060> To: <sip:[email protected]:5060

SIP/2.0 200 OK
Content-Type: application/sdp
Content-Length: 202
Contact: <sip:[email protected]:5060>
Allow:
INVITE,ACK,OPTIONS,BYE,CANCEL,REGISTER,INFO,COMET,UPDATE,PRACK,REFER,SUBSCRIBE,NOTIFY,MESSAGE,PUBLISH
Supported: 100rel,diversion
From: <sip:[email protected]:5060>;tag=172.16.35.74+1+8f3897d6+7bccedd9
To: <sip:[email protected]:5060;user=phone>;tag=352F32463135364148ADDF02
Call-ID: [email protected]
CSeq: 541260929 INVITE
Via: SIP/2.0/UDP
172.16.35.74:5060;branch=z9hG4bK+033310f46d2a5045105ff003161cd95f1+sip+1+a6519c10;received=172.16.35.74

v=0
o=- 170114244 170114244 IN IP4 172.16.35.106
s=-
t=0 0
m=audio 5470 RTP/AVP 8 101
c=IN IP4 172.23.119.158
a=fmtp:101 0-15
a=ptime:20
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000

2020-04-06 23:13:23.580 - MMF editing was applied to an inbound message

Integrated Session Controller SSCC-SBC

956903035

MMF editing has been applied to an inbound message. Logged below are the
edit sequence that was applied and the message after any edits were
made.
If you require more detailed SAS diagnostics showing the full set of
edit steps, you can enable them by configuring a marker-diags filter.
See the Perimeta Operations & Maintenance Guide for more information.
Edit Sequence: FijaRut
Edit Sequence Truncated?: 0
Message after editing:
SIP/2.0 200 OK
Content-Type: application/sdp
Content-Length: 202
Contact: <sip:[email protected]:5060>
Allow:
INVITE,ACK,OPTIONS,BYE,CANCEL,REGISTER,INFO,COMET,UPDATE,PRACK,REFER,SUBSCRIBE,NOTIFY,MESSAGE,PUBLISH
Supported: 100rel,diversion
From: <sip:[email protected]:5060>;tag=172.16.35.74+1+8f3897d6+7bccedd9
To: <sip:[email protected]:5060;user=phone>;tag=352F32463135364148ADDF02
Call-ID: [email protected]
CSeq: 541260929 INVITE
Via: SIP/2.0/UDP
172.16.35.74:5060;branch=z9hG4bK+033310f46d2a5045105ff003161cd95f1+sip+1+a6519c10;received=172.16.35.74
X-RUT:
X-ANI-Cliente: 956903035

v=0
o=- 170114244 170114244 IN IP4 172.16.35.106
s=-
t=0 0
m=audio 5470 RTP/AVP 8 101
c=IN IP4 172.23.119.158
a=fmtp:101 0-15
a=ptime:20
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000

https://172.23.117.18/serviceassurance/tview/print/575?level=20&system=All+Systems&details=true 17/29
6/4/2020 https://172.23.117.18/serviceassurance/tview/print/575?level=20&system=All+Systems&details=true
2020-04-06 23:13:23.580 - Adjacency receives inbound message

Integrated Session Controller SSCC-SBC

956903035

Adjacency receives inbound message

Inbound adjacency: Mobile_Carrius2.

Inbound interop profile: Peer.

2020-04-06 23:13:23.580 - Callee 008887802 has answered

Integrated Session Controller SSCC-SBC

956903035

Callee 008887802 has answered.

2020-04-06 23:13:23.580 - Session Controller has received a SIP INVITE final response

Integrated Session Controller SSCC-SBC

956903035

The response may connect or reject a new call, or accept or fail a

renegotiation on an existing call.
Response code: 200

2020-04-06 23:13:23.580 - Signaling has determined internal settings for SDP

Integrated Session Controller SSCC-SBC

956903035

Signaling has determined the following internal settings for SDP:

Offer-answer message type: 2

Offerer SDP is superfluous: 0
Requesting repeat of answer SDP: 0
SRTP fallback supported: 0
Check SIP session refresh: 0
SDP final answer: 1

2020-04-06 23:13:23.580 - Session Controller is participating in Session Timer

Integrated Session Controller SSCC-SBC

956903035

Session Controller is participating in Session Timer on this call branch.

Session timer role: None
Session Expiry Interval: 1800

2020-04-06 23:13:23.580 - GCI message sent

Integrated Session Controller SSCC-SBC

956903035

Sending gate commit request (rc=0x00000000):

Gate id:52408987, flowpair_id=0x0000C001, side A flow_id=898000, side B flow_id=898001

2020-04-06 23:13:23.580 - Gate commit request received

Integrated Session Controller SSCC-SBC

956903035

<< Gate commit req BillingID (sideA)

00000000 00000000 00000000 00000000 00000000 00000000 BillingID (sideB)
00000000 00000000 00000000 00000000 00000000 00000000

2020-04-06 23:13:23.580 - Flow modify request sent

Integrated Session Controller SSCC-SBC

956903035

<< Flow modify req sent FlowPairID (GCI) 49153 Correlator 898000

2020-04-06 23:13:23.580 - Flow modify response received

Integrated Session Controller SSCC-SBC

956903035

https://172.23.117.18/serviceassurance/tview/print/575?level=20&system=All+Systems&details=true 18/29
6/4/2020 https://172.23.117.18/serviceassurance/tview/print/575?level=20&system=All+Systems&details=true
>> Flow modify rsp rcvd FlowPairID (GCI) 49153 Correlator 898000 Result 0x00000000

2020-04-06 23:13:23.580 - Gate 52408987 is being committed.

Integrated Session Controller SSCC-SBC

956903035

A gate is being committed.

Gate ID: 52408987.

Media stream identifiers:
Media stream ID 1: 46032

2020-04-06 23:13:23.580 - Gate commit response sent

Integrated Session Controller SSCC-SBC

956903035

>> Gate commit rsp (0) BillingID (sideA)

00000000 00000000 00000000 00000000 00000000 00000000 BillingID (sideB)
00000000 00000000 00000000 00000000 00000000 00000000

2020-04-06 23:13:23.580 - GCI message received

Integrated Session Controller SSCC-SBC

956903035

Receiving gate commit response (rc=0x00000000):

Gate id:52408987, flowpair_id=0x0000C001, side A flow_id=898000, side B flow_id=898001

2020-04-06 23:13:23.580 - A codec was agreed for stream 0 : PCMA

Integrated Session Controller SSCC-SBC

956903035

A codec was agreed for stream 0.

Codec name: PCMA

2020-04-06 23:13:23.581 - Media has been allocated for a call

Integrated Session Controller SSCC-SBC

Media has been allocated for a call.

Media stream ID: 49153

Media correlator: 898000
Bandwidth flow A: 12600
Bandwidth flow B: 12600

2020-04-06 23:13:23.581 - Session Controller is participating in Session Timer

Integrated Session Controller SSCC-SBC

956903035

Session Controller is participating in Session Timer on this call branch.

Session timer role: None
Session Expiry Interval: 1800

2020-04-06 23:13:23.581 - Adjacency sends outbound message

Integrated Session Controller SSCC-SBC

956903035

Adjacency sends outbound message

Outbound adjacency: MBCLRY1.

Outbound interop profile: None.

2020-04-06 23:13:23.581 - MMF editing was applied to an outbound message

Integrated Session Controller SSCC-SBC

956903035

MMF editing has been applied to an outbound message. Logged below are
the edit sequence that was applied and the message before any edits were
made.
If you require more detailed SAS diagnostics showing the full set of

https://172.23.117.18/serviceassurance/tview/print/575?level=20&system=All+Systems&details=true 19/29
6/4/2020 https://172.23.117.18/serviceassurance/tview/print/575?level=20&system=All+Systems&details=true
edit steps, you can enable them by configuring a marker-diags filter.
See the Perimeta Operations & Maintenance Guide for more information.
Edit Sequence: deleteRPID,Copiar-From-a-RPID
Edit Sequence Truncated?: 0
Message before editing:
SIP/2.0 200 OK
Call-ID: [email protected]
CSeq: 541260929 INVITE
From: <sip:[email protected];user=phone>;tag=14011976445341
To: <sip:[email protected];user=phone>;tag=sip+4+50f30005+f2fa908a
Via: SIP/2.0/TCP MBCLRY1.MSS.CLARO.CL:5060;received=172.23.216.5;branch=z9hG4bK00072088140142692245
Server: SIP/2.0
Content-Length: 224
Supported: 100rel,diversion
Contact: <sip:[email protected]:5060;transport=tcp>
Content-Type: application/sdp
Allow:
INVITE,ACK,OPTIONS,BYE,CANCEL,REGISTER,INFO,COMET,UPDATE,PRACK,REFER,SUBSCRIBE,NOTIFY,MESSAGE,PUBLISH
X-RUT:
X-ANI-Cliente: 956903035

v=0
o=- 88751374319028 88751374319028 IN IP4 172.16.35.106
s=-
c=IN IP4 172.16.35.106
t=0 0
a=sendrecv
m=audio 16902 RTP/AVP 8 101
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20

2020-04-06 23:13:23.581 - Outgoing SIP message sent : 200 OK (SDP) From:

<sip:[email protected] To: <sip:[email protected]

Integrated Session Controller SSCC-SBC

956903035

Outgoing SIP message sent to 172.23.216.5:5060 from 172.16.35.74:5060 on service network 1:

Summary: 200 OK (SDP) From: <sip:[email protected] To: <sip:[email protected]

SIP/2.0 200 OK
Call-ID: [email protected]
CSeq: 541260929 INVITE
From: <sip:[email protected];user=phone>;tag=14011976445341
To: <sip:[email protected];user=phone>;tag=sip+4+50f30005+f2fa908a
Via: SIP/2.0/TCP MBCLRY1.MSS.CLARO.CL:5060;received=172.23.216.5;branch=z9hG4bK00072088140142692245
Server: SIP/2.0
Content-Length: 224
Supported: 100rel,diversion
Contact: <sip:[email protected]:5060;transport=tcp>
Content-Type: application/sdp
Allow:
INVITE,ACK,OPTIONS,BYE,CANCEL,REGISTER,INFO,COMET,UPDATE,PRACK,REFER,SUBSCRIBE,NOTIFY,MESSAGE,PUBLISH
X-RUT:
X-ANI-Cliente: 956903035
Remote-Party-ID: <sip:[email protected];user=phone>;privacy=off;screen=yes

v=0
o=- 88751374319028 88751374319028 IN IP4 172.16.35.106
s=-
c=IN IP4 172.16.35.106
t=0 0
a=sendrecv
m=audio 16902 RTP/AVP 8 101
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20

2020-04-06 23:13:23.635 - Added association marker for trail 144125970030331496 (only lower 32 bits of
trail ID shown)

Integrated Session Controller SSCC-SBC

https://172.23.117.18/serviceassurance/tview/print/575?level=20&system=All+Systems&details=true 20/29
6/4/2020 https://172.23.117.18/serviceassurance/tview/print/575?level=20&system=All+Systems&details=true
Added association marker for trail 144125970030331496

Variable length data field 0 as hex = 313434313235393730303330333331343936

Variable length data field 0 as string = 144125970030331496
(only lower 32 bits of trail ID shown)

2020-04-06 23:13:23.635 - Trails 1586562664 and 1586562664 associated due to an association marker at the
VPED_ASSOC_SCOPE_TRAIL_GROUP scope (only lower 32 bits of trail IDs are shown).

Integrated Session Controller SSCC-SBC

Trails 1586562664 and 1586562664 associated due to an association marker at the

VPED_ASSOC_SCOPE_TRAIL_GROUP scope (only lower 32 bits of trail IDs are shown).

2020-04-06 23:13:23.653 - Incoming SIP message received : ACK [email protected]

>[email protected]

Integrated Session Controller SSCC-SBC

956903035

Incoming SIP message received from 172.23.216.5:64515 to 172.16.35.74:5060 on service network 1:

Summary: ACK [email protected]>[email protected]

ACK sip:[email protected]:5060;transport=TCP SIP/2.0
From: <sip:[email protected];user=phone>;tag=14011976445341
To: <sip:[email protected];user=phone>;tag=sip+4+50f30005+f2fa908a
Max-Forwards: 70
Via: SIP/2.0/TCP MBCLRY1.MSS.CLARO.CL:5060;branch=z9hG4bK00072084714115738151
Call-ID: [email protected]
CSeq: 541260929 ACK
Content-Length: 0

2020-04-06 23:13:23.653 - MMF editing was applied to an inbound message

Integrated Session Controller SSCC-SBC

956903035

MMF editing has been applied to an inbound message. Logged below are the
edit sequence that was applied and the message after any edits were
made.
If you require more detailed SAS diagnostics showing the full set of
edit steps, you can enable them by configuring a marker-diags filter.
See the Perimeta Operations & Maintenance Guide for more information.
Edit Sequence: Hdr_Ctct_Rmt_Addr,deleteRecordRoute
Edit Sequence Truncated?: 0
Message after editing:
ACK sip:[email protected]:5060;transport=TCP SIP/2.0
From: <sip:[email protected];user=phone>;tag=14011976445341
To: <sip:[email protected];user=phone>;tag=sip+4+50f30005+f2fa908a
Max-Forwards: 70
Via: SIP/2.0/TCP MBCLRY1.MSS.CLARO.CL:5060;branch=z9hG4bK00072084714115738151
Call-ID: [email protected]
CSeq: 541260929 ACK
Content-Length: 0

2020-04-06 23:13:23.653 - Adjacency receives inbound message

Integrated Session Controller SSCC-SBC

956903035

Adjacency receives inbound message

Inbound adjacency: MBCLRY1.

Inbound interop profile: None.

2020-04-06 23:13:23.653 - Adjacency sends outbound message

Integrated Session Controller SSCC-SBC

956903035

Adjacency sends outbound message

Outbound adjacency: Mobile_Carrius2.

Outbound interop profile: Peer.

2020-04-06 23:13:23.653 - Outgoing SIP message sent : ACK [email protected]:5060-

>[email protected]:5060 [email protected]:5060
https://172.23.117.18/serviceassurance/tview/print/575?level=20&system=All+Systems&details=true 21/29
6/4/2020 https://172.23.117.18/serviceassurance/tview/print/575?level=20&system=All+Systems&details=true
Integrated Session Controller SSCC-SBC
956903035

Outgoing SIP message sent to 172.23.119.153:5060 from 172.16.35.74:5060 on service network 1:

Summary: ACK [email protected]:5060->[email protected]:5060 [email protected]:5060

ACK sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 172.16.35.74:5060;branch=z9hG4bK+c892225cd20416027a40830b54a844911+sip+1+a6519c12
Call-ID: [email protected]
From: <sip:[email protected]:5060>;tag=172.16.35.74+1+8f3897d6+7bccedd9
To: <sip:[email protected]:5060;user=phone>;tag=352F32463135364148ADDF02
CSeq: 541260929 ACK
Contact: <sip:[email protected]:5060>
Content-Length: 0
Max-Forwards: 69

2020-04-06 23:13:23.653 - Incoming SIP message received : ACK [email protected]:5060-

>[email protected]:5060 [email protected]:5060

SB_SB_

Incoming SIP message received from none:

Summary: ACK [email protected]:5060->[email protected]:5060 [email protected]:5060

ACK sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 172.16.35.74:5060;branch=z9hG4bK+c892225cd20416027a40830b54a844911+sip+1+a6519c12
Call-ID: [email protected]
From: <sip:[email protected]:5060>;tag=172.16.35.74+1+8f3897d6+7bccedd9
To: <sip:[email protected]:5060;user=phone>;tag=352F32463135364148ADDF02
CSeq: 541260929 ACK
Contact: <sip:[email protected]:5060>
Content-Length: 0
Max-Forwards: 69

2020-04-06 23:13:23.656 - Outgoing SIP message sent : ACK [email protected]:5060-

>[email protected]:5060 [email protected]

SB_SB_

Outgoing SIP message sent to none

Summary: ACK [email protected]:5060->[email protected]:5060 [email protected]

ACK sip:[email protected] SIP/2.0
CSeq: 1 ACK
To: <sip:[email protected]:5060;transport=udp;user=phone>;tag=139bd990-837717ac-13c4-50022-
238648-1e0c21b8-238648
From: <sip:[email protected]:5060;transport=udp;user=phone>;tag=55573246313536414AADDF02
Call-ID: 0210A1A0A681400000135A36@SIPAgent
Max-Forwards: 70
Via: SIP/2.0/UDP
172.23.119.153:5060;branch=z9hG4bK876C114F4900AD63E1F541D0300E9FCE;rport;SIPAgent01.com
Content-Length: 0

2020-04-06 23:13:25.698 - Incoming SIP message received : BYE [email protected]

>[email protected]

Integrated Session Controller SSCC-SBC

956903035

Incoming SIP message received from 172.23.216.5:64515 to 172.16.35.74:5060 on service network 1:

Summary: BYE [email protected]>[email protected]

BYE sip:[email protected]:5060;transport=TCP SIP/2.0
From: <sip:[email protected];user=phone>;tag=14011976445341
To: <sip:[email protected];user=phone>;tag=sip+4+50f30005+f2fa908a
Max-Forwards: 70
Via: SIP/2.0/TCP MBCLRY1.MSS.CLARO.CL:5060;branch=z9hG4bK00072067566048695286
Call-ID: [email protected]
CSeq: 541260930 BYE
Reason: Q.850;cause=34
Content-Length: 0

2020-04-06 23:13:25.698 - MMF editing was applied to an inbound message

Integrated Session Controller SSCC-SBC

956903035

https://172.23.117.18/serviceassurance/tview/print/575?level=20&system=All+Systems&details=true 22/29
6/4/2020 https://172.23.117.18/serviceassurance/tview/print/575?level=20&system=All+Systems&details=true
MMF editing has been applied to an inbound message. Logged below are the
edit sequence that was applied and the message after any edits were
made.
If you require more detailed SAS diagnostics showing the full set of
edit steps, you can enable them by configuring a marker-diags filter.
See the Perimeta Operations & Maintenance Guide for more information.
Edit Sequence: Hdr_Ctct_Rmt_Addr,deleteRecordRoute
Edit Sequence Truncated?: 0
Message after editing:
BYE sip:[email protected]:5060;transport=TCP SIP/2.0
From: <sip:[email protected];user=phone>;tag=14011976445341
To: <sip:[email protected];user=phone>;tag=sip+4+50f30005+f2fa908a
Max-Forwards: 70
Via: SIP/2.0/TCP MBCLRY1.MSS.CLARO.CL:5060;branch=z9hG4bK00072067566048695286
Call-ID: [email protected]
CSeq: 541260930 BYE
Reason: Q.850;cause=34
Content-Length: 0

2020-04-06 23:13:25.698 - 956903035 is disconnecting from the call

Integrated Session Controller SSCC-SBC

956903035

956903035 is disconnecting from the call.

2020-04-06 23:13:25.698 - Adjacency receives inbound message

Integrated Session Controller SSCC-SBC

956903035

Adjacency receives inbound message

Inbound adjacency: MBCLRY1.

Inbound interop profile: None.

2020-04-06 23:13:25.698 - Session Controller has received a SIP BYE request

Integrated Session Controller SSCC-SBC

956903035

The BYE may release the call.

2020-04-06 23:13:25.698 - Adjacency sends outbound message

Integrated Session Controller SSCC-SBC

956903035

Adjacency sends outbound message

Outbound adjacency: Mobile_Carrius2.

Outbound interop profile: Peer.

2020-04-06 23:13:25.698 - Session Controller has sent a SIP BYE request

Integrated Session Controller SSCC-SBC

956903035

The BYE may release the call.

2020-04-06 23:13:25.698 - Sending outgoing SIP call release request

Integrated Session Controller SSCC-SBC

956903035

Sending outgoing SIP call release request

Outbound adjacency: Mobile_Carrius2.

Outbound interop profile: Peer.

2020-04-06 23:13:25.698 - Outgoing SIP message sent : BYE [email protected]:5060-

>[email protected]:5060 [email protected]:5060

Integrated Session Controller SSCC-SBC

956903035

Outgoing SIP message sent to 172.23.119.153:5060 from 172.16.35.74:5060 on service network 1:

https://172.23.117.18/serviceassurance/tview/print/575?level=20&system=All+Systems&details=true 23/29
6/4/2020 https://172.23.117.18/serviceassurance/tview/print/575?level=20&system=All+Systems&details=true
Summary: BYE [email protected]:5060->[email protected]:5060 [email protected]:5060
BYE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 172.16.35.74:5060;branch=z9hG4bK+d16e697f331f2478419760af608225a61+sip+1+a6519c13
Call-ID: [email protected]
From: <sip:[email protected]:5060>;tag=172.16.35.74+1+8f3897d6+7bccedd9
To: <sip:[email protected]:5060;user=phone>;tag=352F32463135364148ADDF02
CSeq: 541260930 BYE
Content-Length: 0
Max-Forwards: 69
Reason: Q.850;cause=34

2020-04-06 23:13:25.698 - Incoming SIP message received : BYE [email protected]:5060-

>[email protected]:5060 [email protected]:5060

SB_SB_

Incoming SIP message received from none:

Summary: BYE [email protected]:5060->[email protected]:5060 [email protected]:5060

BYE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 172.16.35.74:5060;branch=z9hG4bK+d16e697f331f2478419760af608225a61+sip+1+a6519c13
Call-ID: [email protected]
From: <sip:[email protected]:5060>;tag=172.16.35.74+1+8f3897d6+7bccedd9
To: <sip:[email protected]:5060;user=phone>;tag=352F32463135364148ADDF02
CSeq: 541260930 BYE
Content-Length: 0
Max-Forwards: 69
Reason: Q.850;cause=34

2020-04-06 23:13:25.703 - DisconnectAudioTwoWayRequest from APIAPP-ClaroApp3 received.

SB_SB_

Service Broker received DisconnectAudioTwoWayRequest from APIAPP-ClaroApp3.

API Service Invocation was received from the specified entity.

2020-04-06 23:13:25.703 - CallDisconnectRequest from APIAPP-ClaroApp3 received.

SB_SB_

Service Broker received CallDisconnectRequest from APIAPP-ClaroApp3.

API Service Invocation was received from the specified entity.

2020-04-06 23:13:25.742 - CallDisconnectCompleteRequest from APIAPP-ClaroApp3 received.

SB_SB_

Service Broker received CallDisconnectCompleteRequest from APIAPP-ClaroApp3.

API Service Invocation was received from the specified entity.

2020-04-06 23:13:25.745 - Outgoing SIP message sent : BYE [email protected]:5060-

>[email protected]:5060 [email protected]

SB_SB_

Outgoing SIP message sent to none

Summary: BYE [email protected]:5060->[email protected]:5060 [email protected]

BYE sip:[email protected] SIP/2.0
To: <sip:[email protected]:5060;transport=udp;user=phone>;tag=139bd990-837717ac-13c4-50022-
238648-1e0c21b8-238648
From: <sip:[email protected]:5060;transport=udp;user=phone>;tag=55573246313536414AADDF02
Call-ID: 0210A1A0A681400000135A36@SIPAgent
Max-Forwards: 70
CSeq: 3 BYE
Via: SIP/2.0/UDP
172.23.119.153:5060;branch=z9hG4bK799AD96EE70514FA006372A39F0E3678;rport;SIPAgent01.com
Content-Length: 0

2020-04-06 23:13:25.745 - Outgoing SIP message sent : 200 OK From: <sip:[email protected]:5060> To:
<sip:[email protected]:5060

SB_SB_

https://172.23.117.18/serviceassurance/tview/print/575?level=20&system=All+Systems&details=true 24/29
6/4/2020 https://172.23.117.18/serviceassurance/tview/print/575?level=20&system=All+Systems&details=true
Outgoing SIP message sent to none

Summary: 200 OK From: <sip:[email protected]:5060> To: <sip:[email protected]:5060

SIP/2.0 200 OK
From: <sip:[email protected]:5060>;tag=172.16.35.74+1+8f3897d6+7bccedd9
To: <sip:[email protected]:5060;user=phone>;tag=352F32463135364148ADDF02
Call-ID: [email protected]
CSeq: 541260930 BYE
Via: SIP/2.0/UDP
172.16.35.74:5060;branch=z9hG4bK+d16e697f331f2478419760af608225a61+sip+1+a6519c13;received=172.16.35.74
Content-Length: 0

2020-04-06 23:13:25.747 - Flow delete request sent

Integrated Session Controller SSCC-SBC

<< Flow delete req sent FlowPairID (GCI) 49153 Correlator 898000

2020-04-06 23:13:25.747 - Flow delete response received

Integrated Session Controller SSCC-SBC

>> Flow delete rsp rcvd FlowPairID (GCI) 49153 Correlator 898000 Result 0x00000000

2020-04-06 23:13:25.747 - Incoming SIP message received : 200 OK From: <sip:[email protected]:5060>

To: <sip:[email protected]:5060

Integrated Session Controller SSCC-SBC

956903035

Incoming SIP message received from 172.23.119.153:5060 to 172.16.35.74:5060 on service network 1:

Summary: 200 OK From: <sip:[email protected]:5060> To: <sip:[email protected]:5060

SIP/2.0 200 OK
From: <sip:[email protected]:5060>;tag=172.16.35.74+1+8f3897d6+7bccedd9
To: <sip:[email protected]:5060;user=phone>;tag=352F32463135364148ADDF02
Call-ID: [email protected]
CSeq: 541260930 BYE
Via: SIP/2.0/UDP
172.16.35.74:5060;branch=z9hG4bK+d16e697f331f2478419760af608225a61+sip+1+a6519c13;received=172.16.35.74
Content-Length: 0

2020-04-06 23:13:25.747 - MMF editing was applied to an inbound message

Integrated Session Controller SSCC-SBC

956903035

MMF editing has been applied to an inbound message. Logged below are the
edit sequence that was applied and the message after any edits were
made.
If you require more detailed SAS diagnostics showing the full set of
edit steps, you can enable them by configuring a marker-diags filter.
See the Perimeta Operations & Maintenance Guide for more information.
Edit Sequence: FijaRut
Edit Sequence Truncated?: 0
Message after editing:
SIP/2.0 200 OK
From: <sip:[email protected]:5060>;tag=172.16.35.74+1+8f3897d6+7bccedd9
To: <sip:[email protected]:5060;user=phone>;tag=352F32463135364148ADDF02
Call-ID: [email protected]
CSeq: 541260930 BYE
Via: SIP/2.0/UDP
172.16.35.74:5060;branch=z9hG4bK+d16e697f331f2478419760af608225a61+sip+1+a6519c13;received=172.16.35.74
Content-Length: 0
X-RUT:
X-ANI-Cliente: 956903035

2020-04-06 23:13:25.747 - Adjacency receives inbound message

Integrated Session Controller SSCC-SBC

956903035

Adjacency receives inbound message

Inbound adjacency: Mobile_Carrius2.

Inbound interop profile: Peer.

https://172.23.117.18/serviceassurance/tview/print/575?level=20&system=All+Systems&details=true 25/29
6/4/2020 https://172.23.117.18/serviceassurance/tview/print/575?level=20&system=All+Systems&details=true
2020-04-06 23:13:25.747 - Session Controller has received a SIP BYE response

Integrated Session Controller SSCC-SBC

956903035

The BYE response may release the call, or may be passed through without
affecting call state.
Response code: 200
Call releasing: True

2020-04-06 23:13:25.747 - Adjacency sends outbound message

Integrated Session Controller SSCC-SBC

956903035

Adjacency sends outbound message

Outbound adjacency: MBCLRY1.

Outbound interop profile: None.

2020-04-06 23:13:25.747 - GCI message sent

Integrated Session Controller SSCC-SBC

956903035

Sending gate delete

2020-04-06 23:13:25.747 - Gate delete request received

Integrated Session Controller SSCC-SBC

956903035

<< Gate delete req BillingID (sideA)

5E8BEFD3 20202020 20202030 302B3034 30303030 063F7947 BillingID (sideB)
5E8BEFD3 20202020 20202030 302B3034 30303030 063F7948

2020-04-06 23:13:25.747 - Flow delete request sent

Integrated Session Controller SSCC-SBC

956903035

<< Flow delete req sent FlowPairID (GCI) 49153 Correlator 898000

2020-04-06 23:13:25.747 - Gate 52408987 is being deleted

Integrated Session Controller SSCC-SBC

956903035

A gate is being deleted.

Gate ID: 52408987

2020-04-06 23:13:25.747 - MMF editing was applied to an outbound message

Integrated Session Controller SSCC-SBC

956903035

MMF editing has been applied to an outbound message. Logged below are
the edit sequence that was applied and the message before any edits were
made.
If you require more detailed SAS diagnostics showing the full set of
edit steps, you can enable them by configuring a marker-diags filter.
See the Perimeta Operations & Maintenance Guide for more information.
Edit Sequence: deleteRPID,Copiar-From-a-RPID
Edit Sequence Truncated?: 0
Message before editing:
SIP/2.0 200 OK
Call-ID: [email protected]
CSeq: 541260930 BYE
From: <sip:[email protected];user=phone>;tag=14011976445341
To: <sip:[email protected];user=phone>;tag=sip+4+50f30005+f2fa908a
Via: SIP/2.0/TCP MBCLRY1.MSS.CLARO.CL:5060;received=172.23.216.5;branch=z9hG4bK00072067566048695286
Server: SIP/2.0
Content-Length: 0
Contact: <sip:[email protected]:5060;transport=tcp>
X-RUT:
X-ANI-Cliente: 956903035

https://172.23.117.18/serviceassurance/tview/print/575?level=20&system=All+Systems&details=true 26/29
6/4/2020 https://172.23.117.18/serviceassurance/tview/print/575?level=20&system=All+Systems&details=true
2020-04-06 23:13:25.747 - Flow delete response received

Integrated Session Controller SSCC-SBC

956903035

>> Flow delete rsp rcvd FlowPairID (GCI) 49153 Correlator 898000 Result 0x00000000

2020-04-06 23:13:25.747 - Outgoing SIP message sent : 200 OK From: <sip:[email protected] To:
<sip:[email protected]

Integrated Session Controller SSCC-SBC

956903035

Outgoing SIP message sent to 172.23.216.5:5060 from 172.16.35.74:5060 on service network 1:

Summary: 200 OK From: <sip:[email protected] To: <sip:[email protected]

SIP/2.0 200 OK
Call-ID: [email protected]
CSeq: 541260930 BYE
From: <sip:[email protected];user=phone>;tag=14011976445341
To: <sip:[email protected];user=phone>;tag=sip+4+50f30005+f2fa908a
Via: SIP/2.0/TCP MBCLRY1.MSS.CLARO.CL:5060;received=172.23.216.5;branch=z9hG4bK00072067566048695286
Server: SIP/2.0
Content-Length: 0
Contact: <sip:[email protected]:5060;transport=tcp>
X-RUT:
X-ANI-Cliente: 956903035
Remote-Party-ID: <sip:[email protected];user=phone>;privacy=off;screen=yes

2020-04-06 23:13:25.747 - Gate delete response sent

Integrated Session Controller SSCC-SBC

956903035

>> Gate delete rsp (0) BillingID (sideA)

5E8BEFD3 20202020 20202030 302B3034 30303030 063F7947 BillingID (sideB)
5E8BEFD3 20202020 20202030 302B3034 30303030 063F7948

2020-04-06 23:13:25.747 - GCI message received

Integrated Session Controller SSCC-SBC

956903035

Receiving gate delete

2020-04-06 23:13:25.747 - SIP message may be have been dropped due to internal error

Integrated Session Controller SSCC-SBC

956903035

A transmitted SIP response has been received back from CH but cannot be
be matched to an active response
Handles
Call = 1358102533
Dialog = 1422721029
Transaction = 3056271382
Response = 1691156502
Correlators
Call =
11000755 00006C52
Dialog =
11000755 00000000
Transaction =
11000755 00000000
Response =
11000755 00000000

2020-04-06 23:13:25.747 - Session Controller has used a default to calculate VQM statistics

Integrated Session Controller SSCC-SBC

956903035

Session Controller has used a perfect default for a statistic to

calculate VQM statistics for this call because there is no statistic
from the call or from an average to use.

https://172.23.117.18/serviceassurance/tview/print/575?level=20&system=All+Systems&details=true 27/29
6/4/2020 https://172.23.117.18/serviceassurance/tview/print/575?level=20&system=All+Systems&details=true
Statistic: Round trip delay
Default value: 0 ms

2020-04-06 23:13:25.747 - Session Controller has used an average to calculate VQM statistics. This will be
used as input to R-Factor and MOScqe calculation

Integrated Session Controller SSCC-SBC

956903035

Session Controller has used an average statistic to calculate VQM

statistics for this call because there is no statistic from this call to
use. This will be used as input to R-Factor and MOScqe calculation.
Statistic: End point jitter
Average used: Global
Value of average: 2 ms

2020-04-06 23:13:25.747 - Session Controller has used a default to calculate VQM statistics

Integrated Session Controller SSCC-SBC

956903035

Session Controller has used a perfect default for a statistic to

calculate VQM statistics for this call because there is no statistic
from the call or from an average to use.
Statistic: Round trip delay
Default value: 0 ms

2020-04-06 23:13:25.748 - Voice quality monitor statistics were determined for Caller.

Integrated Session Controller SSCC-SBC

956903035

Voice quality monitor statistics were determined for Caller (956903035) on adjacency MBCLRY1.

Perimeta -> Caller:

RTP/RTCP sent to Caller = 108 packets (21600 octets)
RTP received by Caller (taken from RTCP) = 108 packets
RTP/RTCP sent to Caller but not received (derived from RTCP) = 0 packets

Caller -> Perimeta:

RTP sent from Caller stats unavailable.
RTP/RTCP received by Perimeta = 1 packets (200 octets)
RTP/RTCP received by Perimeta and discarded = 0 packets (0 octets)
RTP sent from Caller but not received (derived from RTCP) = 0 packets

Overall VQM Statistics:

Reported by Caller-side endpoint in RTCP:

Maximum jitter = 0 RTP timestamp units
Packet loss = 0.00%

Calculated by Perimeta:
Round trip delay unavailable.
R-factor = 92
MOScqe = 4.4

2020-04-06 23:13:25.748 - Voice quality monitor statistics were determined for Callee.

Integrated Session Controller SSCC-SBC

956903035

Voice quality monitor statistics were determined for Callee (008887802) on adjacency Mobile_Carrius2.

Perimeta -> Callee:

RTP/RTCP sent to Callee = 1 packets (200 octets)
RTP received by Callee (taken from RTCP) stats unavailable.
RTP sent to Callee but not received (derived from RTCP) stats unavailable.

Callee -> Perimeta:

RTP sent from Callee stats unavailable.
RTP/RTCP received by Perimeta = 111 packets (22200 octets)
RTP/RTCP received by Perimeta and discarded = 3 packets (600 octets)
RTP sent from Callee but not received (derived from RTCP) = 0 packets

Overall VQM Statistics:

https://172.23.117.18/serviceassurance/tview/print/575?level=20&system=All+Systems&details=true 28/29
6/4/2020 https://172.23.117.18/serviceassurance/tview/print/575?level=20&system=All+Systems&details=true
Reported by Callee-side endpoint in RTCP:
Maximum jitter unavailable.
Packet loss unavailable.

Calculated by Perimeta:
Round trip delay unavailable.
R-factor = 92
MOScqe = 4.4

2020-04-06 23:13:25.913 - Incoming SIP message received : 200 OK From: <sip:[email protected]:5060

To: <sip:[email protected]:5060

SB_SB_

Incoming SIP message received from none:

Summary: 200 OK From: <sip:[email protected]:5060 To: <sip:[email protected]:5060

SIP/2.0 200 OK
From: <sip:[email protected]:5060;transport=udp;user=phone>;tag=55573246313536414AADDF02
To: <sip:[email protected]:5060;user=phone>;tag=139bd990-837717ac-13c4-50022-238648-1e0c21b8-
238648
Call-ID: 0210A1A0A681400000135A36@SIPAgent
CSeq: 3 BYE
Via: SIP/2.0/UDP
172.23.119.153:5060;rport=5060;branch=z9hG4bK799AD96EE70514FA006372A39F0E3678;SIPAgent01.com
Allow: INVITE, CANCEL, ACK, BYE, OPTIONS, INFO, REFER, NOTIFY, UPDATE
Content-Length: 0

2020-04-06 23:13:25.954 - CallDisconnectCompleteRequest from APIAPP-ClaroApp3 received.

SB_SB_

Service Broker received CallDisconnectCompleteRequest from APIAPP-ClaroApp3.

API Service Invocation was received from the specified entity.

2020-04-06 23:13:25.955 - Call has been successfully released.

SB_SB_

Call has been successfully released.

https://172.23.117.18/serviceassurance/tview/print/575?level=20&system=All+Systems&details=true 29/29