Presentation on theme: "Service Routing Jonathan Rosenberg dynamicsoft. The many facets of routing zRouting decisions can be based on ySIP registration databases ystatic configurations."— Presentation transcript:
The many facets of routing zRouting decisions can be based on ySIP registration databases ystatic configurations ytelephone prefixes (propagated by TRIP) yaccess to external databases zAbove generally done based on request URI zBut what if you want to route not based on who you are calling?
Service Routing zProblem Definition yA session has some service that needs to be invoked xCall screening xCall forwarding xRedirect to Web yCan be invoked at origination domain, termination domain, or in middle yDifferent application servers provide various services yProxy needs to figure out which app server is handling call
Pictorally zApp servers can be in different domains or same domain as proxy zOrigination can be from PC, MGC, softphone, etc. zApp servers can proxy, redirect, or re-originate yMay need to determine a next hop app server as well ASP1 ASP2
Routing Criteria zRequest URI domain yscreen all calls destined for a particular company zRequest URI u@d yCFNA service for some user zFrom domain yincoming call screening preventing spam z Accept header + complete request URI yWeb IVR service z Content-Type yCheck all messages with executable content for viruses
Problem Statement zOnly application servers know what apps they have zOnly application servers know their invocation criteria zApplication servers have relationships with proxies/MGC yinter-provider yintra-provider z Would like to have app server push routing criteria to proxy z Would like to aggregate if possible z Keepalives z Information could be propagated to other proxies
TRIP? zSeems very similar to TRIP-GW problem yKeepalives yPushing of routing information yPossible tie in to inter- domain propagation yRapid operation z Whats different yRoutes arent just prefixes yMore complex rules based on xRequest-URI xFrom field xTo field xContent-Type yHarder to aggregate
Question zDoes this seem reasonable? zIs TRIP the appropriate protocol for service routing? zAlternatives yREGISTER yNew protocol ySLP yothers? z Would like to begin a dialogue