Re: [OpenSIPS-Users] OpenSIPs behind a firewall

[Raúl Alexis Betancor Santana]

On Wednesday 07 October 2009 22:56:06 Daniel Goepp wrote:
> Thanks for the information, that seems to at least change the Via, but
> RTPproxy is still not handling this well.  It will only give it's
> private IP back to OpenSIPS, so I end up wtih:
>
> Connection Information (c): IN IP4 10.250.7.164
>
> I will try and see if I can work around this on the RTPproxy side of
> things.

You will have tons and tons of problems runing an rtpproxy on a private IP, 
more than the ones you will be able to solve.

RTPProxy was designed to BE on a public IP.

Ask your provider to give you some sort of /29 or /28 IP pool and work with 
that, otherwise you will end with headhache.

-- 
Raúl Alexis Betancor Santana
Dimensión Virtual

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] OpenSIPs behind a firewall

[Bogdan-Andrei Iancu]

Hi Daniel,

Try using set_advertised_address() before sending the call out.
  http://www.opensips.org/Resources/DocsCoreFcn#toc125

or use the record_route_preset() function :
 http://www.opensips.org/html/docs/modules/devel/rr.html#id228590

Regards,
Bogdan

Daniel Goepp wrote:
> After further investigation, this only updating the Via header, but
> the RR is remaining untouched:
>
> Record-Route: 
>
> Ideas about how I might get this field updated correctly?
>
> Thanks
>
> -dg
>
> On Wed, Oct 7, 2009 at 2:10 PM, Bogdan-Andrei Iancu
>  wrote:
>   
>> Hi Daniel,
>>
>> try using the advertise_address and advertise_port to force opensips in
>> using the public IPs of the NAT:
>>http://www.opensips.org/Resources/DocsCoreFcn#toc24
>>
>> Regards,
>> Bogdan
>>
>> Daniel Goepp wrote:
>> 
>>> I am trying to setup OpenSIPs to run behind a firewall, and not
>>> finding much information regarding how to get OpenSIPs to be aware of
>>> the public IP for it's signaling.  The firewall is setup with a 1 to 1
>>> NAT for the public and private IPs, and right now all udp and tcp
>>> traffic is being passed directly through.  Has anyone successfully
>>> gotten OpenSIPs setup like this?  If so, can you please provide any
>>> information on how it was setup.
>>>
>>> TIA
>>>
>>> -dg
>>>
>>> ___
>>> Users mailing list
>>> Users@lists.opensips.org
>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>
>>>
>>>   
>> ___
>> Users mailing list
>> Users@lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>> 
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>   


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] OpenSIPs behind a firewall

[Bogdan-Andrei Iancu]

Hi Daniel,

if you want to have rtpproxy in bridging mode, you need to indicate (in 
force_rtp_proxy() ) what interface to be used via the "e" and "i" flags 
(external/internal). See:
http://www.opensips.org/html/docs/modules/1.5.x/nathelper.html#id271055

Regards,
Bogdan

Daniel Goepp wrote:
> Thanks for the information, that seems to at least change the Via, but
> RTPproxy is still not handling this well.  It will only give it's
> private IP back to OpenSIPS, so I end up wtih:
>
> Connection Information (c): IN IP4 10.250.7.164
>
> I will try and see if I can work around this on the RTPproxy side of things.
>
> -dg
>
> On Wed, Oct 7, 2009 at 2:10 PM, Bogdan-Andrei Iancu
>  wrote:
>   
>> Hi Daniel,
>>
>> try using the advertise_address and advertise_port to force opensips in
>> using the public IPs of the NAT:
>>http://www.opensips.org/Resources/DocsCoreFcn#toc24
>>
>> Regards,
>> Bogdan
>>
>> Daniel Goepp wrote:
>> 
>>> I am trying to setup OpenSIPs to run behind a firewall, and not
>>> finding much information regarding how to get OpenSIPs to be aware of
>>> the public IP for it's signaling.  The firewall is setup with a 1 to 1
>>> NAT for the public and private IPs, and right now all udp and tcp
>>> traffic is being passed directly through.  Has anyone successfully
>>> gotten OpenSIPs setup like this?  If so, can you please provide any
>>> information on how it was setup.
>>>
>>> TIA
>>>
>>> -dg
>>>
>>> ___
>>> Users mailing list
>>> Users@lists.opensips.org
>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>
>>>
>>>   
>> ___
>> Users mailing list
>> Users@lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>> 
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>   


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] SIP trace and OpenSIPS-CP 2.0

[Bogdan-Andrei Iancu]

Hi Marc,


marcher wrote:
> Hi Bogdan,
>
> I appreciate you taking the time to answer my basic questions in getting
> opensips-cp functional with my opensips implementation.
>
> I had read the link you included, but its still not clear to me where the
> sip_trace function should be called within the opensips config file.
>   
there is not special place for it - you need to call the sip_trance() 
and set the trace flag when you process the SIP requests - you can do 
this in the very beginning of the script or just before sending the 
request out - it is up to you and up to what kind of traffic you want to 
trace.

