Web Integration I Services, services, services! Programming IP Telephony Services alongside the Call Processing Language (CPL) in addition to CGI



The Above Picture is Related Image of Another Journal


Web Integration I Services, services, services! Programming IP Telephony Services alongside the Call Processing Language (CPL) in addition to CGI

Baker College of Auburn Hills, US has reference to this Academic Journal, Programming IP Telephony Services alongside the Call Processing Language (CPL) in addition to CGI Jonathan Rosenberg Bell Laboratories October 15, 1999 Services, services, services! IP telephony cost benefits so that consumer declining Must be differentiators higher quality? ease of use – UI new services in addition to features Key is new services integration services email, web, presence, IM, chat part of telephony control services allow parameters so that be defined by consumer presentation services new look in addition to feel in consideration of old friends Web Integration I IWR – Interactive Web Response user calls a number web page ?answers? use hyperlinks instead of keypresses so that navigate much easier than voice final link makes phone call VXML in consideration of non-PC access SIP Accept headers in consideration of MIME negotiations! INVITE INVITE redirection Web Page IWR Service

 Gaulin, Steven Baker College of Auburn Hills www.phwiki.com


Related University That Contributed for this Journal are Acknowledged in the above Image


Web Integration II Web Agents A calls B B is not home After N rings, A gets web page instead possibly dynamically created in consideration of caller Web page lists alternate contact information in addition to times cell phone after 5pm email in consideration of non-urgent stuff URL in consideration of recording voicemail mailto URL in consideration of sending email Web Integration III Shared Web Talking ?web? another form of media stream – like audio in addition to video Users can talk in addition to simultaneously browse web Show each other pages Discuss stocks Read the paper Web Caller ID When A calls B, B?s homepage appears in A?s browser ?homepage? dynamically generated in consideration of B perhaps Email E-mail not good in consideration of interactive communications Great in consideration of notification related services! Type of information unbounded Notification possibilities call information call attempts subscriber information monthly bill Messaging emails contain URLs so that streaming media controls

Presence ICQ concept ?buddy lists? in addition to subscriptions know who is online normally in consideration of instant messages Big idea: Users can subscribe so that each other, in addition to learn: when they pick up in addition to hang up the phone when they are available so that talk or not when they are in the office or not chair sensor! when the cell-phone is on or not Presence propagates information about a users willingness, ability, in addition to desire so that communicate using a variety of mediums Example Presence Service Phone status subscription A subscribes so that B?s phone When B?s phone state changes hook state willingness so that talk Notification sent so that A email, instant message, presence notification A can then call B unsubscribe so that B SUBSCRIBE hangup NOTIFY Presence server Challenge – Service Programmability Where do services live? What controls do the programs have? When can the program execute controls? What information are the programs provided? What resources do the programs have access to? Who can create the programs? How are the programs instantiated?

Distributed Systems Session 4: RPCs (Remote Method Invocation) Java RMI. Outline 0 Motivation 0.1 RPC 0.2 RPC so that RMI 0.3 Middleware Layers 0.3 Java RMI:The Essence 0.4 Java 0.5 RMI Rationale 0.6 Client-Service 0.7 Client-Service 0.8 RMI 0.9 Remote Method Invocation 1.0 Conceptual Framework: Aspects 1.1 System Goals of RMI Distributed Object Application Requirements 2.0 Remote Method Invocation 2.1 RMI Architecture 2.2 RMI Components 2.31 The Remote Object: 2.32 The interface 2.33 The Interface: Advantages 2.34 The Client 2.35 The stub 2.36 The Skeleton 2.37 The Server Implementation 3.0 How so that Write RMI Applications 3.0 How so that write an RMI application 3.1 Implementing RMI 3.2 Implementing RMI: RMI Core 3.3 Interfaces in addition to Classes 3.4 Implementing RMI (Server) 3.5 Implementing RMI (Server) 3.6 Implementing RMI (Client) 3.7 Implementing RMI: Summary 4.0 RMI Interface 5.0 Binding 5.1 Binding 5.1 Binding 6.0 Handling of Remote Methods 7.0 Failures of RMIs Summary 1 Summary 2 Summary Critique Critique Online Resources & Reading

