Status: New
Owner: [email protected]
Labels: Type-Defect Priority-Medium Version-3.0.0.FINAL

New issue 88 by [email protected]: Mgcp Provider manages transactions by remote transaction id
http://code.google.com/p/mediaserver/issues/detail?id=88

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.

Reply via email to