mobicents-all-issues-changes  

Messages by Thread

• Re: Issue 25 in sipservlets: SNMP OID entries(notification) are not validated against existing ones. sipservlets
• Re: Issue 2892 in mobicents: outbound transport not detected correctly when proxying with Route headers mobicents
• Re: Issue 20 in sipservlets: Outbound transport not detected correctly when proxying with Route headers sipservlets
  • Re: Issue 20 in sipservlets: Outbound transport not detected correctly when proxying with Route headers sipservlets
  • Re: Issue 20 in sipservlets: Outbound transport not detected correctly when proxying with Route headers sipservlets
• Re: Issue 13 in sipservlets: Request.send alters the hostname of Contact field in REGISTER requests sipservlets
• Issue 266 in sipservlets: Cancel not forwarded to proxy branches after final reponse sipservlets
  • Re: Issue 266 in sipservlets: Cancel not forwarded to proxy branches after final reponse sipservlets
  • Re: Issue 266 in sipservlets: Cancel not forwarded to proxy branches after final reponse sipservlets
• Issue 15 in ussdgateway: while setting up ussd Gateway,finding error for mvn clean install -Pjboss ussdgateway
  • Re: Issue 15 in ussdgateway: while setting up ussd Gateway,finding error for mvn clean install -Pjboss ussdgateway
• Re: Issue 94 in sipservlets: Fixing parameter names when using <distributable /> sipservlets
• Re: Issue 1595 in mobicents: Behavior of Proxy and 408 generated by the container mobicents
  • Re: Issue 1595 in mobicents: Behavior of Proxy and 408 generated by the container mobicents
  • Re: Issue 1595 in mobicents: Behavior of Proxy and 408 generated by the container mobicents
• Re: Issue 48 in sipservlets: ClickToCall End to End Example documentation improvement sipservlets
• Re: Issue 1877 in mobicents: End to End Example documentation improvement mobicents
• Re: Issue 26 in sipservlets: SIP Load Balancer Heartbeat isReachable issue sipservlets
• Re: Issue 2958 in mobicents: SIP Load Balancer Heartbeat isReachable issue mobicents
• Re: Issue 3071 in mobicents: CANCEL not proxied by mss after PRACK or UPDATE mobicents
• Re: Issue 33 in sipservlets: CANCEL not proxied by mss after PRACK or UPDATE sipservlets
  • Re: Issue 33 in sipservlets: CANCEL not proxied by mss after PRACK or UPDATE sipservlets
  • Re: Issue 33 in sipservlets: CANCEL not proxied by mss after PRACK or UPDATE sipservlets
• Re: Issue 10 in sipservlets: Mobicents SipServlet hangs under DoS attack sipservlets
• Re: Issue 29 in sipservlets: MSS Not processing CANCEL request sipservlets
• Re: Issue 2975 in mobicents: MSS Not processing CANCEL request mobicents
  • Re: Issue 2975 in mobicents: MSS Not processing CANCEL request mobicents
• Re: Issue 15 in sipservlets: CacheManager does not recognize config null with SipApplication annotation. sipservlets
• Re: Issue 165 in sipservlets: Creating a MESSAGE with a charset=ISO-10646-UCS-2 parameter on Content header corrupts the message sipservlets
  • Re: Issue 165 in sipservlets: Creating a MESSAGE with a charset=ISO-10646-UCS-2 parameter on Content header corrupts the message sipservlets
  • Re: Issue 165 in sipservlets: Creating a MESSAGE with a charset=ISO-10646-UCS-2 parameter on Content header corrupts the message sipservlets
• Issue 265 in sipservlets: Concurrency Issue with Async Queue if parent SAS is not exited sipservlets
  • Re: Issue 265 in sipservlets: Concurrency Issue with Async Queue if parent SAS is not exited sipservlets
  • Re: Issue 265 in sipservlets: Concurrency Issue with Async Queue if parent SAS is not exited sipservlets
  • Re: Issue 265 in sipservlets: Concurrency Issue with Async Queue if parent SAS is not exited sipservlets
• Issue 134 in mediaserver: Mobicents jsr309-driver bug mediaserver
• Issue 264 in sipservlets: SipSessionKey parsing breaks on ":" in CallId sipservlets
  • Re: Issue 264 in sipservlets: SipSessionKey parsing breaks on ":" in CallId sipservlets
  • Re: Issue 264 in sipservlets: SipSessionKey parsing breaks on ":" in CallId sipservlets
