[OpenSIPS-Users] Limitations of b2b_entities?

[Anca Vamanu]

Hi Takeshi,

This was something easy to do so I added the support for this - I 
extended the client_info structure with 3 more fields: to_dname, 
from_dname ( here you should put the display name) and req_uri for 
Request URI. The to_uri and from_uri fields must really contain a URI.
Check it out.
It would be nice if you would also make your perl/lua code controlling 
b2b_entities module public.

Regards,

-- 
Anca Vamanu
www.voice-system.ro



On 07/19/2010 07:07 AM, mayamatakeshi wrote:
> Hello,
> I'm playing with the module b2b_entities. I was thinking in writing 
> some perl/lua code to control UA entities provided by this module.
> However, I am seeing some shortcomings/bugs in it:
>
> 1) If I pass
>  "\"user1\"<sip:user1 at test1.com <mailto:sip%3Auser1 at test1.com>>" as 
> from_uri to function client_new, it will be rendered as this in the 
> request:
>   From: <"user1"<sip:user1 at test1.com 
> <mailto:sip%3Auser1 at test1.com>>>;tag=a34656f511fe5edd5d76196c64f246a7-aba5
>
> (obs: to_uri is free from this problem:
>   to_uri = "\"user2\"<sip:user2 at 192.168.2.126 
> <mailto:sip%3Auser2 at 192.168.2.126>>" -> To: 
> "user2"<sip:user2 at 192.168.2.126 <mailto:sip%3Auser2 at 192.168.2.126>>)
>
> 2) function client_new doesn't permit to specify the Request-URI. 
> There are situations where Request-URI will have to be set differently 
> from To-Uri (I know at least the case where some PSTN-GWs recognises 
> RURI-Username != To-URI-Username as redirection indication).
>
> I just thought to highlight those points, so that they could be 
> improved in the future.
>
> regards,
> takeshi
>
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>    
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.opensips.org/pipermail/users/attachments/20100719/b9edab16/attachment.htm