Thanks to all!
I found one internet draft that propose to use the INFO method to convey subsequent dialed numbers: http://tools.ietf.org/id/draft-zhang-sipping-overlap-01.txt It claimed to resolve the issues related to the INVITE/484/ACK approach in RFC3578, but this draft seems to be deceased only after one revision, don't know what's wrong with it! ------------------ Original ------------------ From: "Brett Tate"<[email protected]>; Date: Tue, Jul 16, 2013 07:56 PM To: "SIP Learner"<[email protected]>; "sip-implementors"<[email protected]>; Subject: RE: [Sip-implementors] Overlap signaling in a native SIP network > In my opinion, if only a SIP network is involved and > no gateways are used, overlap signalling (e.g., the > caller sends dialed digits to an outbound proxy in > consecutive separate INVITEs for the outbound proxy > to collect enough information and route the requests) > is meaningless, because there are no physical connections > to be established, am I right? It isn't meaningless; it wastes network resources and the devices would need to agree upon what should occur (i.e. how the digits are collected, et cetera). Even though draft-ietf-bliss-shared-appearances provides a PUBLISH mechanism for seizing an appearance, some vendors might also allow an INVITE/484/ACK exchange to temporarily keep an appearance seized. _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