• Issue 263 in sipservlets: Container generated 408 for a proxy branch is not treated as a branch response sipservlets
  • Re: Issue 263 in sipservlets: Container generated 408 for a proxy branch is not treated as a branch response sipservlets
  • Re: Issue 263 in sipservlets: Container generated 408 for a proxy branch is not treated as a branch response sipservlets
  • Re: Issue 263 in sipservlets: Container generated 408 for a proxy branch is not treated as a branch response sipservlets
  • Re: Issue 263 in sipservlets: Container generated 408 for a proxy branch is not treated as a branch response sipservlets
  • Re: Issue 263 in sipservlets: Container generated 408 for a proxy branch is not treated as a branch response sipservlets
  • Re: Issue 263 in sipservlets: Container generated 408 for a proxy branch is not treated as a branch response sipservlets
• Issue 331 in jss7: Can not define multi-homed peers jss7
• Issue 56 in jdiameter: Client cannot reconnect after missing few DWA jdiameter
  • Re: Issue 56 in jdiameter: Client cannot reconnect after missing few DWA jdiameter
  • Re: Issue 56 in jdiameter: Client cannot reconnect after missing few DWA jdiameter
  • Re: Issue 56 in jdiameter: Client cannot reconnect after missing few DWA jdiameter
  • Re: Issue 56 in jdiameter: Client cannot reconnect after missing few DWA jdiameter
  • Re: Issue 56 in jdiameter: Client cannot reconnect after missing few DWA jdiameter
  • Re: Issue 56 in jdiameter: Client cannot reconnect after missing few DWA jdiameter
  • Re: Issue 56 in jdiameter: Client cannot reconnect after missing few DWA jdiameter
  • Re: Issue 56 in jdiameter: Client cannot reconnect after missing few DWA jdiameter
  • Re: Issue 56 in jdiameter: Client cannot reconnect after missing few DWA jdiameter
  • Re: Issue 56 in jdiameter: Client cannot reconnect after missing few DWA jdiameter
• Issue 262 in sipservlets: Adds User-Agent Header by default sipservlets
  • Re: Issue 262 in sipservlets: Adds User-Agent Header by default sipservlets
• Publish Your Research Paper gopic
• Issue 261 in sipservlets: bad_record_mac using TLS sipservlets
  • Re: Issue 261 in sipservlets: bad_record_mac using TLS sipservlets
  • Re: Issue 261 in sipservlets: bad_record_mac using TLS sipservlets
  • Re: Issue 261 in sipservlets: bad_record_mac using TLS sipservlets
  • Re: Issue 261 in sipservlets: bad_record_mac using TLS sipservlets
  • Re: Issue 261 in sipservlets: bad_record_mac using TLS sipservlets
  • Re: Issue 261 in sipservlets: bad_record_mac using TLS sipservlets
  • Re: Issue 261 in sipservlets: bad_record_mac using TLS sipservlets
  • Re: Issue 261 in sipservlets: bad_record_mac using TLS sipservlets
  • Re: Issue 261 in sipservlets: bad_record_mac using TLS sipservlets
  • Re: Issue 261 in sipservlets: bad_record_mac using TLS sipservlets
  • Re: Issue 261 in sipservlets: bad_record_mac using TLS sipservlets
• Issue 260 in sipservlets: "Event header is not parameterable !" sipservlets
  • Re: Issue 260 in sipservlets: "Event header is not parameterable !" sipservlets
• Issue 55 in jdiameter: Problem with send messages using java.nio.SocketChannel in JDiameter jdiameter
  • Re: Issue 55 in jdiameter: Problem with send messages using java.nio.SocketChannel in JDiameter jdiameter
  • Re: Issue 55 in jdiameter: Problem with send messages using java.nio.SocketChannel in JDiameter jdiameter
• Issue 259 in sipservlets: ACK not routed to second MSS server sipservlets
  • Re: Issue 259 in sipservlets: ACK not routed to second MSS server sipservlets
  • Re: Issue 259 in sipservlets: ACK not routed to second MSS server sipservlets
• Issue 330 in jss7: Won't build with maven right out of the box. jss7
• Issue 102 in jain-slee: Notify service SBB on Diameter RA message timeout/connection error jain-slee
• Issue 101 in jain-slee: Diameter: SMS-Information AVP jain-slee
• Issue 20 in webrtcomm: Firefox version throwing error on event.type on addStream event webrtcomm
  • Re: Issue 20 in webrtcomm: Firefox version throwing error on event.type on addStream event webrtcomm
