Amanpreet Singh <amanpreeet.si...@gmail.com> writes: > Peer is expecting the same call-id on the second trunk after route advance, > was wondering if we have something around this to find a common ground to > address this.
Please understand that this isn't a matter of standards compliance, but a matter of the choices that the equipment on one side makes (within the standards) and how well that interoperates with the choices that the equipment on the other side makes (within the standards). Although as another person said, it's very likely that your equipment has a configuration option to cause it to use the same Call-ID for forks of the same call. Dale _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
