Hi all,
For a PC2PC session to establish properly, the following signaling sequence should occur between the clients:
Client1 ---> INVITE ---> Client2 <--- 200 OK <--- ----> ACK ---->
Client2 will get into the CONNECTED state only after it gets the ACK response from Client1. According to the logs, INVITE/200 OK works fine, however, the final ACK response sent by Client1 does not make it to the Client2, i.e. Client2 does not get it. So after about 30 seconds, Client2 hits a transaction timeout and sends a BYE request back to Client1. According to the logs, even this BYE request does not make it to Client1, so Client1 remains in the CONNECTED state.
Can you help me on this topic?
Thanks Keyvan
On 20-05 14:34, andayesh wrote:
Hi all,
For a PC2PC session to establish properly, the following signaling sequence should occur between the clients:
Client1 ---> INVITE ---> Client2 <--- 200 OK <--- ----> ACK ---->
Client2 will get into the CONNECTED state only after it gets the ACK response from Client1. According to the logs, INVITE/200 OK works fine, however, the final ACK response sent by Client1 does not make it to the Client2, i.e. Client2 does not get it. So after about 30 seconds, Client2 hits a transaction timeout and sends a BYE request back to Client1. According to the logs, even this BYE request does not make it to Client1, so Client1 remains in the CONNECTED state.
Can you help me on this topic?
No if you don't provide us with more information (SIP message dumps and SER configuration file).
Jan.
-
andayesh -
Jan Janak