>>>>My Query --> Regarding point 3, should we not send the DID number in the FROM field so that the called party can *identify* the actual caller. [VR]This will be done by P-Preferred-Identity (child id), in case of anonymous, P-Preferred-Identity has child id, P-Asserted-Identity has parent id. >>>>What will be the Request-URI and TO field when IPPBX receives the incoming INVITE? Should we expect the parent number viz 12304 in Request-URI and DDI number in TO field viz (12302 for example) so that PBX can identify the called party on the basis of TO field. [VR] Right but I have also seen reverse. So this is inter-op issue. Vipul Rastogi
________________________________ From: Vivek Batra [mailto:[EMAIL PROTECTED] Sent: Friday, September 19, 2008 4:39 PM To: Rastogi, Vipul (Vipul) Subject: Re: [Sip-implementors] SipConnect Registration/Authentication Hi Vipul, This mail is in concern with your posting on SIP Implementors about DID. I just wanted to confirm what you said: 1. Suppose I have purchased 10 DDI numbers from BroadWorks. Parent number is 12301 and DDI numbers are 12301 to 12310. 2. Now I need to send the REGISTER request only for parent id viz 12301 (shall be present in FROM field). 3. When any user of IPPBX makes an OG call to BroadWorks server, PBX shall send parent id in the FROM field viz 12301. My Query --> Regarding point 3, should we not send the DID number in the FROM field so that the called party can *identify* the actual caller. 4. What will be the Request-URI and TO field when IPPBX receives the incoming INVITE? Should we expect the parent number viz 12304 in Request-URI and DDI number in TO field viz (12302 for example) so that PBX can identify the called party on the basis of TO field. I would be much pleased if you comment on point 3 and point 4. Best Regards, Vivek Batra Date: Thu, 18 Sep 2008 17:38:41 +0800 From: "Rastogi, Vipul (Vipul)" <[EMAIL PROTECTED]> Subject: Re: [Sip-implementors] SipConnect Registration/Authentication Questions To: <[EMAIL PROTECTED]>, <[email protected]> Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset="US-ASCII" Most of Core Service Provider VOIP Platforms supports SIPConnect option 1 and option 2 but they prefer option 2. BroadWorks is one of them. In option 2, we just register with main Id (called Parent ID) and every out going INVITE has Parent Id in 'FROM' header. Option 2 behaves like single endpoint to ISP S/W. - Vipul Rastogi _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
