[SIPForum-discussion] SIP feature support question?

[Chris Liu]

Hello all,
I got a few questions as below want to hear your inputs:

Is there anyone implemented SIP to support long call audit? (e.g. SIP
INFO, SIP re-INVITE with SDP)?

How do you implement SIP to support the use of the DIVERSION header
and under what circumtances this DIVERSION header is been provaked?
(Such as call forwading?) If so, do you support
sending privacy information via the DIVERSION header?

Thanks for sharing.

Chris

On 6/4/08, Yuantao Zhang <yuantao.zhang at ericsson.com> wrote:
> Dear all
>
>
>
> INVITE sip:bob at biloxi.com SIP/2.0:5555
>
> INVITE sip:bob at biloxi.com SIP/2.0
>
>
>
> Above are 2 "Invite" request-line examples. In example one, it indicates
> a port number, 5555. What does the port number mean?
>
>
>
> Is it the port number of SIP proxy? Why we include port number here? The
> SIP proxy(biloxi.com) application layer who receives this "Invite"
> should receive this via port 5555 from lowe layer(UDP). Therefore, The
> SIP proxy(biloxi.com) application layer already know the port is 5555.
> Actualy, the SIP proxy application layer keeps listening port 5555.
>
>
>
> The second "Invite" request-line example is from RFC3261 and does not
> include port number. Can I say the port number is useless? So why
> example one includes a useless part in "Invite" request-line URL?
>
>
>
> Or is the port number is which the UAS is listening to? How the UAC
> knows it is 5555 if so?
>
>
>
> Any standard on this port number issue? Thanks.
>
>
>
> Best regards
>
> Steven
>
>

-- 
Sent from Gmail for mobile | mobile.google.com