2007/9/27, Fabio Margarido <[EMAIL PROTECTED]>:
> Hi there,
>
> when my application receives a 180 with a Require header containing
> 100rel, the PRACK requests Sofia sends lacks the user part of the url
> of the From header, which causes the remote agent to respond with a
> 481.
That is interesti
2007/9/27, [EMAIL PROTECTED] <[EMAIL PROTECTED]>:
> when I call nta_outgoing_tcreate(), my network trace shows that
> Sofia-SIP selects TCP transport to send the message. I would like to
> understand why it does so, and I would also like to be able to enforce
> usage of UDP.
The RFC 3261 tries to
Hi there,
when I use nua with automatic SDP (soa) my application gets two
callbacks:
1. nua_i_invite --> signaling the reception of the invite message
2. nua_i_state --> reporting the parsing results of the SDP=20
SIP stack and phone-application run in separate processes.
On nua_i_invit
On 10/1/07, Pekka Pessi <[EMAIL PROTECTED]> wrote:
> That is interesting. How you set the From header when you send INVITE?
> A tag in nua_handle() or in nua_invite()? In any case, according to
> the spec it is O.K. to change the From URI as long as the From tag is
> kept same.
>
I've tried both,
Hello All,
Is there a list of NUA functions for which the application is required to
maintain a timer?
For example, if I call nua_invite() and the far-end/server does not reply
(or the far-end/server replies with 100 Trying, but never sends a follow-in
200 Ok or Bye), then the application will be
