mobicents-all-issues-changes  

Messages by Thread

• • Re: Issue 153 in sipservlets: SIP Outbound (RFC 5626) broken for target refresh sipservlets
  • Re: Issue 153 in sipservlets: SIP Outbound (RFC 5626) broken for target refresh sipservlets
  • Re: Issue 153 in sipservlets: SIP Outbound (RFC 5626) broken for target refresh sipservlets
  • Re: Issue 153 in sipservlets: SIP Outbound (RFC 5626) broken for target refresh sipservlets
  • Re: Issue 153 in sipservlets: SIP Outbound (RFC 5626) broken for target refresh sipservlets
  • Re: Issue 153 in sipservlets: SIP Outbound (RFC 5626) broken for target refresh sipservlets
  • Re: Issue 153 in sipservlets: SIP Outbound (RFC 5626) broken for target refresh sipservlets
• Issue 243 in sipservlets: MSS_2X - missing tomcat-7 server.xml, making it harder to build a new MSS release for Tomcat 7 sipservlets
  • Re: Issue 243 in sipservlets: MSS_2X - missing tomcat-7 server.xml, making it harder to build a new MSS release for Tomcat 7 sipservlets
• Issue 242 in sipservlets: The source encoding is not specified in the root pom.xml, which can cause maven to bail out because the build becomes platform dependent sipservlets
  • Re: Issue 242 in sipservlets: The source encoding is not specified in the root pom.xml, which can cause maven to bail out because the build becomes platform dependent sipservlets
  • Re: Issue 242 in sipservlets: The source encoding is not specified in the root pom.xml, which can cause maven to bail out because the build becomes platform dependent sipservlets
  • Re: Issue 242 in sipservlets: The source encoding is not specified in the root pom.xml, which can cause maven to bail out because the build becomes platform dependent sipservlets
  • Re: Issue 242 in sipservlets: The source encoding is not specified in the root pom.xml, which can cause maven to bail out because the build becomes platform dependent sipservlets
• Issue 241 in sipservlets: Security domain in ear sipservlets
  • Re: Issue 241 in sipservlets: Security domain in ear sipservlets
  • Re: Issue 241 in sipservlets: Security domain in ear sipservlets
  • Re: Issue 241 in sipservlets: Security domain in ear sipservlets
• Issue 240 in sipservlets: EJBAccessException sipservlets
  • Re: Issue 240 in sipservlets: EJBAccessException sipservlets
  • Re: Issue 240 in sipservlets: EJBAccessException sipservlets
  • Re: Issue 240 in sipservlets: EJBAccessException sipservlets
  • Re: Issue 240 in sipservlets: EJBAccessException sipservlets
• Issue 328 in jss7: JSS7 MapProviderImpl NullPointer Exception jss7
  • Re: Issue 328 in jss7: JSS7 MapProviderImpl NullPointer Exception jss7
  • Re: Issue 328 in jss7: JSS7 MapProviderImpl NullPointer Exception jss7
  • Re: Issue 328 in jss7: JSS7 MapProviderImpl NullPointer Exception jss7
• Re: Issue 59 in sipservlets: Mutli protocol integration into MSS sipservlets
  • Re: Issue 59 in sipservlets: Mutli protocol integration into MSS sipservlets
• Issue 239 in sipservlets: Proxy-Authenticate and WWW-Authenticate are not Parameterable sipservlets
  • Re: Issue 239 in sipservlets: Proxy-Authenticate and WWW-Authenticate are not Parameterable sipservlets
  • Re: Issue 239 in sipservlets: Proxy-Authenticate and WWW-Authenticate are not Parameterable sipservlets
• Issue 50 in jdiameter: Rx: ClientRxSessionImpl: STA: ClassCastException jdiameter
• 50 issues changed in jss7 jss7
• Issue 327 in jss7: MAP SupplementaryCodeValue values wrong jss7
• Issue 326 in jss7: ISUPMessage.getParameter and similar methods dont work properly jss7
• Issue 49 in jdiameter: TCPTransportClient race condition when closing connecton jdiameter
• Issue 48 in jdiameter: Fix TCPTransportClient for all OS's jdiameter
• Issue 325 in jss7: SCCP configuration persistence breaks service jss7
• Issue 131 in jain-sip: REGISTER Refresh throws Timeout jain-sip
• Issue 324 in jss7: MAP enum BearerServiceCodeValue encoding wrong? jss7
• Issue 130 in jain-sip: rport is present 2 times on 407 Authentication Required jain-sip
  • Re: Issue 130 in jain-sip: rport is present 2 times on 407 Authentication Required jain-sip