• Issue 100 in jain-slee: Diameter response lost as activity starts in non suspended mode jain-slee
• Issue 54 in jdiameter: Fix logging - errors are being logged in DEBUG level jdiameter
  • Re: Issue 54 in jdiameter: Fix logging - errors are being logged in DEBUG level jdiameter
  • Re: Issue 54 in jdiameter: Fix logging - errors are being logged in DEBUG level jdiameter
  • Re: Issue 54 in jdiameter: Fix logging - errors are being logged in DEBUG level jdiameter
• Issue 257 in sipservlets: Upgrade to Latest Tomcat Version sipservlets
  • Re: Issue 257 in sipservlets: Upgrade to Latest Tomcat Version sipservlets
  • Re: Issue 257 in sipservlets: Upgrade to Latest Tomcat Version sipservlets
  • Re: Issue 257 in sipservlets: Upgrade to Latest Tomcat Version sipservlets
  • Re: Issue 257 in sipservlets: Upgrade to Latest Tomcat Version sipservlets
  • Re: Issue 257 in sipservlets: Upgrade to Latest Tomcat Version sipservlets
  • Re: Issue 257 in sipservlets: Upgrade to Latest Tomcat Version sipservlets
• Issue 256 in sipservlets: TLS Documentation missing trustStore information sipservlets
  • Re: Issue 256 in sipservlets: TLS Documentation missing trustStore information sipservlets
• Issue 255 in sipservlets: Behind NAT, the getInitialRemoteAddress and getInitialRemotePort don't give socket ip address and port sipservlets
  • Re: Issue 255 in sipservlets: Behind NAT, the getInitialRemoteAddress and getInitialRemotePort don't give socket ip address and port sipservlets