Session Initiation Protocol Invite user so that sessions Basic signaling in addition to session description (SDP) Allows so that search in consideration of the user so that be invited Mobility Redirect/proxy Multicast Location of logic SIP User Agents trust issues heterogeneity of platforms always on problem SIP servers natural place in consideration of routing, screening, pre-call services External devices so that SIP servers SCP/SSP model in IN safety, load balancing, good in consideration of third parties latency issues in IP what replaces INAP? DIAMETER? COPS? MGCP+? SIP (same syntax, wrong semantics) Nature of Control High Level ?forward?, ?reject?, ?redirect? common so that all SP Medium Level controlled device abstracted so that a model call models in IN control = goto state N Lowest level full control – send message X Not a single answer! Fundamental tradeoffs: simplicity vs. flexibility safety vs. flexibility

Nature of Information Highest level ?new call from Joe so that Bob? can be SP independent Medium level state machine transitions + basic data (caller, callee, etc.) Lowest level Full messages Same tradeoffs. Who can write them? Creator determines tradeoff operating point Three principals Administrator Third party provider End user Lines can be blurry Real operating point depends largely on trust Other issues Access so that resources What else can program do besides control General purpose program – anything Java script – lots, but not everything configuration script – very limited How does it get there? Linked in (API model) server must be taken down, recompiled not clean separate process (CGI) data read in (servlet model)

Solution I:SIP CGI Benefits of CGI as a basis programming language independence full control over headers/messages leverage existing tools SIP similar so that HTTP What?s different from HTTP CGI persistence model multiple actions per script output response naming request naming Persistence Model Transaction more complex than request-response proxying provisional responses Many points during transaction where script might execute ?points? = message arrivals Script reinvoked on message arrivals State maintained by cookie opaque so that server passed from script so that server in addition to back on reinvocation Reinvocation points controllable (triggers) Multiple Actions Many actions possible new request proxy request create response return response default Each action looks like a message in script output parser reuse Multiplex actions using SIP message multiplexing rules

Response Naming Wish so that return a response received during previous invocation Server names responses Tell server so that return named response script need not store message 1 2 3 2 Request Naming Multiple requests proxied (forking) When response comes, script wants so that match response so that request Can use branch-id, but complex Solution: request-token Passed back so that script when response comes Not same as response token: multiple responses per request a b c 2 a b c Message Merging When script outputs response or proxied request server computes default resp/request header fields are merged alongside script output Merging header in script replaces header in message header in script alongside no value deletes header in message Simplifies life Script ignores Via?s, MaxForwards, etc.

Example Output INVITE sip:jdrosen@bell-labs SIP/2.0 To: sip:jdrosen@bell-labs From: sip:machine@bell-labs Call-ID: 10 Cseq: 0 INVITE Content-Length: 0 PROXY_REQUEST_TO sip:hgs@cs.columbia SIP/2.0 Max-Forwards: SIP/2.0 180 Ringing User CGI_SCRIPT_COOKIE aoi988ans0naa SIP/2.0 Status Draft 1 submitted so that IETF Dec98, draft 2 May 21, 1999 No wg so that do it likely we will submit as informational Two known implementations Solution II: CPL Call Processing Language targeted in consideration of end user service creation controls at high level information available at high level Describes basic service Model: SIB?s from IN service = DAG Two types of nodes action nodes: outputs = results decision nodes: ouputs = possible values Safety Bounds on compute time

Example DAG Call Representation Use XML links = subtags parameters = attributes extensibility mechanisms useful easy transport generation/parsing by tools GUI in consideration of creation Conclusion Services key Programmability serious problem Two solutions proposed: SIP CGI CPL

Gaulin, Steven General Manager

Gaulin, Steven is from United States and they belong to General Manager and work for KPHX-AM in the AZ state United States got related to this Particular Article.

Journal Ratings by Baker College of Auburn Hills

This Particular Journal got reviewed and rated by Example DAG Call Representation Use XML links = subtags parameters = attributes extensibility mechanisms useful easy transport generation/parsing by tools GUI in consideration of creation Conclusion Services key Programmability serious problem Two solutions proposed: SIP CGI CPL and short form of this particular Institution is US and gave this Journal an Excellent Rating.