• Issue 129 in jain-sip: REGISTER Fails from time to time when using Auth jain-sip
  • Re: Issue 129 in jain-sip: REGISTER Fails from time to time when using Auth jain-sip
  • Re: Issue 129 in jain-sip: REGISTER Fails from time to time when using Auth jain-sip
• Re: Issue 19 in jain-sip: Allows send and receive of keepalives as defined in RFC 5626 jain-sip
  • Re: Issue 19 in jain-sip: Allows send and receive of keepalives as defined in RFC 5626 jain-sip
• Issue 19 in webrtcomm: REGISTER Fails from time to time when using Auth webrtcomm
  • Re: Issue 19 in webrtcomm: REGISTER Fails from time to time when using Auth webrtcomm
• Issue 18 in webrtcomm: SIP MESSAGE sending is not consistent webrtcomm
  • Re: Issue 18 in webrtcomm: SIP MESSAGE sending is not consistent webrtcomm
• Issue 17 in webrtcomm: Authentication of SIP Message is not handled webrtcomm
  • Re: Issue 17 in webrtcomm: Authentication of SIP Message is not handled webrtcomm
• Issue 47 in jdiameter: Automatically configure E-bit when 3000 >= result code < 4000 jdiameter
  • Re: Issue 47 in jdiameter: Automatically configure E-bit when 3000 >= result code < 4000 jdiameter
  • Re: Issue 47 in jdiameter: Automatically configure E-bit when 3000 >= result code < 4000 jdiameter
• Issue 128 in jain-sip: Add Hazelcast cache backend for dialog replication jain-sip
  • Re: Issue 128 in jain-sip: Add Hazelcast cache backend for dialog replication jain-sip
  • Re: Issue 128 in jain-sip: Add Hazelcast cache backend for dialog replication jain-sip
  • Re: Issue 128 in jain-sip: Add Hazelcast cache backend for dialog replication jain-sip
  • Re: Issue 128 in jain-sip: Add Hazelcast cache backend for dialog replication jain-sip
• Issue 98 in jain-slee: SIP-RA leaks when UAS is unavailable jain-slee
  • Re: Issue 98 in jain-slee: SIP-RA leaks when UAS is unavailable jain-slee
  • Re: Issue 98 in jain-slee: SIP-RA leaks when UAS is unavailable jain-slee
  • Re: Issue 98 in jain-slee: SIP-RA leaks when UAS is unavailable jain-slee
• Issue 97 in jain-slee: Diameter Ro RA (server) activities leaking jain-slee
• Issue 16 in webrtcomm: CANCELing a call leads to timeout error on callee side webrtcomm
• Issue 27 in commscale: SNMP adaptor parent's release tag base points to the old source repository commscale
  • Re: Issue 27 in commscale: SNMP adaptor parent's release tag base points to the old source repository commscale
  • Re: Issue 27 in commscale: SNMP adaptor parent's release tag base points to the old source repository commscale
• Issue 15 in webrtcomm: Allow FileSharing using DataChannels webrtcomm
  • Re: Issue 15 in webrtcomm: Allow FileSharing using DataChannels webrtcomm
  • Re: Issue 15 in webrtcomm: Allow FileSharing using DataChannels webrtcomm
  • Re: Issue 15 in webrtcomm: Allow FileSharing using DataChannels webrtcomm
• Issue 14 in webrtcomm: Allow providing of iceServers directly to WebRTComm webrtcomm
  • Re: Issue 14 in webrtcomm: Allow providing of iceServers directly to WebRTComm webrtcomm
  • Re: Issue 14 in webrtcomm: Allow providing of iceServers directly to WebRTComm webrtcomm
  • Re: Issue 14 in webrtcomm: Allow providing of iceServers directly to WebRTComm webrtcomm
  • Re: Issue 14 in webrtcomm: Allow providing of iceServers directly to WebRTComm webrtcomm
