Hi Folks, I am digging into Number portability and SIP. [1] (still a draft document) describes the following ways to convey number portability information
a) Identifying the ported-to-provider by domain name in SIP-URI Sip:+cc1...@ported-to-provider;user=phone b) Using a prefix (PPPPP) to the national significant E164 number to provide information on the Ported-to-provider user and indicating this by providing a national specific phone-context Tel: PPPPP1234;phone-context=+CC-np Sip:PPPPP1234;phone-context=+cc...@ported-to-provider;user=phone c) Retaining the E.164 number unmodified but using the RFC 4769 and RFC4694 provisions to provide information on the "ported-to-provider" in the RFC 4694 routing number parameter. Tel:+CC1234;rn=+CCPPPPP;npdi Tel:+CC1234;rn=PPPPP;rn-context=+CC;npdi Or corresponding SIP: formats d) Retaining the E.164 number unmodified but using the RFC4769 and RFC 4694 provisions to provide information on the "ported-to-provider" in the RFC 4694 routing number parameter in an interworking friendly fashion Tel:+CC1234;rn=PPPPP1234;rn-context=+CC;npdi Tel:+CC1234;rn=+CCPPPPP1234;npdi Or corresponding SIP: formats I was wondering if anyone could share experiences (which mechanisms are actually used) in real deployments. Specifically, with option b. For example, I have just found a new case which includes the prefix between the CC and the national significant number Tel: +CCPPPPP1234;phone-context [1] http://portal.etsi.org/docbox/tispan/open/NGN_LATEST_DRAFTS/RELEASE3/04008-ngn-r3v019.pdf Regards, -- Victor Pascual Ávila _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
