Pena, Christian | 16 Jul 2012 19:32

Called Party Information on INVITES

I have a SIP Trunk with a bunch of DIDs under it. When a call comes into
the SIP Trunk, the CALLED parties number shows up in the To header. The
end user is looking for the called party number to show up on the
Contact header instead. However on my INVITES, that shows the SIP trunk
username(which is one of the customers phone numbers).

I have this same setup working for lots of customers so I think my
configuration is sound, but I have debugs from another provider where
the called party number is on the Contact header.

Who is correct? 

If anyone could site a RFC that would be great! 

Christian Pena | Engineering
EarthLink Business 
www.earthlinkbusiness.com <http://www.earthlinkbusiness.com/> 

E: christian.pena <at> corp.earthlink.com
<mailto:christian.pena <at> corp.earthlink.com> 

O: 786-363-0460 | F: 786-363-0206

Worley, Dale R (Dale | 16 Jul 2012 23:20
Favicon

Re: Called Party Information on INVITES

On Mon, 2012-07-16 at 12:32 -0500, Pena, Christian wrote:
> I have a SIP Trunk with a bunch of DIDs under it. When a call comes into
> the SIP Trunk, the CALLED parties number shows up in the To header. The
> end user is looking for the called party number to show up on the
> Contact header instead. However on my INVITES, that shows the SIP trunk
> username(which is one of the customers phone numbers).

The *requirements* are:

1. The Contact of the INVITE is a URI to which later requests in the
dialog can be sent by the called party.  The called party shouldn't
depend on this URI having any particular format.

2. The request-URI (in the first line of the message) is the URI toward
which the request should be forwarded.  (Of course, various forwarding,
contact resolution, and redirection operations will change the
request-URI in downstream versions of the INVITE.)

By *convention*:

3. The To URI gives the "identity" of the caller.

4. The From URI gives the intended callee, which usually is the
request-URI which the UAC put into the first INVITE.

In reality, the To and From URIs are used only as documentation, in that
no automated action is taken based on their contents (although the UAC
must be careful to ensure that they are syntactically correct, as
downstream elements must be able to extract the "tag" header
parameters).
(Continue reading)


Gmane