• Re: Issue 14 in jain-sip: Memory Leak on TLS Connections when no Certs are installed jain-sip
  • Re: Issue 14 in jain-sip: Memory Leak on TLS Connections when no Certs are installed jain-sip
• Re: Issue 3248 in mobicents: Memory Leak on TLS Connections when no Certs are installed mobicents
• Issue 238 in sipservlets: Proxy transactions are leaking sipservlets
  • Re: Issue 238 in sipservlets: Proxy transactions are leaking sipservlets
  • Re: Issue 238 in sipservlets: Proxy transactions are leaking sipservlets
  • Re: Issue 238 in sipservlets: Proxy transactions are leaking sipservlets
  • Re: Issue 238 in sipservlets: Proxy transactions are leaking sipservlets
• Issue 127 in jain-sip: RE-INVITE request rejected in DialogFiler jain-sip
• Issue 323 in jss7: Bugs in manuals jss7
  • Re: Issue 323 in jss7: Bugs in manuals jss7
• Issue 13 in webrtcomm: New feature: implement RE-INVITE/UPDATE webrtcomm
• Re: Issue 9 in webrtcomm: [feature request] Save webrtcom client configuration in cookies in the test webapp webrtcomm
• Re: Issue 10 in webrtcomm: [feature request] Create a mecanisme to set a listener in webRTCommCall webrtcomm
• Re: Issue 11 in webrtcomm: New feature: use SIP MESSAGE request to send message webrtcomm
  • Re: Issue 11 in webrtcomm: New feature: use SIP MESSAGE request to send message webrtcomm
  • Re: Issue 11 in webrtcomm: New feature: use SIP MESSAGE request to send message webrtcomm
  • Re: Issue 11 in webrtcomm: New feature: use SIP MESSAGE request to send message webrtcomm
  • Re: Issue 11 in webrtcomm: New feature: use SIP MESSAGE request to send message webrtcomm
• Issue 12 in webrtcomm: Proper handling of 407 Proxy Authentication challenge for REGISTER webrtcomm
  • Re: Issue 12 in webrtcomm: Proper handling of 407 Proxy Authentication challenge for REGISTER webrtcomm
  • Re: Issue 12 in webrtcomm: Proper handling of 407 Proxy Authentication challenge for REGISTER webrtcomm
  • Re: Issue 12 in webrtcomm: Proper handling of 407 Proxy Authentication challenge for REGISTER webrtcomm
• Issue 237 in sipservlets: App name resolution problem on error response's ACK sipservlets
  • Re: Issue 237 in sipservlets: App name resolution problem on error response's ACK sipservlets
  • Re: Issue 237 in sipservlets: App name resolution problem on error response's ACK sipservlets
  • Re: Issue 237 in sipservlets: App name resolution problem on error response's ACK sipservlets
  • Re: Issue 237 in sipservlets: App name resolution problem on error response's ACK sipservlets
  • Re: Issue 237 in sipservlets: App name resolution problem on error response's ACK sipservlets
  • Re: Issue 237 in sipservlets: App name resolution problem on error response's ACK sipservlets
  • Re: Issue 237 in sipservlets: App name resolution problem on error response's ACK sipservlets
• Issue 322 in jss7: Adding "name" property into TCAP, TCAP-ANSI, MAP, CAP stackes jss7
  • Re: Issue 322 in jss7: Adding "name" property into TCAP, TCAP-ANSI, MAP, CAP stackes jss7
  • Re: Issue 322 in jss7: Adding "name" property into TCAP, TCAP-ANSI, MAP, CAP stackes jss7
  • Re: Issue 322 in jss7: Adding "name" property into TCAP, TCAP-ANSI, MAP, CAP stackes jss7
• Issue 126 in jain-sip: SIP stack stops responding, for even small load test jain-sip
  • Re: Issue 126 in jain-sip: SIP stack stops responding, for even small load test jain-sip
  • Re: Issue 126 in jain-sip: SIP stack stops responding, for even small load test jain-sip