For example, if you want to trace only calls to your local subscribers, 
you can add the sip_trace() in the if (ruri==myself) {} block.
> My opensips config file is very straightforward, based heavily on the
> distribution sample, but adding piecemeal the config necessary to integrate
> opensips-cp (mi_xmlrpc, dialplan, drouting and siptrace modules to date) I
> also wish to add in SIP trunking gateways using drouting.
>   
you do not need to put in the opensips script all the functionalities 
required by opensips-cp. You can select in opensips-cp only the tools 
you find useful in your opensips script. If you do not need drouting in 
opensips cfg, simply remove the drouting tool from CP.
> To that end, I am also struggling with the correct opensips config to
> implement drouting such that it works in tandem with the lookup(location)
> functionality.
>   
Could you describe a bit more the logic you want here?
> Does there exist a sample config that I could work from that would achieve
> these goals? I'm surprised the folks that produced opensips-cp didn't post
> an opensips config file that would successfully work in tandem with their
> GUI.
>   
because this is impossible :)...opensips-cp allows you to provision some 
functionality blocks (like dialplan, drouting, nathelper, permissions, 
etc). In your opensips cfg you can combine in millions of ways these 
block to get different overall routing logic.

Regards,
Bogdan

> Thanks again.
>
> Cheers,
>
> Marc
>
>
> Bogdan-Andrei Iancu wrote:
>   
>> Hi Marc,
>>
>> loading the siptrace module is not enough. You need to use the 
>> sip_trace() function and set the trace_flag (for transaction tracing).
>> See:
>> http://www.opensips.org/html/docs/modules/1.5.x/siptrace.html#id228291
>>
>> Best regards,
>> Bogdan
>>
>> marcher wrote:
>> 
>>> Hi,
>>>
>>> Trying to get sip trace functionality on opensips-cp working also. 
>>>
>>> Toggling the trace on and off from the web interface appears to be
>>> working
>>> fine.
>>>
>>> Oct  7 13:08:59 [2332] DBG:mi_xmlrpc:default_method: starting up.
>>> Oct  7 13:08:59 [2332] DBG:mi_xmlrpc:default_method: done looking the mi
>>> command.
>>> Oct  7 13:08:59 [2332] DBG:mi_xmlrpc:default_method: done parsing the mi
>>> tree.
>>> Oct  7 13:08:59 [2332] DBG:mi_xmlrpc:default_method: done running the mi
>>> command.
>>> Oct  7 13:08:59 [2332] DBG:mi_xmlrpc:default_method: done building
>>> response.
>>>
>>> However, nothing gets written to the mysql db siptrace table. 
>>>
>>> Hence, nothing gets written to the siptrace table on opensip-cp.
>>>
>>> I'm testing it with SJPhone registering to opensips from the same local
>>> machine.
>>>
>>> I added the following parameters to opensips.cfg
>>>
>>> loadmodule "siptrace.so"
>>>
>>> #-- siptrace db url 
>>> modparam("siptrace", "db_url","mysql://root:###...@localhost/opensips")
>>>
>>> Is this the correct format for the siptrace db_url? 
>>>
>>> The only thing I see in the log that looks related is:
>>>
>>> Oct  7 13:02:53 [2324] DBG:siptrace:trace_sl_onreply_out: trace off...
>>>
>>> For the drouting module, I have the db_url configured as 
>>>
>>> modparam("drouting",
>>> "db_url","mysql://opensips:opensip...@localhost/opensips")
>>>
>>> I did try changing the siptrace db_url to this format, but it didn't work
>>> either.
>>>
>>> Any help greatly appreciated.
>>>
>>> Cheers,
>>>
>>> Marc
>>>
>>>
>>> Iulia Bublea-2 wrote:
>>>   
>>>   
 Load the siptrace module in the opensips.cfg and set the db parameter.

 Iulia

 Gavin Henry wrote:
 
 
> Quick one,
>
> I presume you need the sip_trace function in the right place and that
> you just toggle it on/off via the cp?
>
> Also, you will need the db_url if logging to mysql?
>
> Thanks.
>
>   
>   
>   
 ___
 Users mailing list
 Users@lists.opensips.org
 http://lists.opensips.org/cgi-bin/mailman/listinfo/users


 
 
>>>   
>>>   
>> ___
>> Users mailing list
>> Users@lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
>> 
>
>   


___
Users mailing list
Users@lists.opensips.org
http://lists.opens

Re: [OpenSIPS-Users] Mediaproxy stop working

[Leon Li]

Forget to add, the error when making a call is as below.

 

Oct  8 15:53:18 debian /sbin/opensips[2906]: Media Session starts

Oct  8 15:53:18 debian media-dispatcher[2780]: error: Error processing
request: No suitable relay found

Oct  8 15:53:18 debian /sbin/opensips[2906]:
ERROR:mediaproxy:use_media_proxy: mediaproxy returned error

 

Regards,

Leon 

 

From: users-boun...@lists.opensips.org
[mailto:users-boun...@lists.opensips.org] On Behalf Of Leon Li
Sent: Thursday, 8 October 2009 3:43 PM
To: OpenSIPS users mailling list
Subject: [OpenSIPS-Users] Mediaproxy stop working

 

Hi,

 

My mediaproxy is just stop working for no reason, after my testing
server (opensips+dispatcher+relay) changed IP address. I modified
/etc/mediaproxy/config.ini with new IP as below.

 

[Relay]

dispactchers = public IP

relay_ip = public IP

log_level = DEBUG

[Dispatcher]

socket_path = dispatcher.sock

log_level = DEBUG

[TLS]

certs_path = /etc/mediaproxy/tls

[Database]

[Radius]

[OpenSIPS]

socket_path = '/var/run/mediaproxy/dispatcher.sock'

 

And syslog shows no sign of "adding dispatcher or relay".

 

Oct  8 15:39:28 debian media-relay[2794]: Log opened.

Oct  8 15:39:28 debian media-relay[2794]: Starting MediaProxy Relay
2.3.6

