Personally, I look at it from a motivation perspective: who has the
motivation to change to make something work? In the SIP-Connect case, the
Service Provider is the one selling the SIP-Trunk service, so to win the
deal and satisfy customers they've got more of the motivation/burden to
make it work. The SP's also have a large motivation to support as many
IP-PBX vendors as possible. Any changes we mandate of IP-PBX vendors will
reduce the pool of them that are "SIP-Connect compliant", which is not
good. Especially when what we're proposing basically works *now* in
SIP-Trunk deployments - i.e., there's running code. It doesn't quite work
that way today within the SP's domain on the wire, but as I said they have
the motivation (and the ability) to change their side.
-hadriel
_______________________________________________
Sip mailing list https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors at cs.columbia.edu for questions on current sip
Use sipping at ietf.org for new developments on the application of sip