• Issue 4 in isup2sip: Fill SLS value when CIC is filled isup2sip
• Issue 5 in isup2sip: Check memory leackage isup2sip
• Issue 3 in isup2sip: support multiplex management by means of CLI/configuration files isup2sip
• Issue 1 in isup2sip: Startup procedure - MGCP and ISUP, detecting and resetting channels isup2sip
• Issue 2 in isup2sip: A proper RSIP support for a card isup2sip
• Issue 321 in jss7: Adding support to SS7 Simulator for EIR testing jss7
• Issue 125 in jain-sip: RoundRobinLoadBalancerElector removeLoadBalancerMethod fails jain-sip
  • Re: Issue 125 in jain-sip: RoundRobinLoadBalancerElector removeLoadBalancerMethod fails jain-sip
  • Re: Issue 125 in jain-sip: RoundRobinLoadBalancerElector removeLoadBalancerMethod fails jain-sip
• Issue 124 in jain-sip: RoundRobinLoadBalancerElector is not thread safe jain-sip
• Issue 320 in jss7: Perform address screening jss7
  • Re: Issue 320 in jss7: Perform address screening jss7
• Issue 319 in jss7: ISUP tests dont reuse common framework jss7
  • Re: Issue 319 in jss7: ISUP tests dont reuse common framework jss7
  • Re: Issue 319 in jss7: ISUP tests dont reuse common framework jss7
• Issue 3276 in mobicents: Remove Destination host in CCR Request mobicents
  • Re: Issue 3276 in mobicents: Remove Destination host in CCR Request mobicents
• Issue 3275 in mobicents: Unknown realm mobicents
• Issue 318 in jss7: Adding statistic support into TCAP (and TCAP-ANSI) stacks jss7
  • Re: Issue 318 in jss7: Adding statistic support into TCAP (and TCAP-ANSI) stacks jss7
  • Re: Issue 318 in jss7: Adding statistic support into TCAP (and TCAP-ANSI) stacks jss7
  • Re: Issue 318 in jss7: Adding statistic support into TCAP (and TCAP-ANSI) stacks jss7
  • Re: Issue 318 in jss7: Adding statistic support into TCAP (and TCAP-ANSI) stacks jss7
  • Re: Issue 318 in jss7: Adding statistic support into TCAP (and TCAP-ANSI) stacks jss7
• [no subject] Michael Burns
• Issue 123 in jain-sip: CANCELling a call displays JAINSIPJS Error jain-sip
  • Re: Issue 123 in jain-sip: CANCELling a call displays JAINSIPJS Error jain-sip
• Issue 317 in jss7: Components - ie. invoke ID etc may have wrong tag class jss7
  • Re: Issue 317 in jss7: Components - ie. invoke ID etc may have wrong tag class jss7
  • Re: Issue 317 in jss7: Components - ie. invoke ID etc may have wrong tag class jss7
• Issue 316 in jss7: TCAP ErrorCode is not encoded properly jss7
  • Re: Issue 316 in jss7: TCAP ErrorCode is not encoded properly jss7
  • Re: Issue 316 in jss7: TCAP ErrorCode is not encoded properly jss7
• Issue 236 in sipservlets: NullPointerException when calling SipServletRequestImpl.send() with bad sip URI sipservlets
  • Re: Issue 236 in sipservlets: NullPointerException when calling SipServletRequestImpl.send() with bad sip URI sipservlets
  • Re: Issue 236 in sipservlets: NullPointerException when calling SipServletRequestImpl.send() with bad sip URI sipservlets
  • Re: Issue 236 in sipservlets: NullPointerException when calling SipServletRequestImpl.send() with bad sip URI sipservlets
• Issue 315 in jss7: NPE in UnstructuredSSResponse jss7
  • Re: Issue 315 in jss7: NPE in UnstructuredSSResponse jss7
  • Re: Issue 315 in jss7: NPE in UnstructuredSSResponse jss7
  • Re: Issue 315 in jss7: NPE in UnstructuredSSResponse jss7