Oct  8 15:39:31 debian media-dispatcher[2780]: Twisted is using
epollreactor

Oct  8 15:39:31 debian media-dispatcher[2780]:
mediaproxy.dispatcher.RelayFactory starting on 25060

Oct  8 15:39:31 debian media-dispatcher[2780]:
mediaproxy.dispatcher.OpenSIPSControlFactory starting on
"'/var/run/mediaproxy/dispatcher.sock'"

Oct  8 15:39:31 debian media-dispatcher[2780]:
mediaproxy.dispatcher.ManagementControlFactory starting on 25061

Oct  8 15:39:32 debian media-relay[2794]: Set resource limit for maximum
open file descriptors to 11000

 

Nothing else has really been changed except OpenSIPs config for PSTN
call control, which I don't think related to mediaproxy. Any clues?

 

Thanks

Leon

 

 

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] Mediaproxy stop working

[Leon Li]

Hi,

 

My mediaproxy is just stop working for no reason, after my testing
server (opensips+dispatcher+relay) changed IP address. I modified
/etc/mediaproxy/config.ini with new IP as below.

 

[Relay]

dispactchers = public IP

relay_ip = public IP

log_level = DEBUG

[Dispatcher]

socket_path = dispatcher.sock

log_level = DEBUG

[TLS]

certs_path = /etc/mediaproxy/tls

[Database]

[Radius]

[OpenSIPS]

socket_path = '/var/run/mediaproxy/dispatcher.sock'

 

And syslog shows no sign of "adding dispatcher or relay".

 

Oct  8 15:39:28 debian media-relay[2794]: Log opened.

Oct  8 15:39:28 debian media-relay[2794]: Starting MediaProxy Relay
2.3.6

Oct  8 15:39:31 debian media-dispatcher[2780]: Twisted is using
epollreactor

Oct  8 15:39:31 debian media-dispatcher[2780]:
mediaproxy.dispatcher.RelayFactory starting on 25060

Oct  8 15:39:31 debian media-dispatcher[2780]:
mediaproxy.dispatcher.OpenSIPSControlFactory starting on
"'/var/run/mediaproxy/dispatcher.sock'"

Oct  8 15:39:31 debian media-dispatcher[2780]:
mediaproxy.dispatcher.ManagementControlFactory starting on 25061

Oct  8 15:39:32 debian media-relay[2794]: Set resource limit for maximum
open file descriptors to 11000

 

Nothing else has really been changed except OpenSIPs config for PSTN
call control, which I don't think related to mediaproxy. Any clues?

 

Thanks

Leon

 

 

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] SIP trace and OpenSIPS-CP 2.0

[marcher]

Hi Bogdan,

I appreciate you taking the time to answer my basic questions in getting
opensips-cp functional with my opensips implementation.

I had read the link you included, but its still not clear to me where the
sip_trace function should be called within the opensips config file.

My opensips config file is very straightforward, based heavily on the
distribution sample, but adding piecemeal the config necessary to integrate
opensips-cp (mi_xmlrpc, dialplan, drouting and siptrace modules to date) I
also wish to add in SIP trunking gateways using drouting.

To that end, I am also struggling with the correct opensips config to
implement drouting such that it works in tandem with the lookup(location)
functionality.

Does there exist a sample config that I could work from that would achieve
these goals? I'm surprised the folks that produced opensips-cp didn't post
an opensips config file that would successfully work in tandem with their
GUI.

Thanks again.

Cheers,

Marc


Bogdan-Andrei Iancu wrote:
> 
> Hi Marc,
> 
> loading the siptrace module is not enough. You need to use the 
> sip_trace() function and set the trace_flag (for transaction tracing).
> See:
> http://www.opensips.org/html/docs/modules/1.5.x/siptrace.html#id228291
> 
> Best regards,
> Bogdan
> 
> marcher wrote:
>> Hi,
>>
>> Trying to get sip trace functionality on opensips-cp working also. 
>>
>> Toggling the trace on and off from the web interface appears to be
>> working
>> fine.
>>
>> Oct  7 13:08:59 [2332] DBG:mi_xmlrpc:default_method: starting up.
>> Oct  7 13:08:59 [2332] DBG:mi_xmlrpc:default_method: done looking the mi
>> command.
>> Oct  7 13:08:59 [2332] DBG:mi_xmlrpc:default_method: done parsing the mi
>> tree.
>> Oct  7 13:08:59 [2332] DBG:mi_xmlrpc:default_method: done running the mi
>> command.
>> Oct  7 13:08:59 [2332] DBG:mi_xmlrpc:default_method: done building
>> response.
>>
>> However, nothing gets written to the mysql db siptrace table. 
>>
>> Hence, nothing gets written to the siptrace table on opensip-cp.
>>
>> I'm testing it with SJPhone registering to opensips from the same local
>> machine.
>>
>> I added the following parameters to opensips.cfg
>>
>> loadmodule "siptrace.so"
>>
>> #-- siptrace db url 
>> modparam("siptrace", "db_url","mysql://root:###...@localhost/opensips")
>>
>> Is this the correct format for the siptrace db_url? 
>>
>> The only thing I see in the log that looks related is:
>>
>> Oct  7 13:02:53 [2324] DBG:siptrace:trace_sl_onreply_out: trace off...
>>
>> For the drouting module, I have the db_url configured as 
>>
>> modparam("drouting",
>> "db_url","mysql://opensips:opensip...@localhost/opensips")
>>
>> I did try changing the siptrace db_url to this format, but it didn't work
>> either.
>>
>> Any help greatly appreciated.
>>
>> Cheers,
>>
>> Marc
>>
>>
>> Iulia Bublea-2 wrote:
>>   
>>> Load the siptrace module in the opensips.cfg and set the db parameter.
>>>
>>> Iulia
>>>
>>> Gavin Henry wrote:
>>> 
 Quick one,

 I presume you need the sip_trace function in the right place and that
 you just toggle it on/off via the cp?

 Also, you will need the db_url if logging to mysql?

 Thanks.

   
   
