Project

General

Profile

Actions

Bug #1662

closed

don't print "osmo-ortp(): network_error" messages between CRCX and MDCX.

Added by laforge about 8 years ago. Updated over 7 years ago.

Status:
Closed
Priority:
Low
Assignee:
Category:
-
Target version:
-
Start date:
03/17/2016
Due date:
% Done:

0%

Spec Reference:

Description

Right now we receive the messages between the IPAC_CRCX and the IPAC_MDCX. In the time in between, the stack attempts
to send RTP/UDP messages to an unknown / non-existant UDP port (portnumber 0):

<0000> rsl.c:1266 (bts=0,trx=0,ts=1,ss=0) RSL Tx IPAC_CRCX_ACK (local 127.0.0.1:61008, remote 127.0.0.1:0)

Once the MDCX is received to set the remote UDP port, the messages disappear.

We should find a way to either not send any packets until the port number is !=, or to suppress the error messages, as they confuse the user.

Actions #1

Updated by msuraev almost 8 years ago

  • Assignee set to msuraev

Might be related to #1661

Actions #2

Updated by msuraev almost 8 years ago

  • Status changed from New to Feedback
  • Assignee changed from msuraev to laforge

Should be fixed by e54d7bcef534461f794f98fa186f8afd8f8c318d in libosmo-abis

Actions #3

Updated by laforge over 7 years ago

  • Status changed from Feedback to Closed
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)