On Mon, 2010-01-11 at 23:30 -0500, M. Ranganathan wrote: > Attached is a sipxbrdge.xml with branchId enhancements to References. > This allows related transactions to be related to each other. > > If interested, please have a look and let me know what you think of it.
Here are some suggestions: Change "branch" to "sipx-branch". (I think you've already got this in the works.) When a request is passing through sipXbridge, the outgoing request should have "References: [call-id of the dialog on the other side];rel=chain". Frame 244: OK Frame 274: This has rel=sequel, where rel=chain seems more appropriate. Frame 408: OK Frame 515: I'm not sure that there is a defined References: value for this request, because this is a re-INVITE stimulated by receiving a REFER on the other side. But if you want to use References (and you probably do, to carry the branch value), you want rel=chain. Frame 586: OK Frame 604: I'm not sure that there is a defined References: value for this request, because this request really isn't stimulated by a request from the other side. Frame 637: This should be rel=chain, given the call-id in the References header. Frame 644: This NOTIFY has the same problem as frame 604. Frame 685: This should use rel=service, since it is an INVITE for MOH. Frame 788: This should be rel=chain, given the call-id in the References header. Dale _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
