mobicents-all-issues-changes  

Messages by Thread

• • Re: Issue 142 in jain-sip: DisabledAll TLS check ClientAuthType property is failing on NIO jain-sip
• Issue 281 in sipservlets: Revamp WebRTC Application sipservlets
  • Re: Issue 281 in sipservlets: Revamp WebRTC Application sipservlets
  • Re: Issue 281 in sipservlets: Revamp WebRTC Application sipservlets
  • Re: Issue 281 in sipservlets: Revamp WebRTC Application sipservlets
  • Re: Issue 281 in sipservlets: Revamp WebRTC Application Kamil Mohamed
  • Re: Issue 281 in sipservlets: Revamp WebRTC Application sipservlets
  • Re: Issue 281 in sipservlets: Revamp WebRTC Application sipservlets
  • Re: Issue 281 in sipservlets: Revamp WebRTC Application sipservlets
• Issue 141 in jain-sip: NIO_MAX_SOCKET_IDLE_TIME is not used for server sockets jain-sip
  • Re: Issue 141 in jain-sip: NIO_MAX_SOCKET_IDLE_TIME is not used for server sockets jain-sip
  • Re: Issue 141 in jain-sip: NIO_MAX_SOCKET_IDLE_TIME is not used for server sockets jain-sip
  • Re: Issue 141 in jain-sip: NIO_MAX_SOCKET_IDLE_TIME is not used for server sockets jain-sip
  • Re: Issue 141 in jain-sip: NIO_MAX_SOCKET_IDLE_TIME is not used for server sockets jain-sip
  • Re: Issue 141 in jain-sip: NIO_MAX_SOCKET_IDLE_TIME is not used for server sockets jain-sip
• Issue 280 in sipservlets: javax.sip.TransactionUnavailableException: Transaction not available -- could not acquire stack lock sipservlets
  • Re: Issue 280 in sipservlets: javax.sip.TransactionUnavailableException: Transaction not available -- could not acquire stack lock sipservlets
  • Re: Issue 280 in sipservlets: javax.sip.TransactionUnavailableException: Transaction not available -- could not acquire stack lock sipservlets
  • Re: Issue 280 in sipservlets: javax.sip.TransactionUnavailableException: Transaction not available -- could not acquire stack lock sipservlets
• Issue 279 in sipservlets: IllegalStateException on Proxy Derived Session Invalidation sipservlets
  • Re: Issue 279 in sipservlets: IllegalStateException on Proxy Derived Session Invalidation sipservlets
  • Re: Issue 279 in sipservlets: IllegalStateException on Proxy Derived Session Invalidation sipservlets
• Issue 278 in sipservlets: SDP on First Challenged INVITE is not null sipservlets
  • Re: Issue 278 in sipservlets: SDP on First Challenged INVITE is not null sipservlets
  • Re: Issue 278 in sipservlets: SDP on First Challenged INVITE is not null sipservlets
• Issue 140 in jain-sip: Create Android version of jars created by the ant or maven script jain-sip
  • Re: Issue 140 in jain-sip: Create Android version of jars created by the ant or maven script jain-sip
  • Re: Issue 140 in jain-sip: Create Android version of jars created by the ant or maven script jain-sip
• Issue 277 in sipservlets: Applications somtimes fail to deploy on MSS AS7.2.0.Final version sipservlets
  • Re: Issue 277 in sipservlets: Applications somtimes fail to deploy on MSS AS7.2.0.Final version sipservlets
  • Re: Issue 277 in sipservlets: Applications somtimes fail to deploy on MSS AS7.2.0.Final version sipservlets
  • Re: Issue 277 in sipservlets: Applications somtimes fail to deploy on MSS AS7.2.0.Final version sipservlets
• Issue 109 in jain-slee: Invalid method signature generated when adding ACI interface to an existing SBB jain-slee
• 4 issues changed in sipservlets sipservlets
• Issue 276 in sipservlets: Via Header used instead of Contact Header for ReINVITE (from callee to caller) proxying sipservlets
  • Re: Issue 276 in sipservlets: Via Header used instead of Contact Header for ReINVITE (from callee to caller) proxying sipservlets
  • Re: Issue 276 in sipservlets: Via Header used instead of Contact Header for ReINVITE (from callee to caller) proxying sipservlets
  • Re: Issue 276 in sipservlets: Via Header used instead of Contact Header for ReINVITE (from callee to caller) proxying sipservlets
