Environment
SCTP 2.0.18
Scenario
The stack is used to serve a diameter "server" stack (jDiameter). The remote node is requesting following stream setup during INIT:
Number of outbound streams: 17 Number of inbound streams: 17
Our response in the INIT_ACK:
Number of outbound streams: 10 Number of inbound streams: 17
Diameter CER/CEA is exchanged successfully and association/peer is considered open.
Expected result
Association should be remain available.
Actual result
After 10 (remote originated) messages the remote stack drops the association (SCTP ABORT). The reason is that our application stops responding to diameter the keep-alive request (Device-Watchdog-Request) because the SCTP stack refuses to send out a packet using stream ID 10.
It seems that the remote node considers SID 10 to be valid but our SCTP doesn't? The check in question is found in org.mobicents.protocols.sctp.AssociationImpl.java:625.
Environment
SCTP 2.0.18
Scenario
The stack is used to serve a diameter "server" stack (jDiameter). The remote node is requesting following stream setup during
INIT:Number of outbound streams: 17 Number of inbound streams: 17Our response in the
INIT_ACK:Number of outbound streams: 10 Number of inbound streams: 17Diameter CER/CEA is exchanged successfully and association/peer is considered open.
Expected result
Association should be remain available.
Actual result
After 10 (remote originated) messages the remote stack drops the association (SCTP ABORT). The reason is that our application stops responding to diameter the keep-alive request (Device-Watchdog-Request) because the SCTP stack refuses to send out a packet using stream ID 10.
It seems that the remote node considers SID 10 to be valid but our SCTP doesn't? The check in question is found in
org.mobicents.protocols.sctp.AssociationImpl.java:625.