[SIPForum-discussion] URI in the TO header

[shawn.degraw at comcast.net]

When ISUP messages are converted to SIP the Called party number is usually mapped to the RURI header and the Original Called number, if included, would be mapped to the TO header. In this example the RURI and TO header would usually be different. Likewise, in your example, I would think the dialed number, 1234, would be mapped to the TO header and the new number, 44445555, would be mapped to the RURI header when creating the INVITE. 



----- Original Message ----- 
From: "FRANCISCO GIOIA" <GIOIA at embratel.com.br> 
To: discussion at sipforum.org 
Cc: "RENATO DE ALMEIDA ANTUNES" <RREAL at embratel.com.br>, "MARCIO DE MIRANDA LOPES" <MMLOPES at embratel.com.br> 
Sent: Wednesday, October 13, 2010 10:24:54 AM 
Subject: [SIPForum-discussion] URI in the TO header 




Dear all, I have a doubt. Can you help me? 



Question: 

RFC 3261 (item 8.1.1.1) recommends that the REQUEST-URI of the initial message (Request-line) should be equal to the URI of the "TO" header field. The explicit exception in this item of the RFC is when it comes to the REGISTER method (where such information may be different). 



We wonder if there are situations in which the URI in the TO header field may be different from the URI of the Request-Line? 

An entity (UAS) that receives a SIP INVITE message must focus on which recipient to make the correct routing of the call ( Request-Line URI or TO header Field URI )? 



RFC 4497 (item 11.4) mentions the possibility of difference between REQUEST-Line URI and URI in the TO header field in case of interworking between SIP and QSIG. In this case should be considered that there was a call forwarding? This applies, by analogy, to other cases of interworking (SIP x SIP, SIP x ISUP, SIP x MGCP, ...)? 



In the case of numerical regeneration done by the UAS, how does the Request-Line URI and the TO header field URI of the INVITE message must be filled? Remembering that it is not Call Forwarding but regeneration(numerical manipulation). 



Example: 

UAS receives 
Source = 22223333 (tel number of calling subscriber) 
Destination = 1234 (dialed number) - UAS manipulates to 44445555 



Thank you in advance for your attention and understanding. 



Francisco Gioia. 

AVISO DE CONFIDENCIALIDADE 
Esta mensagem e seus anexos são de uso exclusivo de pessoas e entidades autorizadas pela Embratel e podem conter informações confidenciais e/ou privilegiadas. É proibido revelar, alterar, copiar, divulgar ou se beneficiar, direta ou indiretamente, destas informações sem a autorização de seus autores. Se você recebeu este e-mail por engano, por favor, informe o remetente e apague a mensagem imediatamente. A Embratel se reserva o direito de pleitear ressarcimento pelos prejuízos decorrentes do uso indevido das informações e de requerer a aplicação das penalidades cabíveis. 

_______________________________________________ 
This is the SIP Forum discussion mailing list 
TO UNSUBSCRIBE, or edit your delivery options, please visit http://sipforum.org/mailman/listinfo/discussion 
Post to the list at discussion at sipforum.org 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20101014/2d2508ad/attachment-0002.html>