• Issue 275 in sipservlets: NOTIFY not handled if answer of SUBSCRIBE not received. sipservlets
  • Re: Issue 275 in sipservlets: NOTIFY not handled if answer of SUBSCRIBE not received. sipservlets
  • Re: Issue 275 in sipservlets: NOTIFY not handled if answer of SUBSCRIBE not received. sipservlets
• Issue 274 in sipservlets: Record-Route header not added in outgoing Re-INVITE. sipservlets
  • Re: Issue 274 in sipservlets: Record-Route header not added in outgoing Re-INVITE. sipservlets
  • Re: Issue 274 in sipservlets: Record-Route header not added in outgoing Re-INVITE. sipservlets
• Issue 3278 in mobicents: Possible to configure multiple links for SCTP communication on diameter? mobicents
• Issue 273 in sipservlets: PRACK not seen on second application when proxying to same application with different routing regions sipservlets
  • Re: Issue 273 in sipservlets: PRACK not seen on second application when proxying to same application with different routing regions sipservlets
  • Re: Issue 273 in sipservlets: PRACK not seen on second application when proxying to same application with different routing regions sipservlets
  • Re: Issue 273 in sipservlets: PRACK not seen on second application when proxying to same application with different routing regions sipservlets
• Issue 272 in sipservlets: ReasonHeader is not forwarded sipservlets
  • Re: Issue 272 in sipservlets: ReasonHeader is not forwarded sipservlets
  • Re: Issue 272 in sipservlets: ReasonHeader is not forwarded sipservlets
  • Re: Issue 272 in sipservlets: ReasonHeader is not forwarded sipservlets
• Issue 271 in sipservlets: Memory leaks in Mobicents Sip stack sipservlets
  • Re: Issue 271 in sipservlets: Memory leaks in Mobicents Sip stack sipservlets
  • Re: Issue 271 in sipservlets: Memory leaks in Mobicents Sip stack sipservlets
  • Re: Issue 271 in sipservlets: Memory leaks in Mobicents Sip stack sipservlets
  • Re: Issue 271 in sipservlets: Memory leaks in Mobicents Sip stack sipservlets
  • Re: Issue 271 in sipservlets: Memory leaks in Mobicents Sip stack sipservlets
  • Re: Issue 271 in sipservlets: Memory leaks in Mobicents Sip stack sipservlets
  • Re: Issue 271 in sipservlets: Memory leaks in Mobicents Sip stack sipservlets
  • Re: Issue 271 in sipservlets: Memory leaks in Mobicents Sip stack sipservlets
  • Re: Issue 271 in sipservlets: Memory leaks in Mobicents Sip stack sipservlets
  • Re: Issue 271 in sipservlets: Memory leaks in Mobicents Sip stack sipservlets
  • Re: Issue 271 in sipservlets: Memory leaks in Mobicents Sip stack sipservlets
  • Re: Issue 271 in sipservlets: Memory leaks in Mobicents Sip stack sipservlets
• Issue 139 in jain-sip: Incoming messages are not correctly parsed under turkish locale jain-sip
  • Re: Issue 139 in jain-sip: Incoming messages are not correctly parsed under turkish locale jain-sip
• Issue 138 in jain-sip: Non TLS Connection to TLS Listening Point hang jain-sip
  • Re: Issue 138 in jain-sip: Non TLS Connection to TLS Listening Point hang jain-sip
• Issue 64 in jdiameter: IllegalStateException thrown when there are retransmissions in cluster mode jdiameter
  • Re: Issue 64 in jdiameter: IllegalStateException thrown when there are retransmissions in cluster mode jdiameter
  • Re: Issue 64 in jdiameter: IllegalStateException thrown when there are retransmissions in cluster mode jdiameter
  • Re: Issue 64 in jdiameter: IllegalStateException thrown when there are retransmissions in cluster mode jdiameter
• Issue 137 in jain-sip: Invalid websocket handshake response in case of fragmentation of request HTTP message jain-sip
  • Re: Issue 137 in jain-sip: Invalid websocket handshake response in case of fragmentation of request HTTP message jain-sip
• Issue 108 in jain-slee: Update EclipSLEE nightly build location in the User Guide jain-slee
  • Re: Issue 108 in jain-slee: Update EclipSLEE nightly build location in the User Guide jain-slee
