[OpenSIPS-Users] B2BUA tests

Jeff Pyle jpyle at fidelityvoice.com
Fri Oct 30 14:52:58 CET 2009 

Fantastic.  You guys are rockstars.


Thanks,
Jeff



On 10/30/09 9:46 AM, "Anca Vamanu" <anca at opensips.org> wrote:

> Hi Jeff,
> 
> It does not help to do insert_hf after b2b_init since that INVITE will
> not be forwarded to the client. In fact if the b2b_init is successful
> you should exit from the script.
> But the finite number of headers is no longer valid. At the beginning of
> this week I have committed a patch that allows defining with a module
> parameter the extra headers that you want to be passed from one side to
> the other. The name of the parameter is "custom_headers". You have to
> take the trunk sources for this. The only modification from 1.6 branch
> is this addition.
> 
> Regards,
> Anca
> 
> Jeff Pyle wrote:
>> Anca,
>> 
>> Alright.  It's making more sense every moment.
>> 
>> I read on a post a few months ago about how either the B2BUA module or the
>> top-hiding scenario (can't remember which) passes only a finite number of
>> headers from one dialog to the other.  How might one manually pass through
>> specific, non-standard headers?  Is it as simple as saving them to a $var()
>> before b2b_init, and running insert_hf() after b2b_init?
>> 
>> 
>> - Jeff
>> 
>> 
>> 
>> On 10/30/09 6:11 AM, "Anca Vamanu" <anca at opensips.org> wrote:
>> 
>>   
>>> Hi Jeff,
>>> 
>>> Yes, you could surely do that also, use another server on the same
>>> machine ( it does not need to be a different machine but just a
>>> different server :) ).
>>> 
>>> Regards,
>>> Anca
>>> 
>>> Jeff Pyle wrote:
>>>     
>>>> Anca,
>>>> 
>>>> Great information.  I think I'm starting to get this.
>>>> 
>>>> Let me run this scenario past you.  As I've described, I have a functional
>>>> proxy that forwards INVITEs upstream to a PSTN gateway.  My original
>>>> intention was to use the top-hiding scenario to obscure the gateway's
>>>> information.  Instead of using a separate server to accomplish this, is
>>>> there any reason I couldn't forward the PSTN-bound request to a distinct
>>>> domain on the same server (t_relay to the same box) where the routing
>>>> behavior for this domain would be to change the RURI domain to the true
>>>> PSTN
>>>> gateway and b2b_init top-hiding?
>>>> 
>>>> 
>>>> Regards,
>>>> Jeff
>>>> 
>>>> 
>>>> 
>>>> On 10/29/09 5:02 AM, "Anca Vamanu" <anca at opensips.org> wrote:
>>>> 
>>>>   
>>>>       
>>>>> Hi Jeff,
>>>>> 
>>>>> You are right. You only need to call b2b_init function for the init
>>>>> request. But beware that the requests for that dialog will not get into
>>>>> the script anymore.
>>>>> You can read more details here:
>>>>> http://www.opensips.org/Resources/B2buaTutorial#toc17.
>>>>> If you are doing some other processing on the proxy, like accounting, it
>>>>> is advisable to move the B2BUA component on a separate server and to
>>>>> forward the requests to it.
>>>>> 
>>>>> Regards,
>>>>> Anca
>>>>> 
>>>>> Jeff Pyle wrote:
>>>>>     
>>>>>         
>>>>>> Hi Anca,
>>>>>> 
>>>>>> Please let me know if my train of thought makes sense.
>>>>>> 
>>>>>> I have a functional traditional proxy configuration where packets are
>>>>>> forwarded with t_relay, loose_route, etc.  If I wanted to convert this to
>>>>>> a
>>>>>> topology hiding B2BUA in Opensips, I would replace the t_relay of the
>>>>>> initial INVITE with a b2b_init.  That way, instead of statefully relaying
>>>>>> to
>>>>>> the UAS, I would be establishing a new dialog in B2BUA mode.
>>>>>> 
>>>>>> Am I on the right track?  Would I need to do anything to the current
>>>>>> loose_route section, or would all dialogs be translated automatically
>>>>>> without any modification?
>>>>>> 
>>>>>> 
>>>>>> - Jeff
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> On 10/28/09 4:48 AM, "Anca Vamanu" <anca at opensips.org> wrote:
>>>>>> 
>>>>>>   
>>>>>>       
>>>>>>           
>>>>>>> Hi Jeff,
>>>>>>> 
>>>>>>> I have completed the documentation on
>>>>>>> http://www.opensips.org/Resources/B2buaTutorial#toc12 with some schema.
>>>>>>> What happens in topology hiding is that the B2BUA starts a new dialog
>>>>>>> with the other party, so it will first send an INVITE message. Now, if
>>>>>>> you call b2b_init before you do lookup location and the target address
>>>>>>> is has in the domain part the domain of your sip proxy, then the INVITE
>>>>>>> will get back to the server and back in the script. For this case I was
>>>>>>> saying that you should not require authentication for it.
>>>>>>> And no, the B2BUA component does not have any type of authentication of
>>>>>>> its own, it only knows to put itself in the middle of the call and
>>>>>>> establish two dialogs, with each party.
>>>>>>> 
>>>>>>> Regards,
>>>>>>> Anca
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> Jeff Pyle wrote:
>>>>>>>     
>>>>>>>         
>>>>>>>            
>>>>>>>> Anca,
>>>>>>>> 
>>>>>>>> Does the B2BUA module have some type of authentication on its own?  Is
>>>>>>>> it
>>>>>>>> looping back to the top of the script and trying to authenticate
>>>>>>>> itself,
>>>>>>>> and
>>>>>>>> that's where your suggestion comes from?  Or something else?
>>>>>>>> 
>>>>>>>> It appears I don't have a good understanding of the message flow
>>>>>>>> through
>>>>>>>> Opensips in a B2BUA'd session.  At b2b_init time, does something return
>>>>>>>> to
>>>>>>>> the top of route[0] and start over?  As such should I run b2b_init as
>>>>>>>> close
>>>>>>>> to the top of route[0] as possible?
>>>>>>>> 
>>>>>>>> If you could help me understand what happens to the message flow in a
>>>>>>>> non-B2BUA session versus one that has B2BUA, perhaps I'll be able to my
>>>>>>>> mind
>>>>>>>> around this.
>>>>>>>> 
>>>>>>>> 
>>>>>>>> Thanks,
>>>>>>>> Jeff
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>> On 10/27/09 12:48 PM, "Anca Vamanu" <anca at opensips.org> wrote:
>>>>>>>> 
>>>>>>>>   
>>>>>>>>       
>>>>>>>>           
>>>>>>>>           
>>>>>>>>> Hi Jeff,
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> To get pass the problems with authentication I suggest you put a check
>>>>>>>>> in your configuration file:
>>>>>>>>> 
>>>>>>>>> if(src_ip== proxy_ip && src_port== proxy_port)
>>>>>>>>>     dont_ask_authetification;
>>>>>>>>> 
>>>>>>>>> Just to let it pass without challenging it and go to the part where
>>>>>>>>> the
>>>>>>>>> Invite is forwarded to the end user.
>>>>>>>>> 
>>>>>>>>> Regards,
>>>>>>>>> Anca
>>>>>>>>> 
>>>>>>>>>     
>>>>>>>>>         
>>>>>>>>>          
>>>>>>>>>          
>>>>>>> _______________________________________________
>>>>>>> Users mailing list
>>>>>>> Users at lists.opensips.org
>>>>>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>>>>>     
>>>>>>>         
>>>>>>>            
>>>>>> _______________________________________________
>>>>>> Users mailing list
>>>>>> Users at lists.opensips.org
>>>>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>>>> 
>>>>>>   
>>>>>>       
>>>>>>           
>>>>> _______________________________________________
>>>>> Users mailing list
>>>>> Users at lists.opensips.org
>>>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>>>     
>>>>>         
>>>> _______________________________________________
>>>> Users mailing list
>>>> Users at lists.opensips.org
>>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>> 
>>>>   
>>>>       
>>> _______________________________________________
>>> Users mailing list
>>> Users at lists.opensips.org
>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>     
>> 
>> 
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>> 
>>   
> 
> 
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users

More information about the Users mailing list