search

noushadali / mediaserver

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

Mgcp Provider manages transactions by remote transaction id #88

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
While using several mgcp clients both can send different requests with same 
transaction id.This is expected behaviour since mgcp client generates 
transactions by date and while using 2 clients if both will generate tx in same 
time ( up to nanos ) this will create same tx id.
Should add local transaction id and manage transaction by local transaction id 
to disallow duplicates.

Original issue reported on code.google.com by oifa.yul...@gmail.com on 23 Oct 2012 at 9:15

GoogleCodeExporter commented 9 years ago 
Resolved by revision  8bbe72c7530f

Original comment by oifa.yul...@gmail.com on 23 Oct 2012 at 12:49