• Issue 107 in jain-slee: SIP RA: B2BUA engine bad forwarding requests sent by second leg jain-slee
  • Re: Issue 107 in jain-slee: SIP RA: B2BUA engine bad forwarding requests sent by second leg jain-slee
• Re: Issue 59 in jdiameter: jDiameter should be able to wait for a period before binding to port jdiameter
  • Re: Issue 59 in jdiameter: jDiameter should be able to wait for a period before binding to port jdiameter
  • Re: Issue 59 in jdiameter: jDiameter should be able to wait for a period before binding to port jdiameter
  • Re: Issue 59 in jdiameter: jDiameter should be able to wait for a period before binding to port jdiameter
  • Re: Issue 59 in jdiameter: jDiameter should be able to wait for a period before binding to port jdiameter
• Issue 63 in jdiameter: Detect Answers without Result-Code or Experimental-Result-Code AVP jdiameter
• Re: Issue 48 in jdiameter: Fix TCPTransportClient for all OS's for detecting closed connections jdiameter
  • Re: Issue 48 in jdiameter: Fix TCPTransportClient for all OS's for detecting closed connections jdiameter
• Issue 62 in jdiameter: Number of threads keeps on increasing during stack start and stop jdiameter
  • Re: Issue 62 in jdiameter: Number of threads keeps on increasing during stack start and stop jdiameter
  • Re: Issue 62 in jdiameter: Number of threads keeps on increasing during stack start and stop jdiameter
  • Re: Issue 62 in jdiameter: Number of threads keeps on increasing during stack start and stop jdiameter
• Issue 136 in jain-sip: Large expire values cause IllegalArgumentException jain-sip
  • Re: Issue 136 in jain-sip: Large expire values cause IllegalArgumentException jain-sip
  • Re: Issue 136 in jain-sip: Large expire values cause IllegalArgumentException jain-sip
  • Re: Issue 136 in jain-sip: Large expire values cause IllegalArgumentException jain-sip
• Issue 333 in jss7: MAP: MAPDialogState=INITIAL_RECEIVED not handled correctly jss7
• Issue 106 in jain-slee: Exposing counter type usage parameters as JMX attributes jain-slee
  • Re: Issue 106 in jain-slee: Exposing counter type usage parameters as JMX attributes jain-slee
  • Re: Issue 106 in jain-slee: Exposing counter type usage parameters as JMX attributes jain-slee
  • Re: Issue 106 in jain-slee: Exposing counter type usage parameters as JMX attributes jain-slee
• Issue 61 in jdiameter: Diameter s6a ActivityIsEndingException for answers jdiameter
• Issue 135 in jain-sip: NullPointerExceptions - CommonLogger.legacyLogger is not thread-safe jain-sip
• Issue 135 in mediaserver: [JSR309 Driver] Request identifier overflow. mediaserver
• Issue 21 in webrtcomm: Firefox and Chrome incompatibilities webrtcomm
  • Re: Issue 21 in webrtcomm: Firefox and Chrome incompatibilities webrtcomm
  • Re: Issue 21 in webrtcomm: Firefox and Chrome incompatibilities webrtcomm
• Issue 134 in jain-sip: JainSIP JS : SIPTransaction state issue jain-sip
  • Re: Issue 134 in jain-sip: JainSIP JS : SIPTransaction state issue jain-sip
  • Re: Issue 134 in jain-sip: JainSIP JS : SIPTransaction state issue jain-sip
• Issue 332 in jss7: jss7 is not compiled on my machine required simulator-ss7? jss7
• Issue 3277 in mobicents: doCreditControlAnswer don't start after server response mobicents
• Issue 26 in commtesting: Send body in register message. commtesting
• Issue 60 in jdiameter: jDiameter statistics sometimes become null causing peer connection failure jdiameter
  • Re: Issue 60 in jdiameter: jDiameter statistics sometimes become null causing peer connection failure jdiameter
• Issue 59 in jdiameter: jDiameter should wait 60 seconds before binding to port jdiameter
  • Re: Issue 59 in jdiameter: jDiameter should wait 60 seconds before binding to port jdiameter
• Issue 58 in jdiameter: JDiameter replace getHostName with getHostString jdiameter
  • Re: Issue 58 in jdiameter: JDiameter replace getHostName with getHostString jdiameter
