ISDN/SIP interworking [ETSI TS 183 036]
- Subject: ISDN/SIP interworking [ETSI TS 183 036]
- From: Javi Muñoz <javi@xxxxxxxxxxxxx>
- Date: Wed, 30 Nov 2011 18:59:21 +0100
- Delivered-to: sipping@xxxxxxxxxxxxxx
- User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; es-ES; rv:1.9.2.24) Gecko/20111103 Thunderbird/3.1.16
Three questions about it:
(a) ISDN/SIP interworking spec [ETSI TS 183 036] proposes that in the
Q.931/SIP interworking, some EIs Q.931 are codec to SDP and/or inserted
in the SIP body as a PSTN XML element.
Under what criteria, an Q.931 EI should be?:
(1) Coding to SDP
AND / OR (this is also important)
(2) Inserted in the SIP body as a PSTN XML element
or
(3) Coding to the URI SIP or and SIP header
or
(4) None (only interpreted by the AGW, without being carried over SIP)
(b) Why does [ETSI TS 183 036]define the mapping of the IE "User to
user" to the SIP header User-to-User [draft-johnston-sipping-cc-uui-09],
instead of transporting it over an PSTN XML element? (the IE "User to
user" must be transported transparently by the nerwork)
(c) Although as optional, [ETSI TS 183 036]defines the coding to SDP of
the "High Layer Characteristics Identification" field of the IE
HLC[Q.931].According to Q.931, this EI HLC should be used by the
end-to-end terminals, not by the LEs (or AGWs in NGN). Then:
(1) Why this SDP coding?
(2) And why is it optional?
Regards,
Javi
_______________________________________________
Sipping mailing list https://www.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@xxxxxxxxxxxxxxx for questions on current sip
Use sip@xxxxxxxx for new developments of core SIP
[IETF Announce]
[IETF Discussion]
[Linux SCSI]
[Linux USB Devel]
[Video for Linux]
[Linux Audio Users]
[Photo]
[Yosemite News]
[Yosemite Photos]
[Free Online Dating]
[Linux Kernel]
[Linux SCSI]
[XFree86]
[Big List of Linux Books]