Re: [Sofia-sip-devel] Sofia-Sip UA with Multiple Lines

Hello, Okay. I found that when I use NUTAG_M_USERNAME() tag, then the Contact header IS correct (I thought it wasn't)). So you can disregard this issue. Best Regards, Jerry -Original Message- From: Jerry Richards [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 13, 2008 12:23 PM T

Re: [Sofia-sip-devel] Sofia-Sip UA with Multiple Lines

Hello, Below you mentioned use of NUTAG_M_USERPART() to cause the Contact header to be correct when running multiple lines in a single agent. I see no NUTAG_M_USERPART() tag defined in sofia-sip (version 1.12.7). I did fine a NUTAG_M_USERNAME() tag, but this does not work with nua_invite(). Eve

[Sofia-sip-devel] sofia-sip changes (2008-02-13)

This posting was generated automatically from darcs repo . Wed Feb 13 16:23:24 EET 2008 Pekka Pessi <[EMAIL PROTECTED]> * nua_subnotref.c: do not terminate subscriptions immediately after receiving 200 OK to un-SUBSCRIBE M ./libsofia-sip-ua/nua/nua_su

Re: [Sofia-sip-devel] how to implement a statefull proxy?

Pekka Pessi ha scritto: > 2008/2/13, Antonio Gallo <[EMAIL PROTECTED]>: >> Now i route the "200 OK" but i don't get the ACK. I think the ACK is >> sent directly bypassing me because i didn't added any "Record-Route" >> stuff to the packets. >> I am correct? > Yep, that is right. For 2XX responses,

Re: [Sofia-sip-devel] how to implement a statefull proxy?

2008/2/13, Antonio Gallo <[EMAIL PROTECTED]>: > Now i route the "200 OK" but i don't get the ACK. I think the ACK is > sent directly bypassing me because i didn't added any "Record-Route" > stuff to the packets. > > I am correct? Yep, that is right. For 2XX responses, the ACK is sent directly to t

[Sofia-sip-devel] SIP Protocol checker

Do you use any tool to check if sofia-sip or the phones is sending out some broken SIP messages? - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go

Re: [Sofia-sip-devel] how to implement a statefull proxy?

Antonio Gallo ha scritto: > Pekka Pessi ha scritto: >> There is a bare-bones stateful proxy implementation in >> . Have a peek in it? > Peeked ;-) I can forward the message but no one of my callbacks is > invoked when the other side answer me with a 401. Ok i got it working ;-) dunno what happene

Re: [Sofia-sip-devel] how to implement a statefull proxy?

Pekka Pessi ha scritto: > There is a bare-bones stateful proxy implementation in > . Have a peek in it? Peeked ;-) I can forward the message but no one of my callbacks is invoked when the other side answer me with a 401. To forward INVITE from A to B i did this: case sip_method

Re: [Sofia-sip-devel] Notify Problem

2008/2/13, Pekka Pessi <[EMAIL PROTECTED]>: > The function nua_subscribe_client_response() in nua_subnotref.c has > code for handling the case with fetch (the initial SUBSCRIBE has > expire value 0). > > I guess you could remove the condition from the if (!eu->eu_notified) > branch like this and se

Re: [Sofia-sip-devel] how to implement a statefull proxy?

2008/2/13, Antonio Gallo <[EMAIL PROTECTED]>: > Hello, the NTA page show an example of a stateless proxy using 302 > REDIRECT stuffs. Instead i want to write a statefull proxy that will > stay into the message path using "Record-Route" header and "lr=" param. There is a bare-bones stateful proxy i

Re: [Sofia-sip-devel] Notify Problem

2008/2/13, rajeev k <[EMAIL PROTECTED]>: > I am using 1.12.7. The stack has a problem when removing a > subscription(expire value 0), that it will respond terminated notify > (Subscription-State: terminated) with '481 Call does not exists'. Has anyone > faced this? The function nua_subscribe_clien

[Sofia-sip-devel] how to implement a statefull proxy?

Hello, the NTA page show an example of a stateless proxy using 302 REDIRECT stuffs. Instead i want to write a statefull proxy that will stay into the message path using "Record-Route" header and "lr=" param. How do i do this for example for an INVITE? Its not clear with API i should use to rout

[Sofia-sip-devel] Notify Problem

Hi, I am using 1.12.7. The stack has a problem when removing a subscription(expire value 0), that it will respond terminated notify (Subscription-State: terminated) with '481 Call does not exists'. Has anyone faced this? Is this bug fixed in version 1.12.8? Thanks, - Rajeev --