• Issue 53 in jdiameter: Jdiameter SCTP support (Stack doesn't come up as diameter client) jdiameter
  • Re: Issue 53 in jdiameter: Jdiameter SCTP support (Stack doesn't come up as diameter client) jdiameter
• Re: Issue 3076 in mobicents: Default diameter Gx auth app id mobicents
  • Re: Issue 3076 in mobicents: Default diameter Gx auth app id mobicents
• Issue 254 in sipservlets: Upgrade to JBoss AS 7.3.0.Final sipservlets
  • Re: Issue 254 in sipservlets: Upgrade to JBoss AS 7.3.0.Final sipservlets
  • Re: Issue 254 in sipservlets: Upgrade to JBoss AS 7.3.0.Final sipservlets
  • Re: Issue 254 in sipservlets: Upgrade to JBoss AS 7.3.0.Final sipservlets
  • Re: Issue 254 in sipservlets: Upgrade to JBoss AS 7.3.0.Final sipservlets
• Issue 253 in sipservlets: ProxyBranch.cancel is not sending CANCEL if a PRACK has been used sipservlets
  • Re: Issue 253 in sipservlets: ProxyBranch.cancel is not sending CANCEL if a PRACK has been used sipservlets
  • Re: Issue 253 in sipservlets: ProxyBranch.cancel is not sending CANCEL if a PRACK has been used sipservlets
  • Re: Issue 253 in sipservlets: ProxyBranch.cancel is not sending CANCEL if a PRACK has been used sipservlets
  • Re: Issue 253 in sipservlets: ProxyBranch.cancel is not sending CANCEL if a PRACK has been used sipservlets
  • Re: Issue 253 in sipservlets: ProxyBranch.cancel is not sending CANCEL if a PRACK has been used sipservlets
• Issue 329 in jss7: sccp-impl 8 tests failing jss7
• Issue 252 in sipservlets: SIP Messages are parsed using system encoding instead of UTF sipservlets
  • Re: Issue 252 in sipservlets: SIP Messages are parsed using system encoding instead of UTF sipservlets
  • Re: Issue 252 in sipservlets: SIP Messages are parsed using system encoding instead of UTF sipservlets
  • Re: Issue 252 in sipservlets: SIP Messages are parsed using system encoding instead of UTF sipservlets
• Issue 251 in sipservlets: Extra Route header added on INVITE sipservlets
  • Re: Issue 251 in sipservlets: Extra Route header added on INVITE sipservlets
  • Re: Issue 251 in sipservlets: Extra Route header added on INVITE sipservlets
  • Re: Issue 251 in sipservlets: Extra Route header added on INVITE sipservlets
  • Re: Issue 251 in sipservlets: Extra Route header added on INVITE sipservlets
  • Re: Issue 251 in sipservlets: Extra Route header added on INVITE sipservlets
  • Re: Issue 251 in sipservlets: Extra Route header added on INVITE sipservlets
• Issue 250 in sipservlets: Fallback to second DNS Record is not even attempted in event of TCP Connection failure sipservlets
  • Re: Issue 250 in sipservlets: Fallback to second DNS Record is not even attempted in event of TCP Connection failure sipservlets
  • Re: Issue 250 in sipservlets: Fallback to second DNS Record is not even attempted in event of TCP Connection failure sipservlets
  • Re: Issue 250 in sipservlets: Fallback to second DNS Record is not even attempted in event of TCP Connection failure sipservlets
  • Re: Issue 250 in sipservlets: Fallback to second DNS Record is not even attempted in event of TCP Connection failure sipservlets
  • Re: Issue 250 in sipservlets: Fallback to second DNS Record is not even attempted in event of TCP Connection failure sipservlets
  • Re: Issue 250 in sipservlets: Fallback to second DNS Record is not even attempted in event of TCP Connection failure sipservlets
  • Re: Issue 250 in sipservlets: Fallback to second DNS Record is not even attempted in event of TCP Connection failure sipservlets
  • Re: Issue 250 in sipservlets: Fallback to second DNS Record is not even attempted in event of TCP Connection failure sipservlets
  • Re: Issue 250 in sipservlets: Fallback to second DNS Record is not even attempted in event of TCP Connection failure sipservlets
  • Re: Issue 250 in sipservlets: Fallback to second DNS Record is not even attempted in event of TCP Connection failure sipservlets
  • Re: Issue 250 in sipservlets: Fallback to second DNS Record is not even attempted in event of TCP Connection failure sipservlets
• Issue 249 in sipservlets: Connection to only 2 SRV records in DNS Lookup are Attempted sipservlets
  • Re: Issue 249 in sipservlets: Connection to only 2 SRV records in DNS Lookup are Attempted sipservlets
  • Re: Issue 249 in sipservlets: Connection to only 2 SRV records in DNS Lookup are Attempted sipservlets
  • Re: Issue 249 in sipservlets: Connection to only 2 SRV records in DNS Lookup are Attempted sipservlets
  • Re: Issue 249 in sipservlets: Connection to only 2 SRV records in DNS Lookup are Attempted sipservlets
  • Re: Issue 249 in sipservlets: Connection to only 2 SRV records in DNS Lookup are Attempted sipservlets
• Issue 24 in commtesting: SipUnit adds the To tag in the INVITE after a 401/407 response commtesting
• Issue 35 in smscgateway: Incoming SMPP Support smscgateway
• Issue 23 in commtesting: Challenge response for REGISTER contains to tag commtesting
• Issue 52 in jdiameter: NPE in ClientRxSessionImpl for AAA with no result code jdiameter
  • Re: Issue 52 in jdiameter: NPE in ClientRxSessionImpl for AAA with no result code jdiameter
• Issue 248 in sipservlets: How to start to run click to call example sipservlets
  • Re: Issue 248 in sipservlets: How to start to run click to call example sipservlets
• Re: Issue 50 in jdiameter: Rx: ClientRxSessionImpl: ClassCastException handling STA at handleFailureMessage jdiameter
  • Re: Issue 50 in jdiameter: Rx: ClientRxSessionImpl: ClassCastException handling STA at handleFailureMessage jdiameter
• Issue 51 in jdiameter: ClassCastException at org.jdiameter.client.impl.app.rf.ClientRfSessionImpl handling FAILED_SEND_RECORD jdiameter
  • Re: Issue 51 in jdiameter: ClassCastException at org.jdiameter.client.impl.app.rf.ClientRfSessionImpl handling FAILED_SEND_RECORD jdiameter
• Issue 99 in jain-slee: Diameter Ro RA: Client sets CC-request-type twice when sending CCRs jain-slee
  • Re: Issue 99 in jain-slee: Diameter Ro RA: Client sets CC-request-type twice when sending CCRs jain-slee
• Re: Issue 39 in jdiameter: SCTP Transport classes define static variables for association jdiameter
  • Re: Issue 39 in jdiameter: SCTP Transport classes define static variables for association jdiameter
• Re: Issue 39 in jdiameter: SCTP Server Class defines static variables for association jdiameter
• Issue 247 in sipservlets: mobicents does not handle doAck properly when security is enabled sipservlets
  • Re: Issue 247 in sipservlets: mobicents does not handle doAck properly when security is enabled sipservlets
  • Re: Issue 247 in sipservlets: mobicents does not handle doAck properly when security is enabled sipservlets
• Issue 246 in sipservlets: Problem in SipConnector handling if reverse DNS lookup is missing sipservlets
  • Re: Issue 246 in sipservlets: Problem in SipConnector handling if reverse DNS lookup is missing sipservlets
  • Re: Issue 246 in sipservlets: Problem in SipConnector handling if reverse DNS lookup is missing sipservlets
• Issue 133 in mediaserver: JSR-309 driver leaks memory mediaserver
  • Re: Issue 133 in mediaserver: JSR-309 driver leaks memory mediaserver
  • Re: Issue 133 in mediaserver: JSR-309 driver leaks memory mediaserver
  • Re: Issue 133 in mediaserver: JSR-309 driver leaks memory mediaserver
  • Re: Issue 133 in mediaserver: JSR-309 driver leaks memory mediaserver
  • Re: Issue 133 in mediaserver: JSR-309 driver leaks memory mediaserver
  • Re: Issue 133 in mediaserver: JSR-309 driver leaks memory mediaserver
  • Re: Issue 133 in mediaserver: JSR-309 driver leaks memory mediaserver
  • Re: Issue 133 in mediaserver: JSR-309 driver leaks memory mediaserver
  • Re: Issue 133 in mediaserver: JSR-309 driver leaks memory mediaserver
  • Re: Issue 133 in mediaserver: JSR-309 driver leaks memory mediaserver
  • Re: Issue 133 in mediaserver: JSR-309 driver leaks memory mediaserver
  • Re: Issue 133 in mediaserver: JSR-309 driver leaks memory mediaserver
  • Re: Issue 133 in mediaserver: JSR-309 driver leaks memory mediaserver
  • Re: Issue 133 in mediaserver: JSR-309 driver leaks memory mediaserver
  • Re: Issue 133 in mediaserver: JSR-309 driver leaks memory mediaserver
  • Re: Issue 133 in mediaserver: JSR-309 driver leaks memory mediaserver
  • Re: Issue 133 in mediaserver: JSR-309 driver leaks memory mediaserver
  • Re: Issue 133 in mediaserver: JSR-309 driver leaks memory mediaserver
  • Re: Issue 133 in mediaserver: JSR-309 driver leaks memory mediaserver
• Issue 132 in jain-sip: Via Header's "sent-by" info got changed when using websocket jain-sip
• Issue 245 in sipservlets: Impossible to add address parameter to From Header sipservlets
  • Re: Issue 245 in sipservlets: Impossible to add address parameter to From Header sipservlets
  • Re: Issue 245 in sipservlets: Impossible to add address parameter to From Header sipservlets
  • Re: Issue 245 in sipservlets: Impossible to add address parameter to From Header sipservlets
  • Re: Issue 245 in sipservlets: Impossible to add address parameter to From Header sipservlets
• Issue 244 in sipservlets: If an INVITE is forwarded in B2BUA mode, the call is forked by some proxy, and the UAS that answers the call is not the UAS that sent the first provisional response, then forwarding the 200 OK to the UAC fails sipservlets
  • Re: Issue 244 in sipservlets: If an INVITE is forwarded in B2BUA mode, the call is forked by some proxy, and the UAS that answers the call is not the UAS that sent the first provisional response, then forwarding the 200 OK to the UAC fails sipservlets
  • Re: Issue 244 in sipservlets: If an INVITE is forwarded in B2BUA mode, the call is forked by some proxy, and the UAS that answers the call is not the UAS that sent the first provisional response, then forwarding the 200 OK to the UAC fails sipservlets
  • Re: Issue 244 in sipservlets: If an INVITE is forwarded in B2BUA mode, the call is forked by some proxy, and the UAS that answers the call is not the UAS that sent the first provisional response, then forwarding the 200 OK to the UAC fails sipservlets
• Re: Issue 153 in sipservlets: SIP Outbound (RFC 5626) broken for target refresh sipservlets

• Earlier messages
• Later messages