80 likes | 280 Views
GIN with Literal AoRs for SIP in SSPs (GLASS) draft-kaplan-martini-glass-00. Hadriel Kaplan. The Problem. Draft-gin handles E.164 How do we handle alpha-numeric usernames? sip:bob@ssp.com. The Solution.
E N D
GIN with Literal AoRs for SIP in SSPs (GLASS)draft-kaplan-martini-glass-00 Hadriel Kaplan
The Problem • Draft-gin handles E.164 • How do we handle alpha-numeric usernames? sip:bob@ssp.com
The Solution • “Bulk” REGISTER any provisioned AoR, as if the PBX had separately Registered for each one • Contact-routing a la RFC3261 still works • If it would have worked for explicit REGISTERs • The Contact-URI “expansion” is the provisioned AoR user portion • The same that would be provisioned for a separate REGISTER
Example • PBX does a draft-gin REGISTER • SSP has provisioning for bob@ssp.com • INVITE to bob@ssp.com follows rfc3261 Originator SSP PBX REGISTER sip:ssp.comTo: <sip:pbx123@ssp.com>Contact: <sip:192.1.2.3;bnc> INVITEsip:bob@ssp.com INVITEsip:bob@192.1.2.3
Perceived Problems don’t apply • Draft-gin really did Register globally unique AoRs • E.g., sip:+123456789@ssp.com • So now we’re bulk Registering other globally unique AoRs, scoped to the Registered domain (ssp.com) • Just like RFC 3261 would do for any AoR
What about bob@ssp.co.ca? • Question: • How does the PBX know the call was for bob@ssp.com and not for bob@ssp.co.ca? (if both are handled) • Answer: it won’t • It wouldn’t have in rfc3261 either, if one REGISTER for bob@ssp.com did more • Really the call is being re-targeted to bob@ssp.com – and we have hist-info for figuring out the original target, right?
Other solutions for bob@ssp.co.ca • The PBX can REGISTER to ssp.co.ca • By definition it knows about ssp.co.ca, so it can REGISTER to ssp.co.ca separately • Or we can define a new URI user parameter named “user-context”: sip:bob;user-context=ssp.co.ca@192.1.2.3 • Why is this legit? Same thing as phone-context really, just for any alphanumeric
Open Issues • Can this just be informational vs. standards-track?