Project

General

Profile

Bug #3741

Unknow call parameters shown in vty

Added by msuraev 3 months ago. Updated 3 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
12/28/2018
Due date:
% Done:

0%

Resolution:

Description

Observed during 35c3:

Call(9535) from 5139 to 6523
 Initial leg of type: MNCC
 MNCC state(CONNECTED)
 MNCC dir(MO)
 MNCC callref(2147484726)
 MNCC called TON(0) NPI(1) NUM(6523)
 MNCC calling TON(0) NPI(0) NUM(5139)
 MNCC imsi(262423403000905)
 MNCC timer pending(0)
 Remote leg of type: SIP
 SIP nua_handle(0x55dfdf2cb940)
 SIP state(CONNECTED)
 SIP dir(MT)
 SIP wanted_codec(AMR)
Call(9343) from   to
 Remote leg of type: SIP
 SIP nua_handle(0x55dfdf2e2f30)
 SIP state(CONNECTED)
 SIP dir(MT)
 SIP wanted_codec(AMR)
Call(9283) from � to -Info
 Remote leg of type: SIP
 SIP nua_handle(0x55dfdf2aeb60)
 SIP state(CONNECTED)
 SIP dir(MT)
 SIP wanted_codec(AMR)
Call(8995) from �%/��U to
 Remote leg of type: SIP
 SIP nua_handle(0x55dfdf2b4d30)
 SIP state(CONNECTED)
 SIP dir(MT)
 SIP wanted_codec(AMR)
Call(7518) from 2317 to 4769
 Initial leg of type: SIP
 SIP nua_handle(0x55dfdf2ae6d0)
 SIP state(CONFIRMED)
 SIP dir(MO)
 SIP wanted_codec((null))

For some calls the "from" and "to" fields (corresponding to call->source and call->dest) are clearly poiting to some place they shouldn't. We should fix this and make sure that call-> fields are always pointing to correct parameters.

History

#1 Updated by msuraev 3 months ago

Version: OsmoSIPcon 1.1.1.45-dc16 (OsmoSIPcon)

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)