search

Suvarna1488 / boghe

Automatically exported from code.google.com/p/boghe
0 stars 0 forks source link

changing RTP port for every Re-Invite #164

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Call to IMS core, where Alerting indication is generated. IMS Core acting as 
B2BUA.
2. After Connect (200 OK) CallServer send Re-Invite to A with SDP data (RTP 
address) of B terminal (also Boghe)
3. A answers with 200 OK and with new RTP port. This new data (new A RTP port) 
is then with Re-Invite sended to B. B answers with 200 OK and again with new 
RTP port. This new data (new B RTP port) is then sended to A with Re-Invite. A 
answers with 200 OK and again with new RTP port. This could take all night.

What is the expected output? What do you see instead?
When Boghe receives Re-Invite it is not necessarily to always change RTP port

What version of the product are you using? On what operating system?
Boghe IMS Client v2.0.106.731, Win XP

Please provide any additional information below.

Original issue reported on code.google.com by ales.st...@gmail.com on 7 Dec 2012 at 9:45