>>> ___
>>> Users mailing list
>>> Users@lists.opensips.org
>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>
>>>
>>> 
>>
>>   
> 
> 
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> 
> 

-- 
View this message in context: 
http://n2.nabble.com/SIP-trace-and-OpenSIPS-CP-2-0-tp3063389p3785337.html
Sent from the OpenSIPS - Users mailing list archive at Nabble.com.

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] OpenSIPs behind a firewall

[Daniel Goepp]

After further investigation, this only updating the Via header, but
the RR is remaining untouched:

Record-Route: 

Ideas about how I might get this field updated correctly?

Thanks

-dg

On Wed, Oct 7, 2009 at 2:10 PM, Bogdan-Andrei Iancu
 wrote:
> Hi Daniel,
>
> try using the advertise_address and advertise_port to force opensips in
> using the public IPs of the NAT:
>    http://www.opensips.org/Resources/DocsCoreFcn#toc24
>
> Regards,
> Bogdan
>
> Daniel Goepp wrote:
>> I am trying to setup OpenSIPs to run behind a firewall, and not
>> finding much information regarding how to get OpenSIPs to be aware of
>> the public IP for it's signaling.  The firewall is setup with a 1 to 1
>> NAT for the public and private IPs, and right now all udp and tcp
>> traffic is being passed directly through.  Has anyone successfully
>> gotten OpenSIPs setup like this?  If so, can you please provide any
>> information on how it was setup.
>>
>> TIA
>>
>> -dg
>>
>> ___
>> Users mailing list
>> Users@lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] OpenSIPs behind a firewall

[Daniel Goepp]

Thanks for the information, that seems to at least change the Via, but
RTPproxy is still not handling this well.  It will only give it's
private IP back to OpenSIPS, so I end up wtih:

Connection Information (c): IN IP4 10.250.7.164

I will try and see if I can work around this on the RTPproxy side of things.

-dg

On Wed, Oct 7, 2009 at 2:10 PM, Bogdan-Andrei Iancu
 wrote:
> Hi Daniel,
>
> try using the advertise_address and advertise_port to force opensips in
> using the public IPs of the NAT:
>    http://www.opensips.org/Resources/DocsCoreFcn#toc24
>
> Regards,
> Bogdan
>
> Daniel Goepp wrote:
>> I am trying to setup OpenSIPs to run behind a firewall, and not
>> finding much information regarding how to get OpenSIPs to be aware of
>> the public IP for it's signaling.  The firewall is setup with a 1 to 1
>> NAT for the public and private IPs, and right now all udp and tcp
>> traffic is being passed directly through.  Has anyone successfully
>> gotten OpenSIPs setup like this?  If so, can you please provide any
>> information on how it was setup.
>>
>> TIA
>>
>> -dg
>>
>> ___
>> Users mailing list
>> Users@lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] OpenSIPs behind a firewall

[Bogdan-Andrei Iancu]

Hi Daniel,

try using the advertise_address and advertise_port to force opensips in 
using the public IPs of the NAT:
http://www.opensips.org/Resources/DocsCoreFcn#toc24

Regards,
Bogdan

Daniel Goepp wrote:
> I am trying to setup OpenSIPs to run behind a firewall, and not
> finding much information regarding how to get OpenSIPs to be aware of
> the public IP for it's signaling.  The firewall is setup with a 1 to 1
> NAT for the public and private IPs, and right now all udp and tcp
> traffic is being passed directly through.  Has anyone successfully
> gotten OpenSIPs setup like this?  If so, can you please provide any
> information on how it was setup.
>
> TIA
>
> -dg
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>   


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] OpenSIPs behind a firewall

[Daniel Goepp]

I am trying to setup OpenSIPs to run behind a firewall, and not
finding much information regarding how to get OpenSIPs to be aware of
the public IP for it's signaling.  The firewall is setup with a 1 to 1
NAT for the public and private IPs, and right now all udp and tcp
traffic is being passed directly through.  Has anyone successfully
gotten OpenSIPs setup like this?  If so, can you please provide any
information on how it was setup.

TIA

-dg

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] SIP trace and OpenSIPS-CP 2.0

[Bogdan-Andrei Iancu]

Hi Marc,

loading the siptrace module is not enough. You need to use the 
sip_trace() function and set the trace_flag (for transaction tracing). See:
http://www.opensips.org/html/docs/modules/1.5.x/siptrace.html#id228291

Best regards,
Bogdan