• Issue 314 in jss7: M3UA AspFactory is not correctly handling SCTP Restart jss7
  • Re: Issue 314 in jss7: M3UA AspFactory is not correctly handling SCTP Restart jss7
  • Re: Issue 314 in jss7: M3UA AspFactory is not correctly handling SCTP Restart jss7
• Issue 96 in jain-slee: MAP RA : NPE when creating entity from management console jain-slee
• Issue 95 in jain-slee: NPE thrown when accessing EventRouterStatistics when statistics are disabled jain-slee
  • Re: Issue 95 in jain-slee: NPE thrown when accessing EventRouterStatistics when statistics are disabled jain-slee
  • Re: Issue 95 in jain-slee: NPE thrown when accessing EventRouterStatistics when statistics are disabled jain-slee
• Issue 313 in jss7: SccpStack interface not exposing setMtp3UserPart jss7
  • Re: Issue 313 in jss7: SccpStack interface not exposing setMtp3UserPart jss7
  • Re: Issue 313 in jss7: SccpStack interface not exposing setMtp3UserPart jss7
• Re: Issue 95 in sipservlets: Bundle SNMP MIB Generator jar in TelScale distribution sipservlets
• Issue 235 in sipservlets: JBoss AS7 - jain-sip libraries should be available as global-module sipservlets
  • Re: Issue 235 in sipservlets: JBoss AS7 - jain-sip libraries should be available as global-module sipservlets
  • Re: Issue 235 in sipservlets: JBoss AS7 - jain-sip libraries should be available as global-module sipservlets
• Issue 234 in sipservlets: WebRTC application is not using STUN and does not allow TURN server sipservlets
  • Re: Issue 234 in sipservlets: WebRTC application is not using STUN and does not allow TURN server sipservlets
  • Re: Issue 234 in sipservlets: WebRTC application is not using STUN and does not allow TURN server sipservlets
• Issue 132 in mediaserver: UdpManager getHighestPort() bug mediaserver
• Issue 131 in mediaserver: UdpManager getHighestPort() bug mediaserver
• Issue 122 in jain-sip: StringMsgParser exception jain-sip
  • Re: Issue 122 in jain-sip: StringMsgParser exception jain-sip
  • Re: Issue 122 in jain-sip: StringMsgParser exception jain-sip
• Issue 121 in jain-sip: JBoss AS7 SIPNode doesn't advertise the http port to the LoadBalancer jain-sip
  • Re: Issue 121 in jain-sip: JBoss AS7 SIPNode doesn't advertise the http port to the LoadBalancer jain-sip
• Issue 233 in sipservlets: JBoss AS7 SIPNode doesn't advertise the http port to the LoadBalancer sipservlets
  • Re: Issue 233 in sipservlets: JBoss AS7 SIPNode doesn't advertise the http port to the LoadBalancer sipservlets
  • Re: Issue 233 in sipservlets: JBoss AS7 SIPNode doesn't advertise the http port to the LoadBalancer sipservlets
• Issue 46 in jdiameter: Support for more local interfaces jdiameter
  • Re: Issue 46 in jdiameter: Support for more local interfaces jdiameter
  • Re: Issue 46 in jdiameter: Support for more local interfaces jdiameter
  • Re: Issue 46 in jdiameter: Support for more local interfaces jdiameter
• Issue 312 in jss7: CAP InitialDP empty (zero length) IMSI jss7
  • Re: Issue 312 in jss7: CAP InitialDP empty (zero length) IMSI jss7
  • Re: Issue 312 in jss7: CAP InitialDP empty (zero length) IMSI jss7
  • Re: Issue 312 in jss7: CAP InitialDP empty (zero length) IMSI jss7
  • Re: Issue 312 in jss7: CAP InitialDP empty (zero length) IMSI jss7
  • Re: Issue 312 in jss7: CAP InitialDP empty (zero length) IMSI jss7
  • Re: Issue 312 in jss7: CAP InitialDP empty (zero length) IMSI jss7
  • Re: Issue 312 in jss7: CAP InitialDP empty (zero length) IMSI jss7
  • Re: Issue 312 in jss7: CAP InitialDP empty (zero length) IMSI jss7
  • Re: Issue 312 in jss7: CAP InitialDP empty (zero length) IMSI jss7

• Earlier messages
• Later messages