• Issue 270 in sipservlets: Event header is modified by B2buaHelper for NOTIFY requests sipservlets
  • Re: Issue 270 in sipservlets: Event header is modified by B2buaHelper for NOTIFY requests sipservlets
• Issue 105 in jain-slee: Wrong encoding of msisdn in UserIdentityAvp (expected TBCD) jain-slee
• Issue 104 in jain-slee: Failed to unmarshal User-Data AVP into JAXB Object jain-slee
• Issue 25 in commtesting: sendRequestWithTransaction() causes subsequent waitForDisconnect() to timeout. commtesting
• Issue 57 in jdiameter: Unstable connection establishment in some scenarios jdiameter
• Issue 103 in jain-slee: Client transactions not removed on Dialog.delete(). jain-slee
  • Re: Issue 103 in jain-slee: Client transactions not removed on Dialog.delete(). jain-slee
  • Re: Issue 103 in jain-slee: Client transactions not removed on Dialog.delete(). jain-slee
  • Re: Issue 103 in jain-slee: Client transactions not removed on Dialog.delete(). jain-slee
• Issue 269 in sipservlets: createBranch for a new SIP Request sipservlets
  • Re: Issue 269 in sipservlets: createBranch for a new SIP Request sipservlets
  • Re: Issue 269 in sipservlets: createBranch for a new SIP Request sipservlets
• Re: Issue 133 in sipservlets: Extract client and annotations modules from libs module in AS7 sipservlets
• Issue 133 in jain-sip: Cannot add multiple reason headers jain-sip
  • Re: Issue 133 in jain-sip: Cannot add multiple reason headers jain-sip
  • Re: Issue 133 in jain-sip: Cannot add multiple reason headers jain-sip
• Re: Issue 170 in sipservlets: Trailing '=' character added to flag parameters in URIs sipservlets
  • Re: Issue 170 in sipservlets: Trailing '=' character added to flag parameters in URIs sipservlets
• Issue 268 in sipservlets: SipServletMessage.addHeader handles transport badly sipservlets
  • Re: Issue 268 in sipservlets: SipServletMessage.addHeader handles transport badly sipservlets
• Issue 267 in sipservlets: NPE when sending a CANCEL sipservlets
  • Re: Issue 267 in sipservlets: NPE when sending a CANCEL sipservlets
  • Re: Issue 267 in sipservlets: NPE when sending a CANCEL sipservlets
  • Re: Issue 267 in sipservlets: NPE when sending a CANCEL sipservlets
  • Re: Issue 267 in sipservlets: NPE when sending a CANCEL sipservlets
  • Re: Issue 267 in sipservlets: NPE when sending a CANCEL sipservlets
  • Re: Issue 267 in sipservlets: NPE when sending a CANCEL sipservlets
  • Re: Issue 267 in sipservlets: NPE when sending a CANCEL sipservlets
  • Re: Issue 267 in sipservlets: NPE when sending a CANCEL sipservlets
  • Re: Issue 267 in sipservlets: NPE when sending a CANCEL sipservlets
  • Re: Issue 267 in sipservlets: NPE when sending a CANCEL sipservlets
• Re: Issue 169 in sipservlets: ClassCastException in SipServletMessageImpl.setContent() sipservlets
  • Re: Issue 169 in sipservlets: ClassCastException in SipServletMessageImpl.setContent() sipservlets
  • Re: Issue 169 in sipservlets: ClassCastException in SipServletMessageImpl.setContent() sipservlets
• Re: Issue 2912 in mobicents: MSS 1.7 doesn't allow changing To header after first proxy branch mobicents
• Re: Issue 24 in sipservlets: Allow changing To header after first proxy branch sipservlets
  • Re: Issue 24 in sipservlets: Allow changing To header after first proxy branch sipservlets
• Re: Issue 7 in sipservlets: Cancelled transaction leaks for proxy MSS sipservlets
• Re: Issue 171 in sipservlets: createApplicationSession() does not create new session if the http session has already one associated. sipservlets
• Re: Issue 154 in sipservlets: Proxy implementation not forwarding additional 2xx responses from downstream fork (again) sipservlets
  • Re: Issue 154 in sipservlets: Proxy implementation not forwarding additional 2xx responses from downstream fork (again) sipservlets
  • Re: Issue 154 in sipservlets: Proxy implementation not forwarding additional 2xx responses from downstream fork (again) sipservlets
  • Re: Issue 154 in sipservlets: Proxy implementation not forwarding additional 2xx responses from downstream fork (again) sipservlets