marcher wrote:
> Hi,
>
> Trying to get sip trace functionality on opensips-cp working also. 
>
> Toggling the trace on and off from the web interface appears to be working
> fine.
>
> Oct  7 13:08:59 [2332] DBG:mi_xmlrpc:default_method: starting up.
> Oct  7 13:08:59 [2332] DBG:mi_xmlrpc:default_method: done looking the mi
> command.
> Oct  7 13:08:59 [2332] DBG:mi_xmlrpc:default_method: done parsing the mi
> tree.
> Oct  7 13:08:59 [2332] DBG:mi_xmlrpc:default_method: done running the mi
> command.
> Oct  7 13:08:59 [2332] DBG:mi_xmlrpc:default_method: done building response.
>
> However, nothing gets written to the mysql db siptrace table. 
>
> Hence, nothing gets written to the siptrace table on opensip-cp.
>
> I'm testing it with SJPhone registering to opensips from the same local
> machine.
>
> I added the following parameters to opensips.cfg
>
> loadmodule "siptrace.so"
>
> #-- siptrace db url 
> modparam("siptrace", "db_url","mysql://root:###...@localhost/opensips")
>
> Is this the correct format for the siptrace db_url? 
>
> The only thing I see in the log that looks related is:
>
> Oct  7 13:02:53 [2324] DBG:siptrace:trace_sl_onreply_out: trace off...
>
> For the drouting module, I have the db_url configured as 
>
> modparam("drouting",
> "db_url","mysql://opensips:opensip...@localhost/opensips")
>
> I did try changing the siptrace db_url to this format, but it didn't work
> either.
>
> Any help greatly appreciated.
>
> Cheers,
>
> Marc
>
>
> Iulia Bublea-2 wrote:
>   
>> Load the siptrace module in the opensips.cfg and set the db parameter.
>>
>> Iulia
>>
>> Gavin Henry wrote:
>> 
>>> Quick one,
>>>
>>> I presume you need the sip_trace function in the right place and that
>>> you just toggle it on/off via the cp?
>>>
>>> Also, you will need the db_url if logging to mysql?
>>>
>>> Thanks.
>>>
>>>   
>>>   
>> ___
>> Users mailing list
>> Users@lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
>> 
>
>   


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] SIP trace and OpenSIPS-CP 2.0

[marcher]

Hi,

Trying to get sip trace functionality on opensips-cp working also. 

Toggling the trace on and off from the web interface appears to be working
fine.

Oct  7 13:08:59 [2332] DBG:mi_xmlrpc:default_method: starting up.
Oct  7 13:08:59 [2332] DBG:mi_xmlrpc:default_method: done looking the mi
command.
Oct  7 13:08:59 [2332] DBG:mi_xmlrpc:default_method: done parsing the mi
tree.
Oct  7 13:08:59 [2332] DBG:mi_xmlrpc:default_method: done running the mi
command.
Oct  7 13:08:59 [2332] DBG:mi_xmlrpc:default_method: done building response.

However, nothing gets written to the mysql db siptrace table. 

Hence, nothing gets written to the siptrace table on opensip-cp.

I'm testing it with SJPhone registering to opensips from the same local
machine.

I added the following parameters to opensips.cfg

loadmodule "siptrace.so"

#-- siptrace db url 
modparam("siptrace", "db_url","mysql://root:###...@localhost/opensips")

Is this the correct format for the siptrace db_url? 

The only thing I see in the log that looks related is:

Oct  7 13:02:53 [2324] DBG:siptrace:trace_sl_onreply_out: trace off...

For the drouting module, I have the db_url configured as 

modparam("drouting",
"db_url","mysql://opensips:opensip...@localhost/opensips")

I did try changing the siptrace db_url to this format, but it didn't work
either.

Any help greatly appreciated.

Cheers,

Marc


Iulia Bublea-2 wrote:
> 
> Load the siptrace module in the opensips.cfg and set the db parameter.
> 
> Iulia
> 
> Gavin Henry wrote:
>> Quick one,
>>
>> I presume you need the sip_trace function in the right place and that
>> you just toggle it on/off via the cp?
>>
>> Also, you will need the db_url if logging to mysql?
>>
>> Thanks.
>>
>>   
> 
> 
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> 
> 

-- 
View this message in context: 
http://n2.nabble.com/SIP-trace-and-OpenSIPS-CP-2-0-tp3063389p3783252.html
Sent from the OpenSIPS - Users mailing list archive at Nabble.com.

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] CAll controller Issue

[Dan Pascu]

On 7 Oct 2009, at 14:22, ASHWINI NAIDU wrote:

> Hi all,
>
> I am using call controller-2.0.3 .
>
> Problem 1: If i place the call_control( )  function after setting  
> diverter_avp the call controller takes all the accounts as postpaid.  
> what is the reason for this behavior

The diverter_avp if set will indicate who is the billing party. Maybe  
that account is postpaid.

--
Dan




___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] newtran() limitations

[Bogdan-Andrei Iancu]

Hi Brett,

if you create sooner the transaction, you have bigger chances to catch a 
retransmission asap - detecting retransmission asap helps you because 
you avoid any processing (in script) for a retransmission.

Regards,
Bogdan

