Hi Osiris, The uri that is put in RURI for Publish(presentity uri) is the uri in To header of the Notify. You can not change that. If you want the Publish to be sent to a certain IP, you can set the module parameter ''presence_server" in module pua_bla to that address. If you really want to set another presentity uri then you could catch the Publish in local route and change it there.
Regards, -- Anca Vamanu www.voice-system.ro osiris123d wrote: > I am trying to test and set up BLA and followed the following config > http://www.opensips.org/Resources/PuaBlaConfig > > I am noticing that when my phone sends the notify and it executes the > bla_handle_notify() OpenSIPS is sending the publish to the actual domain > name IP address instead of the actual IP address thats in the location > table. Here is an example > > U 2010/05/25 20:01:23.568868 1XX.XXX.XXX.134:5060 -> 75.X.X.15X:2053 > SUBSCRIBE sip:[email protected]:2053;line=293pwn59 SIP/2.0. > Via: SIP/2.0/UDP 1XX.XXX.XXX.134;branch=z9hG4bK2df4.72cce6b.0. > To: sip:[email protected]. > From: <sip:[email protected]>;tag=144b207508c0e0296792f226e399eaf5-9670. > CSeq: 10 SUBSCRIBE. > Call-ID: [email protected]. > Content-Length: 0. > User-Agent: OpenSIPS (1.6.2-notls (x86_64/linux)). > Max-Forwards: 70. > Event: dialog;sla. > Contact: <sip:1XX.XXX.XXX.134:5060>. > Expires: 3610. > . > > # > U 2010/05/25 20:01:23.639853 75.X.X.15X:2053 -> 1XX.XXX.XXX.134:5060 > SIP/2.0 200 OK. > Via: SIP/2.0/UDP 1XX.XXX.XXX.134;branch=z9hG4bK2df4.72cce6b.0. > From: <sip:[email protected]>;tag=144b207508c0e0296792f226e399eaf5-9670. > To: sip:[email protected];tag=k87elwiitr. > Call-ID: [email protected]. > CSeq: 10 SUBSCRIBE. > Contact: <sip:[email protected]:2053;line=293pwn59>. > Expires: 3610. > Content-Length: 0. > . > > # > U 2010/05/25 20:01:23.653515 75.X.X.15X:2053 -> 1XX.XXX.XXX.134:5060 > NOTIFY sip:1XX.XXX.XXX.134:5060 SIP/2.0. > Via: SIP/2.0/UDP 192.168.0.7:2053;branch=z9hG4bK-77nm5w2yoeob;rport. > From: sip:[email protected];tag=k87elwiitr. > To: <sip:[email protected]>;tag=144b207508c0e0296792f226e399eaf5-9670. > Call-ID: [email protected]. > CSeq: 1 NOTIFY. > Max-Forwards: 70. > Contact: <sip:[email protected]:2053;line=293pwn59>;reg-id=1. > Event: dialog;sla. > Subscription-State: active. > Content-Type: application/dialog-info+xml. > Content-Length: 152. > . > <?xml version="1.0"?> > <dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="0" > state="full" entity="sip:[email protected]"></dialog-info> > > # > U 2010/05/25 20:01:23.691668 1XX.XXX.XXX.134:5060 -> 75.X.X.15X:2053 > SIP/2.0 200 OK. > Via: SIP/2.0/UDP > 192.168.0.7:2053;branch=z9hG4bK-c63fix17ewk4;rport=2053;received=75.X.X.15X. > From: "Blah Blah" <sip:[email protected]>;tag=bnfufrbb7w. > To: "Blah Blah" > <sip:[email protected]>;tag=fa9ad7a35cf4c9d5a26f33f3220f505e.690f. > Call-ID: 3c26704f19b6-ih2vdtwqqd1u. > CSeq: 2 REGISTER. > Contact: > <sip:[email protected]:2053;line=293pwn59>;q=0.5;expires=3600;received="sip:75.X.X.15X:2053". > Server: AE SIP Proxy. > Content-Length: 0. > . > > # > U 2010/05/25 20:01:23.715677 1XX.XXX.XXX.134:5060 -> 97.74.144.17:5060 > PUBLISH sip:[email protected] SIP/2.0. > Via: SIP/2.0/UDP 1XX.XXX.XXX.134;branch=z9hG4bK5d36.1de80852.0. > To: sip:[email protected]. > From: <sip:[email protected]>;tag=144b207508c0e0296792f226e399eaf5-8f7a. > CSeq: 10 PUBLISH. > Call-ID: [email protected]. > Content-Length: 139. > User-Agent: OpenSIPS (1.6.2-notls (x86_64/linux)). > Max-Forwards: 70. > Event: dialog;sla. > Expires: 3601. > Content-Type: application/dialog-info+xml. > Sender: sip:[email protected]:2053;line=293pwn59. > . > <?xml version="1.0"?> > <dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="0" > state="full" entity="sip:[email protected]"/> > > > > Since I am following the instructions from the link above what function am I > missing to make the publish get sent to the CONTACT or RECIEVED uri located > in the Location Database?? > _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
