[OpenSIPS-Devel] SF.net SVN: opensips:[7775] trunk/modules/b2b_logic

Ovidiu Sas osas at voipembedded.com
Fri Mar 4 21:09:37 CET 2011 

The dialog module requires the server to ruin in proxy mode.
The b2b modules are not running in proxy mode (there are different
transactions for the received message and the sent message).
In fact, the config for b2b should be very simple (see the one posed
on the tutorial page).

Regards,
Ovidiu Sas

On Fri, Mar 4, 2011 at 3:00 PM,  <a.zagorskiy at oyster-telecom.ru> wrote:
> Hi, Ovidiu.
>
> Could you explain why mixing dialog and b2b isn't a good idea?
> I think this should be written in docs in red color.
>
>
> Do you want to see full config?
>
>
>
> On Fri, 4 Mar 2011 12:21:31 -0500
>  Ovidiu Sas <osas at voipembedded.com> wrote:
>>
>> It seems that you are mixing dialog with b2b, which is not a good idea.
>> The issue that you are having here has nothing to do with my change.
>>
>> Can you post your config?
>>
>>
>> Regards,
>> Ovidiu Sas
>>
>> 2011/3/4 Anton Zagorskiy <a.zagorskiy at oyster-telecom.ru>:
>>>
>>> Full debug log for this call is 303Kb. Do you really need it all :) ?
>>>
>>>
>>> Shortly, on BYE request:
>>>
>>> [25509]: DBG:uac:restore_uri: Dialog found: 0x80416a818
>>> [25509]: DBG:dialog:fetch_dlg_value: looking for <vsf>
>>> [25509]: DBG:dialog:fetch_dlg_value: var found-> <>!
>>> [25509]: DBG:rr:is_direction: param ftag not found
>>> [25509]: DBG:uac:restore_uri: decoded uris are:
>>> new=[sip:xxxxxxxxxxx at 192.168.0.1] old=[sip:xxxxxxxxxxx at 192.168.0.1]
>>> [25509]: DBG:uac:restore_uri: Dialog found: 0x80416a818
>>> [25509]: DBG:dialog:fetch_dlg_value: looking for <vst>
>>> [25509]: DBG:dialog:fetch_dlg_value: var found-> <>!
>>> [25509]: ERROR:uac:restore_uri: new URI shorter than old URI
>>>
>>> Then, B2B resends BYE via loopback interface:
>>>
>>> [25512]: DBG:core:parse_msg: SIP Request:
>>> [25512]: DBG:core:parse_msg:  method:  <BYE>
>>> [25512]: DBG:core:parse_msg:  uri:
>>>
>>> <sip:192.168.0.1;lr=on;ftag=2cd29b5f31bb4ce67aea29e5fa24ff1d;did=6f2.243de2e
>>> 2>
>>> [25512]: DBG:core:parse_msg:  version: <SIP/2.0>
>>> [25512]: DBG:core:parse_headers: flags=2
>>> [25512]: DBG:core:parse_via_param: found param type 232, <branch> =
>>> <z9hG4bK6c16.0ce82964.0>; state=16
>>> [25512]: DBG:core:parse_via: end of header reached, state=5
>>> [25512]: DBG:core:parse_headers: via found, flags=2
>>> [25512]: DBG:core:parse_headers: this is the first via
>>> [25512]: DBG:core:receive_msg: After parse_msg...
>>> [25512]: DBG:core:receive_msg: preparing to run routing scripts...
>>> [25512]: DBG:core:parse_headers: flags=ffffffffffffffff
>>> [25512]: DBG:core:parse_via_param: found param type 234, <received> =
>>> <192.168.0.2>; state=6
>>> [25512]: DBG:core:parse_via_param: found param type 232, <branch> =
>>> <z9hG4bK0a7b76b8>; state=6
>>> [25512]: DBG:core:parse_via_param: found param type 235, <rport> =
>>> <5060>;
>>> state=16
>>> [25512]: DBG:core:parse_via: end of header reached, state=5
>>> [25512]: DBG:core:parse_headers: via found, flags=ffffffffffffffff
>>> [25512]: DBG:core:parse_headers: parse_headers: this is the second via
>>> [25512]: DBG:core:parse_to_param: tag=2cd29b5f31bb4ce67aea29e5fa24ff1d
>>> [25512]: DBG:core:parse_to: end of header reached, state=29
>>> [25512]: DBG:core:parse_to: display={"test"}, ruri={sip:100 at mydomain.com}
>>> [25512]: DBG:core:get_hdr_field: <To> [90]; uri=[sip:100 at mydomain.com]
>>> [25512]: DBG:core:get_hdr_field: to body ["test" <sip:100 at mydomain.com>]
>>> [25512]: DBG:core:get_hdr_field: cseq <CSeq>: <102> <BYE>
>>> [25512]: DBG:core:get_hdr_field: content_length=0
>>> [25512]: DBG:core:get_hdr_field: found end of header
>>> [25512]: DBG:b2b_entities:b2b_prescript_f: start - method = BYE
>>> [25512]: DBG:b2b_entities:b2b_prescript_f: <uri> host:port
>>> [192.168.0.1][0]
>>> [25512]: DBG:b2b_entities:b2b_prescript_f: <socket> address:port
>>> [192.168.0.1][5060]
>>> [25512]: ERROR:core:parse_to: unexpected char [.] in status 6:
>>> <<<sip:xxxxxxxxxxx at 192.168.0.1>> .
>>> [25512]: ERROR:core:parse_from_header: bad from header
>>> [25512]: DBG:core:set_err_info: ec: 1, el: 3, ei: 'error parsing From
>>> header'
>>> [25512]: ERROR:b2b_entities:b2b_prescript_f: cannot parse From header
>>>
>>> (Here I'm trying to print From header to the log)
>>> [25512]: ERROR:core:parse_to: unexpected char [.] in status 6:
>>> <<<sip:xxxxxxxxxxx at 192.168.0.1>> .
>>> [25512]: ERROR:core:parse_from_header: bad from header
>>> [25512]: DBG:core:set_err_info: ec: 1, el: 3, ei: 'error parsing From
>>> header'
>>> [25512]: ERROR:core:pv_get_from_attr: cannot parse From header
>>>
>>>
>>>
>>>
>>>
>>> WBR, Anton Zagorskiy
>>> VoIP Developer, Oyster Telecom
>>> Phone.: +7 812 601-0666
>>> Fax: +7 812 601-0593
>>> a.zagorskiy at oyster-telecom.ru
>>> www.oyster-telecom.ru
>>>
>>>
>>>
>>>> -----Original Message-----
>>>> From: sip.nslu at gmail.com [mailto:sip.nslu at gmail.com] On Behalf Of
>>>> Ovidiu Sas
>>>> Sent: Friday, March 04, 2011 6:36 PM
>>>> To: Anton Zagorskiy
>>>> Cc: OpenSIPS devel mailling list
>>>> Subject: Re: [OpenSIPS-Devel] SF.net SVN: opensips:[7775]
>>>> trunk/modules/b2b_logic
>>>>
>>>> That's strange.  Can you post your full debug logs?
>>>> I have tested the following scenarios and all worked ok for me:
>>>>  1. param not defined
>>>>  2. param defined and not set
>>>>  3. param defined and set
>>>>
>>>> On scenario 2 there is a small issue (an error is printed out about
>>>> the PV not being a uri) but all the messages are ok.
>>>>
>>>>
>>>> Regards,
>>>> Ovidiu Sas
>>>>
>>>> 2011/3/4 Anton Zagorskiy <a.zagorskiy at oyster-telecom.ru>:
>>>> > Hi, Ovidiu.
>>>> >
>>>> > I've just got the latest svn trunk and got that situation without
>>>> changing
>>>> > any parameters.
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >> -----Original Message-----
>>>> >> From: sip.nslu at gmail.com [mailto:sip.nslu at gmail.com] On Behalf Of
>>>> >> Ovidiu Sas
>>>> >> Sent: Friday, March 04, 2011 6:16 PM
>>>> >> To: OpenSIPS devel mailling list
>>>> >> Cc: Anton Zagorskiy
>>>> >> Subject: Re: [OpenSIPS-Devel] SF.net SVN: opensips:[7775]
>>>> >> trunk/modules/b2b_logic
>>>> >>
>>>> >> Are you saying that you set up the "b2bl_from_spec_param" and you
>>>> got
>>>> >> an error?
>>>> >>
>>>> >> Regards,
>>>> >> Ovidiu Sas
>>>> >>
>>>> >> On Fri, Mar 4, 2011 at 10:05 AM, Anton Zagorskiy
>>>> >> <a.zagorskiy at oyster-telecom.ru> wrote:
>>>> >> > Hi.
>>>> >> >
>>>> >> > I think it is you fix: I'm using top hiding and on BYE request b2b
>>>> >> sends in
>>>> >> > the lo interface BYE request with extra zeroes in a FROM header.
>>>> >> >
>>>> >> > Like this: From: "xxx" <sip:xxxxx at 192.168.0.1\0000\0000\0000\000>
>>>> >> >
>>>> >> >
>>>> >> >> -----Original Message-----
>>>> >> >> From: devel-bounces at lists.opensips.org [mailto:devel-
>>>> >> >> bounces at lists.opensips.org] On Behalf Of Ovidiu Sas
>>>> >> >> Sent: Thursday, March 03, 2011 7:05 PM
>>>> >> >> To: devel at lists.opensips.org
>>>> >> >> Subject: [OpenSIPS-Devel] SF.net SVN: opensips:[7775]
>>>> >> >> trunk/modules/b2b_logic
>>>> >> >>
>>>> >> >> Revision: 7775
>>>> >> >>
>>>> >> >> http://opensips.svn.sourceforge.net/opensips/?rev=7775&view=rev
>>>> >> >> Author:   osas
>>>> >> >> Date:     2011-03-03 16:05:29 +0000 (Thu, 03 Mar 2011)
>>>> >> >>
>>>> >> >> Log Message:
>>>> >> >> -----------
>>>> >> >> b2b_logic: new param "b2bl_from_spec_param"
>>>> >> >>
>>>> >> >>  - This new param allows setting a custom "From" header for the
>>>> >> >> outgoing INVITE
>>>> >> >>
>>>> >> >> Modified Paths:
>>>> >> >> --------------
>>>> >> >>     trunk/modules/b2b_logic/b2b_logic.c
>>>> >> >>     trunk/modules/b2b_logic/logic.c
>>>> >> >>
>>>> >> >>
>>>> >> >> This was sent by the SourceForge.net collaborative development
>>>> >> >> platform, the world's largest Open Source development site.
>>>> >> >>
>>>> >> >> _______________________________________________
>>>> >> >> Devel mailing list
>>>> >> >> Devel at lists.opensips.org
>>>> >> >> http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
>>>> >> >
>>>> >> >
>>>> >> > _______________________________________________
>>>> >> > Devel mailing list
>>>> >> > Devel at lists.opensips.org
>>>> >> > http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
>>>> >> >
>>>> >
>>>> >
>>>
>>>
>
>

More information about the Devel mailing list