Brett Nemeroff wrote:
> Bogdan,
> This kind of explanation is really helpful. If you don't mind, I'd 
> like to ask a little more detail.
>
> Can you please explain when it would be necessary to force creation of 
> a transaction where t_relay wouldn't suffice?
>
> Thanks,
> Brett
>
>
> On Wed, Oct 7, 2009 at 9:50 AM, Bogdan-Andrei Iancu 
> mailto:bog...@voice-system.ro>> wrote:
>
> Hi Stan,
>
> Just to explain you want actually happens when you do t_newtran() :
>
> This function forces the creation of the transaction (which
> otherwise is
> automatically done by functions like t_relay() and t_reply() ).
> Part of
> creating the transaction is cloning of the current request into shared
> memory (cloned from pkg into shm). We need this copy in
> transaction (is
> shared mem) as the processing of this request may continue in a
> failure
> route (somewhere later, in other process).
>
> So, the warning is about this cloning/copy action - the request, as it
> is at that moment, will be copied into shm for later usage -
> whenever/whenever you do use later the transaction, you will see the
> message (and its changes) from the cloning time. Changes that are
> copies
> at cloning time are the lumps (changes on the textual level). Other
> things like flags, RURI are updated in transaction at t_relay() time.
>
> Hope this story will answer your questions :)
>
> Regards,
> Bogdan
>
> Stanisław Pitucha wrote:
> > Hi,
> >
> > I'd like to know what exactly does this note mean: (from the
> documentation)
> >
> > "NOTE that the changes on the request that are made after this
> > function call will not be saved into transaction!!!"
> >
> > What is the limitation in practice / what is saved into transaction.
> > In details - if I have an INVITE packet and call t_newtran() on it:
> > - will modification of the message body take effect on t_relay()?
> > (done both before and after newtran)
> > - will modification of $ru and $du have any effect after newtran()
> > - what other scenarios should I think about that might be affected?
> >
> >
>
>
> ___
> Users mailing list
> Users@lists.opensips.org 
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
> 
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>   


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] newtran() limitations

[Stanisław Pitucha]

2009/10/7 Brett Nemeroff :
> Can you please explain when it would be necessary to force creation of a
> transaction where t_relay wouldn't suffice?

It's really not that t_relay() doesn't suffice, but rather that
t_relay() is at the end of the script and if one process starts
working on the message and another one gets the retransmission of that
message, you process the message twice with possibly strange effects.
(for example you place 2 calls out to the gateway, even though the
phone requested only one).

The limitation I was interested in and that Bogdan verified later on
the channel is that any change to the text of the message that is done
*after* newtran(), will not be present in the failure route, or new
branches.

-- 
KTHXBYE,

Stanisław Pitucha, Gradwell Voip Engineer

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] problem starting XCAP server on redhat linux

[Iñaki Baz Castillo]

2009/10/7 Susheela :
>  2. Is it mandatory to have Mysql installed to start xcap server.

Please read the full documentation as it clearly says that MySQL is required.


-- 
Iñaki Baz Castillo


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] newtran() limitations

[Brett Nemeroff]

Bogdan,This kind of explanation is really helpful. If you don't mind, I'd
like to ask a little more detail.

Can you please explain when it would be necessary to force creation of a
transaction where t_relay wouldn't suffice?

Thanks,
Brett


On Wed, Oct 7, 2009 at 9:50 AM, Bogdan-Andrei Iancu
wrote:

> Hi Stan,
>
> Just to explain you want actually happens when you do t_newtran() :
>
> This function forces the creation of the transaction (which otherwise is
> automatically done by functions like t_relay() and t_reply() ). Part of
> creating the transaction is cloning of the current request into shared
> memory (cloned from pkg into shm). We need this copy in transaction (is
> shared mem) as the processing of this request may continue in a failure
> route (somewhere later, in other process).
>
> So, the warning is about this cloning/copy action - the request, as it
> is at that moment, will be copied into shm for later usage -
> whenever/whenever you do use later the transaction, you will see the
> message (and its changes) from the cloning time. Changes that are copies
> at cloning time are the lumps (changes on the textual level). Other
> things like flags, RURI are updated in transaction at t_relay() time.
>
> Hope this story will answer your questions :)
>
> Regards,
> Bogdan
>
> Stanisław Pitucha wrote:
> > Hi,
> >
> > I'd like to know what exactly does this note mean: (from the
> documentation)
> >
> > "NOTE that the changes on the request that are made after this
> > function call will not be saved into transaction!!!"
> >
> > What is the limitation in practice / what is saved into transaction.
> > In details - if I have an INVITE packet and call t_newtran() on it:
> > - will modification of the message body take effect on t_relay()?
> > (done both before and after newtran)
> > - will modification of $ru and $du have any effect after newtran()
> > - what other scenarios should I think about that might be affected?
> >
> >
>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] newtran() limitations

[Bogdan-Andrei Iancu]

Hi Stan,

Just to explain you want actually happens when you do t_newtran() :

This function forces the creation of the transaction (which otherwise is 
automatically done by functions like t_relay() and t_reply() ). Part of 
creating the transaction is cloning of the current request into shared 
memory (cloned from pkg into shm). We need this copy in transaction (is 
shared mem) as the processing of this request may continue in a failure 
route (somewhere later, in other process).

So, the warning is about this cloning/copy action - the request, as it 
is at that moment, will be copied into shm for later usage - 
whenever/whenever you do use later the transaction, you will see the 
message (and its changes) from the cloning time. Changes that are copies 
at cloning time are the lumps (changes on the textual level). Other 
things like flags, RURI are updated in transaction at t_relay() time.

Hope this story will answer your questions :)

Regards,
Bogdan

Stanisław Pitucha wrote:
> Hi,
>
> I'd like to know what exactly does this note mean: (from the documentation)
>
> "NOTE that the changes on the request that are made after this
> function call will not be saved into transaction!!!"
>
> What is the limitation in practice / what is saved into transaction.
> In details - if I have an INVITE packet and call t_newtran() on it:
> - will modification of the message body take effect on t_relay()?
> (done both before and after newtran)
> - will modification of $ru and $du have any effect after newtran()
> - what other scenarios should I think about that might be affected?
>
>   


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] newtran() limitations

[Stanisław Pitucha]

Hi,

I'd like to know what exactly does this note mean: (from the documentation)

"NOTE that the changes on the request that are made after this
function call will not be saved into transaction!!!"

