Re: Query on how to instantiate a call for Request to call.
Igor Faynberg <[email protected]> Mon, 12 Jan 2004 15:30:45 -0500
| Newsgroups | gmane.ietf.pint |
|---|---|
| Organization | Lucent Technologies |
| Message-ID | <[email protected]> |
Rohith, Indeed, the SCP is the primary example of the "Executive System." Another= such example is the IN Service Node (SN) described in ITU-T Recommendation Q.1= 205. In the case of the SN, both parts of the call are created using ISDN PRI and bridged by the SN.=20 As far as the PSTN is concerned, only IN was envisioned by PINT. (In othe= r words, no messages were expected to be sent directly to switches.) Nevert= heless, nothing precludes implementing PINT on a switch if an operator wishes to = do so. In this case, the call will, of course, be created by the switch iself.=20 To this end, PINT assumed that the enterprise (PBX) PINT implementations = do use the switch as an "Executive System." With best regards, Igor Faynberg=20 rohith wrote: >=20 > Hi All, >=20 > I was going through the RFCs 2848 and 2458. I wanted to know if there = are any standard defined for and beyond the =93Executive System=94 (RFC 2= 848, figure 1). In particular I wanted to know the protocols and message= s that are used in the PSTN to bring about the =93Request to call=94. >=20 > The SCP initiated =93Create call=94 message could be used for instantia= ting a call in an IN environment. Are there any such non-IN solutions do= to this (besides using =93RLT=94 or =93a service node that call-transfer= s=94)? >=20 > Thanks, > Rohith K N >=20 > ---------------------------------------------------------------------= ----------- > _______________________________________________ > PINT mailing list > [email protected] > http://lists.bell-labs.com/mailman/listinfo/pint