[OpenSER-Users] Log errors when processing a contact list with RLSmodule
Anca Vamanu
anca at voice-system.ro
Thu Apr 17 11:17:43 CEST 2008
Hi,
Here you have the same problem in your configuration file, you should
accept in dialog SUBSCRIBE and NOTIFY requests that are directed to the
proxy.
I think that the example config file from 1.3.0 might have this mistake.
It was fixed but probably after the release. You should look at the
config from 1.3.1.
regards,
Anca
Pablo Guijarro Enríquez wrote:
> Hi Anca,
>
> Oops, you are right, sorry :p Now errors have disappeared, but there is
> something wrong. The notify messages sent as a result of the subscribe ones
> generated by the rls module for each of the contacts in the list are
> rejected with 404 responses. For example:
>
>
> SUBSCRIBE sip:800129 at comm.hi.inet SIP/2.0
> Via: SIP/2.0/UDP 10.95.43.31;branch=z9hG4bK16cd.9a07a1d1.0
> To: sip:800129 at comm.hi.inet
> From: sip:354354 at comm.hi.inet;tag=533cb9e91f4b999cf76861cbb9ed54ed-1a1a
> CSeq: 10 SUBSCRIBE
> Call-ID: 42e7a6e1-31560 at 10.95.43.31
> Content-Length: 0
> User-Agent: OpenSER (1.3.1-notls (i386/linux))
> Max-Forwards: 70
> Event: presence
> Contact: <sip:10.95.43.31>
> Expires: 3610
> Max-Forwards: 70
> Support: eventlist
>
>
> NOTIFY sip:10.95.43.31 SIP/2.0
> Via: SIP/2.0/UDP 10.95.43.31;branch=z9hG4bK975a.bb2427c3.0
> To: sip:354354 at comm.hi.inet;tag=533cb9e91f4b999cf76861cbb9ed54ed-1a1a
> From: sip:800129 at comm.hi.inet;tag=10.31561.1208325872.1
> CSeq: 1 NOTIFY
> Call-ID: 42e7a6e1-31560 at 10.95.43.31
> Content-Length: 0
> User-Agent: OpenSER (1.3.1-notls (i386/linux))
> Max-Forwards: 70
> Event: presence
> Contact: <sip:10.95.43.31>
> Subscription-State: active;expires=3600
>
>
> SIP/2.0 404 Not here
> Via: SIP/2.0/UDP 10.95.43.31;branch=z9hG4bK975a.bb2427c3.0
> To: sip:354354 at comm.hi.inet;tag=533cb9e91f4b999cf76861cbb9ed54ed-1a1a
> From: sip:800129 at comm.hi.inet;tag=10.31561.1208325872.1
> CSeq: 1 NOTIFY
> Call-ID: 42e7a6e1-31560 at 10.95.43.31
> Server: OpenSER (1.3.1-notls (i386/linux))
> Content-Length: 0
>
>
> What could be the reason for this to happen? It seems that openser does not
> want to handle that message or something... I have tried setting an alias
> for 10.95.43.31 in openser configuration file, but that did not work either.
>
> Log file is huge, so I cannot attach this whole part, just the end of it.
> Feel free to ask whatever data you may want to ckeck.
>
> Regards,
> Pablo
>
>
> -----Mensaje original-----
> De: Anca Vamanu [mailto:anca at voice-system.ro]
> Enviado el: viernes, 11 de abril de 2008 15:41
> Para: Pablo Guijarro Enríquez
> CC: users at lists.openser.org
> Asunto: Re: [OpenSER-Users] Log errors when processing a contact list with
> RLS module
>
> Hi Pablo,
>
> It is exactly the same error you mentioned with pua_xmpp :). RLS also
> depends on pua and since you have changed it .. You need to run a 'make
> proper' in the rls module directory and then compile it again.
>
> regards,
> Anca
>
>
> Pablo Guijarro Enríquez wrote:
>
>> Hi,
>>
>>
>>
>> I am running openser v1.3.1 and I cannot get the RLS module to work
>> properly when handling a contact list already retrieved from database.
>> Some errors related with the pua module appear in the log when the
>> server seems to be trying to generate the subscribe requests for each
>> of the contacts in the list (see attached, lines 60 to 62).
>>
>>
>>
>> Apr 10 13:02:23 comm ./openser[20184]: ERROR:pua:subs_build_hdr:
>> getting event from list
>>
>> Apr 10 13:02:23 comm ./openser[20184]: ERROR:pua:send_subscribe: while
>> building extra headers
>>
>> Apr 10 13:02:23 comm ./openser[20184]:
>> ERROR:rls:process_list_and_exec: infunction given as a parameter
>>
>>
>>
>> Those requests are never sent. What could this be due to?
>>
>>
>>
>> Thanks!
>>
>>
>>
>> Pablo
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.openser.org
>> http://lists.openser.org/cgi-bin/mailman/listinfo/users
>>
>>
>
>
More information about the sr-users
mailing list