(Python) SIP conference bot, anyone? ;-)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Attached you can see how I do it.

regards
klaus



Benny Prijono schrieb:
> On Tue, Aug 25, 2009 at 4:08 PM, Klaus
> Darilion<klaus.mailinglists at pernau.at> wrote:
>>
>> Benny Prijono schrieb:
>>> Okay, that is something that I don't understand. The MESSAGE sent by
>>> the bot does have Route: <sip:pjsip.org;transport=tcp>, since I wanted
>>> to use TCP. I also have "pjsip.org" as my alias in my openser.cfg. And
>>> I have this as well:
>>>
>>>        # record routing
>>>        if (!is_method("REGISTER|MESSAGE"))
>>>                record_route();
>>>
>>> So it should remove my Route, shouldn't it? (openser newbie here)
>> No. This just adds a record-route header.
>>
>> You should have somewhere in the beginning your config:
>>
>> ...
>>  if (loose_route()) {
>>     .....
>>     t_relay();
>>     exit;
>>  }
>> ...
>>
>> The loose_route function is not easy to understand.
> 
> Nor that I ever even try to understand it. :)
> 
> Turns out my "if(loose_route)" was put inside "if (has_totag())", I
> wonder why. Must be left over from a very old openser example.
> 
> Thanks
>  Benny
> 
> 
> Basically this function
>> checks if a route-set is announced by the client - i.e. if the request
>> contains a route header - as this would indicate that all the routing
>> information is already available and the request can be relayed (as it is
>> usually the case with in-dialog requests). If Route header is present, the
>> top-most route entry is removed.
>>
>> But there is one exception: If there is only 1 Route header, and the Route
>> header points to the proxy itself (Route URI domain equals one of the
>> aliases), and there is no totag (as with the MESSAGE), then the function
>> returns FALSE and the Route header is removed.
>>
>> regards
>> klaus
>>
>>
>>
>>> Anyway I now hide the Route header from the bot, it shouldn't be there
>>> anymore.
>>>
>>> Thanks
>>>  Benny
>>>
>>> On Tue, Aug 25, 2009 at 3:30 PM, Klaus
>>> Darilion<klaus.mailinglists at pernau.at> wrote:
>>>> As stated in the other email, the bug is in the pjsip.org SIP proxy.
>>>>
>>>> regards
>>>> klaus
>>>>
>>>> Benny Prijono schrieb:
>>>>> On Tue, Aug 25, 2009 at 1:18 PM, Klaus
>>>>> Darilion<klaus.mailinglists at pernau.at> wrote:
>>>>>>> Hint: send IM "--join" to join the chatroom (or "--help" for other
>>>>>>> commands), or just call it to join the voice conf. You don't need to
>>>>>>> register to pjsip.org SIP service to join the conf.
>>>>>> either it does not work or I am too stupid.
>>>>>> I do not get any responses (IMs) when sending "--help"
>>>>>>
>>>>> Obviously you must allow MESSAGE to get through from bot at pjsip.org to
>>>>> you?
>>>>>
>>>>> _______________________________________________
>>>>> Visit our blog: http://blog.pjsip.org
>>>>>
>>>>> pjsip mailing list
>>>>> pjsip at lists.pjsip.org
>>>>> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>>>> _______________________________________________
>>>> Visit our blog: http://blog.pjsip.org
>>>>
>>>> pjsip mailing list
>>>> pjsip at lists.pjsip.org
>>>> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>>>>
>>> _______________________________________________
>>> Visit our blog: http://blog.pjsip.org
>>>
>>> pjsip mailing list
>>> pjsip at lists.pjsip.org
>>> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>> _______________________________________________
>> Visit our blog: http://blog.pjsip.org
>>
>> pjsip mailing list
>> pjsip at lists.pjsip.org
>> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>>
> 
> _______________________________________________
> Visit our blog: http://blog.pjsip.org
> 
> pjsip mailing list
> pjsip at lists.pjsip.org
> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: loose_route.txt
URL: <http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20090825/cc7f6589/attachment-0001.txt>


[Index of Archives]     [Asterisk Users]     [Asterisk App Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [Linux API]
  Powered by Linux