• Re: Issue 137 in sipservlets: getRemoteAddr() for locally-generated message is not null sipservlets
  • Re: Issue 137 in sipservlets: getRemoteAddr() for locally-generated message is not null sipservlets
• Re: Issue 139 in sipservlets: @SipApplicationKey fails on Tomcat if not defined on the servlet class sipservlets
  • Re: Issue 139 in sipservlets: @SipApplicationKey fails on Tomcat if not defined on the servlet class sipservlets
  • Re: Issue 139 in sipservlets: @SipApplicationKey fails on Tomcat if not defined on the servlet class sipservlets
• Re: Issue 106 in sipservlets: defining any context-param in web.xml results in a "Duplicate context initialization parameter" IllegalArgumentException. sipservlets
• Re: Issue 3155 in mobicents: Enhancement (no defect): Consider adding popped route in DefaultApplicationRouter Regular Expression match mobicents
• Re: Issue 43 in sipservlets: Add popped route in DefaultApplicationRouter Regular Expression match sipservlets
  • Re: Issue 43 in sipservlets: Add popped route in DefaultApplicationRouter Regular Expression match sipservlets
• Re: Issue 132 in sipservlets: Mobicents SIP Servlet generating IllegalstateException sipservlets
  • Re: Issue 132 in sipservlets: Mobicents SIP Servlet generating IllegalstateException sipservlets
• Re: Issue 38 in sipservlets: JNDI resources overwritten when new app is deployed sipservlets
• Re: Issue 3105 in mobicents: IllegalStateException if class with @SipApplicationKey annotation is subclassed mobicents
• Re: Issue 37 in sipservlets: IllegalStateException if class with @SipApplicationKey annotation is subclassed sipservlets
  • Re: Issue 37 in sipservlets: IllegalStateException if class with @SipApplicationKey annotation is subclassed sipservlets
• Re: Issue 35 in sipservlets: MSS do not invalidate the SipSession when receiving CANCEL sipservlets
  • Re: Issue 35 in sipservlets: MSS do not invalidate the SipSession when receiving CANCEL sipservlets
• Re: Issue 3064 in mobicents: Session.setOutboundInterface not working on B2BUA mobicents
• Re: Issue 164 in sipservlets: CANCEL not proxied after INVITE sipservlets
• Re: Issue 2905 in mobicents: MSS 1.7 throws exception when processing certain ACKs after proxying error response mobicents
  • Re: Issue 2905 in mobicents: MSS 1.7 throws exception when processing certain ACKs after proxying error response mobicents
  • Re: Issue 2905 in mobicents: MSS 1.7 throws exception when processing certain ACKs after proxying error response mobicents
• Re: Issue 22 in sipservlets: Exception when processing certain ACKs after proxying error response sipservlets
  • Re: Issue 22 in sipservlets: Exception when processing certain ACKs after proxying error response sipservlets
  • Re: Issue 22 in sipservlets: Exception when processing certain ACKs after proxying error response sipservlets
  • Re: Issue 22 in sipservlets: Exception when processing certain ACKs after proxying error response sipservlets
  • Re: Issue 22 in sipservlets: Exception when processing certain ACKs after proxying error response sipservlets
  • Re: Issue 22 in sipservlets: Exception when processing certain ACKs after proxying error response sipservlets
• Re: Issue 72 in sipservlets: May 2014 sipservlets
  • Re: Issue 72 in sipservlets: May 2014 sipservlets
• Re: Issue 2893 in mobicents: MSS: subsequent requests are proxied even if final response was generated by application mobicents
  • Re: Issue 2893 in mobicents: MSS: subsequent requests are proxied even if final response was generated by application mobicents
  • Re: Issue 2893 in mobicents: MSS: subsequent requests are proxied even if final response was generated by application mobicents
  • Re: Issue 2893 in mobicents: MSS: subsequent requests are proxied even if final response was generated by application mobicents
• Re: Issue 21 in sipservlets: Subsequent requests are proxied even if final response was generated by application sipservlets
  • Re: Issue 21 in sipservlets: Subsequent requests are proxied even if final response was generated by application sipservlets
  • Re: Issue 21 in sipservlets: Subsequent requests are proxied even if final response was generated by application sipservlets

• Earlier messages
• Later messages