What is the limitation in practice / what is saved into transaction.
In details - if I have an INVITE packet and call t_newtran() on it:
- will modification of the message body take effect on t_relay()?
(done both before and after newtran)
- will modification of $ru and $du have any effect after newtran()
- what other scenarios should I think about that might be affected?

-- 
KTHXBYE,

Stanisław Pitucha, Gradwell Voip Engineer

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] problem starting XCAP server on redhat linux

[Sanjeev BA]

Try executing with the --no-fork option. It may give you some clue.

Regards
Sanjeev

-Original Message-
From: users-boun...@lists.opensips.org 
[mailto:users-boun...@lists.opensips.org] On Behalf Of Peter Lemenkov
Sent: Wednesday, October 07, 2009 8:58 PM
To: OpenSIPS users mailling list
Subject: Re: [OpenSIPS-Users] problem starting XCAP server on redhat linux

2009/10/7 Susheela :
>
> Hi,
> ? I am new to openxcap, have installed Version 1.1.2 on redhat linux box,
> but having problem while starting the server.
> ?looks like it is failing at "process.daemonize(pidFile)"

There are various possible reasons (perhaps, you'll need superuser's
privileges for creating pid-file - just my guess), so I cannot say
something valuable here.

However, I advice you to grab srpm-file from there and test it.

https://bugzilla.redhat.com/show_bug.cgi?id=525432

-- 
With best regards, Peter Lemenkov.

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] problem starting XCAP server on redhat linux

[Peter Lemenkov]

2009/10/7 Susheela :
>
> Hi,
>   I am new to openxcap, have installed Version 1.1.2 on redhat linux box,
> but having problem while starting the server.
>  looks like it is failing at "process.daemonize(pidFile)"

There are various possible reasons (perhaps, you'll need superuser's
privileges for creating pid-file - just my guess), so I cannot say
something valuable here.

However, I advice you to grab srpm-file from there and test it.

https://bugzilla.redhat.com/show_bug.cgi?id=525432

-- 
With best regards, Peter Lemenkov.

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] problem starting XCAP server on redhat linux

[Susheela]

Hi,
   I am new to openxcap, have installed Version 1.1.2 on redhat linux box, 
but having problem while starting the server.
 looks like it is failing at "process.daemonize(pidFile)"

 1.first of all is this supported on redhat linux?
 2. Is it mandatory to have Mysql installed to start xcap server.

 thanks in advance for any help
 Susheela.
-- 
View this message in context: 
http://n2.nabble.com/problem-starting-XCAP-server-on-redhat-linux-tp3781322p3781322.html
Sent from the OpenSIPS - Users mailing list archive at Nabble.com.

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] CAll controller Issue

[ASHWINI NAIDU]

Hi all,

I am using call controller-2.0.3 .

Problem 1: If i place the *call_control( )*  function after setting
diverter_avp the call controller *takes all the accounts as postpaid*. what
is the reason for this behavior
Problem 2: Same kind of code behave differently on 2 different opensips
servers i.e the behavior of call-controller.

*Below i have given extract of the code*.*All accounts are taken are
postpaid*

if ((method=="INVITE" && !has_totag())) {
if ( is_avp_set("$avp(s:from_alias)")) {
uac_replace_from("$fU","$avp(s:from_alias)");
$avp(s:billing_party)=$avp(s:from_alias);

$avp(i:805)=$(avp(s:from_alias){uri.user})+"@"+$(avp(s:from_alias){uri.domain});
 }

setflag(1);
setflag(3);
setflag(20);
route(20); *//call-controller route*
};



route[20] {

#--
# Call control function at the first INVITE
$var(retcode) = call_control();
xlog("L_INFO","\n 1. * RETURN
CODE=$var(retcode)");
xlog("L_INFO","\n 2. * RETURN
CODE=$var(retcode)");
xlog("L_INFO","\n 3. * RETURN
CODE=$var(retcode)");
xlog("L_INFO","\n The call is From: $fu
*To:$tu Contact:
$ct*UA=[$ua]\n");

switch ($var(retcode)){

case -1:
   # Not enough credit (prepaid call)
   xlog("L_INFO", "Call control: not enough credit for
prepaid call\n");
   acc_aaa_request("402");
   sl_send_reply("402", "Not enough credit");
   exit;
   break;
case -2:
   # Locked by call in progress (prepaid call)
   xlog("L_INFO", "Call control: prepaid call locked by
another call in progress\n");
   acc_aaa_request("403");
   sl_send_reply("403", "Call locked by another call in
progress");
   exit;
   break;

case 1:
   # Call with a limit under callcontrol management
(either prepaid or postpaid)
xlog("L_INFO", "Call control: Inside 1 for pre
paid\n");
break;

case 2:
xlog("L_INFO", "Call control: Inside 2 for post
paid\n");
   # Call with no limit
break;

   default:
   # Internal error (message parsing, communication,
...)
   xlog("L_INFO", "Call control: internal server
error\n");
   acc_aaa_request("500");
   sl_send_reply("500", "Internal server error");
   exit;
  }

}


-- 
Thanking You,
Ashwini BR Naidu
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] OpenXCAP-OpenSIPS

[Iñaki Baz Castillo]

2009/10/7 Adrian Georgescu :
> The only advantage that remains is the configurable access list for
> who mis allows to connect over xml_rpc. This ACL is not available in
> OpenSIPS module.

ok, so basically with iptables the same feature can be achieved.

Thanks a lot.

-- 
Iñaki Baz Castillo


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] OpenXCAP-OpenSIPS

[Adrian Georgescu]

The only advantage that remains is the configurable access list for  
who mis allows to connect over xml_rpc. This ACL is not available in  
OpenSIPS module.

--
Adrian





On Oct 7, 2009, at 11:00 AM, Iñaki Baz Castillo wrote:

> 2009/10/7 Adrian Georgescu :
>> The problem you mentioned has been fixed in OpenSIPS xml_rpc  
>> module. I have
>> just updated the wiki page to reflect this.
>
> Does it mean that opensips-mi-proxy is not needed now?
> Or does it provides some advantage?
>
> Thanks.
>
>
> -- 
> Iñaki Baz Castillo
> 
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] OpenXCAP-OpenSIPS

[Iñaki Baz Castillo]

2009/10/7 Adrian Georgescu :
> The problem you mentioned has been fixed in OpenSIPS xml_rpc module. I have
> just updated the wiki page to reflect this.

Does it mean that opensips-mi-proxy is not needed now?
Or does it provides some advantage?

Thanks.


-- 
Iñaki Baz Castillo


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] OpenXCAP-OpenSIPS

[Adrian Georgescu]

The problem you mentioned has been fixed in OpenSIPS xml_rpc module. I  
have just updated the wiki page to reflect this.


--
Adrian





On Oct 7, 2009, at 9:33 AM, Sanjeev BA wrote:


Hi,

I am trying to get OpenSIPS working with OpenXCAP. Has anyone in the  
group, tried this before?


OpenXCAP best practices mentions the following.
The rpc management interface exposed by OpenSER needs to be  
protected by iptables or other methods otherwise is reachable from  
the network. The mi_xmlrpc seem to freeze with no reason after  
awhile, a restart of the proxy is necessary, next version will use  
the datagram interface which seem to be more stable. Avoid using  
built-in rpc management interface above and use opensips-mi-proxy  
package, it provides both access list and stable control interface


Does this still hold true? Is there an associated email thread which  
discusses how to setup OpenXCAP with OpenSIPS?


Please advice.

Regards
Sanjeev


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Prepay charge by source IP

[Adrian Georgescu]

Most of the software you mentioned had been designed to run with SIP  
URI in the form of u...@domain.


The short answer is that it will not work with only IP addresses  
without a major re-engineering.


--
Adrian





On Oct 7, 2009, at 4:59 AM, Adam Botbyl wrote:

I am trying to setup a opensips/cdrtool/callcontrol gateway for pre- 
pay ratings. My conundrum is that I need to debit account by IP  
alone (not username). I found that I can auth by IP by just  
inserting it into the database, but cannot seem to wild-card the  
username. Is there a way to do this without re-writing the source?


Basically all calls from 1.2.3.4 will rate as the account for  
1.2.3.4 instead of having to have 1...@1.2.3.4 1...@1.2.3.4 etc, etc.


Documentation and googling seems sparse on this.

Regards,
 --Adam
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] OpenXCAP-OpenSIPS

[Sanjeev BA]

Hi,

 

I am trying to get OpenSIPS working with OpenXCAP. Has anyone in the group,
tried this before?

 

OpenXCAP best practices mentions the following.

The rpc management interface exposed by OpenSER needs to be protected by
iptables or other methods otherwise is reachable from the network. The
mi_xmlrpc seem to freeze with no reason after awhile, a restart of the proxy
is necessary, next version will use the datagram interface which seem to be
more stable. Avoid using built-in rpc management interface above and use
 opensips-mi-proxy package, it
provides both access list and stable control interface

 

Does this still hold true? Is there an associated email thread which
discusses how to setup OpenXCAP with OpenSIPS?

 

Please advice.

 

Regards

Sanjeev

 

 

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Login to OpenSIPS website

[Bogdan-Andrei Iancu]

Hi Sanjeev,

what is the account you created? I can check the state of your pending 
account.

Regards,
Bogdan

Sanjeev BA wrote:
>
> Hi,
>
> I have been trying to login to OpenSIPS website using the Login option.
>
>  
>
> However, everytime I click on the confirmation email link, I see a 
> webpage with error messages.
>
>  
>
> From existing email account.
>
> Error: Your email link is not synchronized with the state of the 
> password file. Please reissue your change-password request.
>
> (or)
>
> From Gmail
>
> Please use the link provided in the email to access this page.
>
>  
>
>  
>
> Has anyone faced this issue before?
>
>  
>
> Please advice.
>
>  
>
> Regards,
>
> Sanjeev
>
> 
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>   


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Prepay charge by source IP

[Bogdan-Andrei Iancu]

Hello Adam,

There are 2 ways to get this working:
- use opensips 1.6, where via the callcontrol module you can send 
custom data (including the source IP)
- in 1.5, you can try to mask the src IP in some of the fields that 
are already sent out - maybe RURI ...

Regards,
Bogdan

Adam Botbyl wrote:
>
> I am trying to setup a opensips/cdrtool/callcontrol gateway for 
> pre-pay ratings. My conundrum is that I need to debit account by IP 
> alone (not username). I found that I can auth by IP by just inserting 
> it into the database, but cannot seem to wild-card the username. Is 
> there a way to do this without re-writing the source?
>
>  
>
> Basically all calls from 1.2.3.4 will rate as the account for 1.2.3.4 
> instead of having to have 1...@1.2.3.4  
> 1...@1.2.3.4  etc, etc.
>
>  
>
> Documentation and googling seems sparse on this.
>
>  
>
> Regards,
>
>  --Adam
>
> 
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>   


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users