Re: [SR-Users] [sr-dev] dialog module with DB Backend

[Daniel-Constantin Mierla]

Hello,

I pushed some patches to the master branch in order to remove the dialog 
from its associated profiles when it gets in terminated state. I 
encountered such issue (not that) recently, but I haven't gotten the 
time to get to it before.


Then, the second patch is to not add dialogs in profiles when loading 
from database and the state is terminated (5).


Here are the links to the patches:

- 
http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=edf61acb57ed5e8ee0ca9ec1f796e43ce993be48
- 
http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=9b88eb7ee2d243882383a44f601baa21fd679cd5


Should be straightforward to cherry pick to 4.1 (even 4.0 I expect). If 
you test and all goes fine, I will backport -- here I had no time for 
real testing.


I plan also to not add the dialogs in memory for state terminated, but 
destroy them at db load time. But this needs a bit of a review, to be 
sure that all necessary callbacks are executed.


On the other hand, if the dialogs are not removed from db, might be an 
issue with the database driver (cassandra in this case, which is rather 
new module). Do you get any syslog errors from kamailio or database 
server? I expect that people would have reported such issue for other 
database engines so far. Still it might be an issue, just that was not 
noticed...


Cheers,
Daniel

On 24/02/14 11:19, jay binks wrote:

So poking round the code for the dialog module
Im not sure what im missing here.


get_profile_size dosnt care bout the state of a dialog... so you get 
ALL dialogs that are in the hash table.
( which is interesting if you want to use dialog module to enforce 
channel limits etc )


So you go... OK...  kamailio only expects to have "ACTIVE" dialogs in 
the hash table... kewl..

lets assume that to be the case.

but then in dlg_db_handler.c , load_dialog_info_from_db loads all 
dialogs from the DB, regardless of state.
so all dialogs in the DB ( ones that didnt get deleted yet... but were 
in state 5 ) get re-created in kamailio

upon startup.

what this means is...
( assume starting with empty DB )

I start kamailio, make some calls... they get synced to the DB.
I end the calls,  kamailio removes from dialogs module internal hash, 
but the sync to DB hasnt happened yet.


I kill kamailio ( or crash .. whatever )  restart kamailio and it 
re-loads all those dialogs

and thinks they are still active calls.

Im SURE Im missing something here, because it seems to be VERY common 
to use dialogs for channel limiting..
maybe not so much using cassandra db behind the scenes, but as of yet 
... Im still yet to find anything that makes me thing this is 
db_cassandra mis-behaving.


if im wrong, please point me in the right direction.

Jay




On 24 February 2014 17:54, jay binks > wrote:


Am I REALLY the only person who has ever run into this !?


On 19 February 2014 14:08, jay binks mailto:jaybi...@gmail.com>> wrote:

Hi all, im using the dialog module with db_cassandra backend..
I dont believe this issue is related to cassandra, but its
worth mentioning anyways.

so... I run kamailio, make calls, see dialogs in the DB..
and I Can use "kamctl mi dlg_list" and see that dialogs go
away when I hangup a call..

When I query the DB Backend, I still see the queries, but they
have a state of 5.
I Initially thought this was a bug, but it seems dialogs in
state 5 get cleaned up after a period.
so I moved on.

now , lets restart kamailio..
kamailio loads all dialogs on startup, after kamailio starts I
call "kamctl mi dlg_list" again, and it shows all my dialogs
from the DB.   they DO show as "State 5"
but for some reason, these dialogs appear to stick around for
a long time, and the bigger issue it causes me is that my
channel limiting ( using get_profile_size ) seems to consider
these dialogs ( in state 5 ) as being active calls.

Please someone point me in the right direction... :)

what am I doing wrong ?
( or is this a bug somewhere )

Sincerely

Jay




-- 
Sincerely


Jay




--
Sincerely

Jay


___
sr-dev mailing list
sr-...@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev


--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] kamailio with mediaproxy-ng, 488 Not Acceptable Here

[Richard Fuchs]

On 02/22/14 07:07, Mihai Marin wrote:
> Hello Sirs, Sir Richard,
> Thank you for your detailed explication.
> I'm still thinking on that but I would say to act as the caller and keep
> caller decision. If caller makes an offer with rtcp-mux ,
> include separate ICE candidates for RTCP for media proxy too and forward
> as it is to alice. If callee accept it (or not) you will receive the OK
> with alice sdp, modify it (depending on her choices) and forward to bob.
> In this way, we cover all the cases. Eventually we can add another
> parameter to always ignore rtcp-mux offers.

Alright, can you please update your 3.0 branch from git and try with
this. The rtcp-mux default now is to go along with the client's choice,
which I believe should fix your use case.

On the other hand, it may break the usual WebRTC<>non-WebRTC bridging
case, depending on how picky the WebRTC client is. To accommodate for
this, there's a set of new flags within the control protocol to do
things like accepting rtcp-mux when the other client doesn't accept it,
removing an rtcp-mux offer from SDP, offering it when it wasn't offered,
offering it but rejecting it on the other side, and all kinds of other
scenarios (which may or may not collide with how ICE candidates are
handled). I'll see if I can get those implemented into the rtpproxy-ng
module soon for those who may need them.

cheers



signature.asc
Description: OpenPGP digital signature
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Kamailio as redirect

[Daniel Tryba]

On Monday 24 February 2014 14:45:18 Mike Claudi Pedersen wrote:
> okay i somewhat get that.. but cant i use something like a lookup in a
> textfile instead of a db?

You can. alias_db also accepts dbtext as backend:
http://kamailio.org/docs/modules/stable/modules/db_text.html

But TIMTOWTDI, alias_db was just a suggestion.

Please keep the mailing list included.

-- 

POCOS B.V. - Croy 9c - 5653 LC Eindhoven
Telefoon: 040 293 8661 - Fax: 040 293 8658
http://www.pocos.nl/   - http://www.sipo.nl/
K.v.K. Eindhoven 17097024

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] kamailio with mediaproxy-ng, 488 Not Acceptable Here

[Carlos Ruiz Díaz]

Just in case someone is interested, I created a sample script that could
help new comers having the same problem.

I will write a blog entry explaining how this works, but in a nutshell:

- this script is configured to run behind NAT, port TCP 10080 and TCP/UDP
5090 are exposed to the Internet
- you have to create valid users using, preferably, "kamctl add ..."
- RTP ports should be open in range 30k-35k, inclusive
- I used jssip as WEBRTC SIP UA: http://tryit.jssip.net/
- Always disable video before placing a call from jssip UA
- I tested calls between:
- jssip to csipsimple
- csipsimple to jssip
- csipsimple to csipsimple


Link to the scripts: https://github.com/caruizdiaz/kamailio-ws

Regards,

On Sat, Feb 22, 2014 at 9:31 AM, Richard Fuchs  wrote:

> On 02/22/14 07:07, Mihai Marin wrote:
> > Hello Sirs, Sir Richard,
> > Thank you for your detailed explication.
> > I'm still thinking on that but I would say to act as the caller and keep
> > caller decision. If caller makes an offer with rtcp-mux ,
> > include separate ICE candidates for RTCP for media proxy too and forward
> > as it is to alice. If callee accept it (or not) you will receive the OK
> > with alice sdp, modify it (depending on her choices) and forward to bob.
> > In this way, we cover all the cases. Eventually we can add another
> > parameter to always ignore rtcp-mux offers.
> >
> > What are the disadvantages on doing that? Is there any possibility that
> > some SIP clients not to respond properly to an SDP with rtcp-mux and
> > that's why you are removing it - or for '+' case where delay will be
> added?
>
> Compatibility is exactly the reason. I don't have any exact numbers, but
> I'm sure that there's a large number of SIP/RTP clients out there (I'd
> say the vast majority) which don't support rtcp-mux at all. Some of them
> might start misbehaving if they receive an rtcp-mux offer (even though
> as per RFC, they shouldn't, but experience shows that RFC compliance is
> often just wishful thinking). Since from our point of view (always
> either '+' or '-') there's no disadvantage in always demuxing RTCP, this
> was what was implemented.
>
> In any case, I'll see if I can get a solution implemented in the near
> future.
>
> cheers
>
>
> ___
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users@lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
>


-- 
Carlos
http://caruizdiaz.com
http://ngvoice.com
+595981146623
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Configuring Kamailio as an upstream proxy for FreeSwitch and which RTP proxy to choose

[Fred Posner]

On Mon Feb 24 10:50:07 CET 2014 Sean Kemball wrote:

> New to Kamailio and FreeSwitch, loosely familiar with SIP mechanics,
> and not a complete network idiot... but please be gentle. :)

Welcome!s,

> Questions:
>
> 1.Should the proposed topology, with Kamailio + an RTP proxy
> behind a firewall, relaying to FS on an inside interface, work?
> (Can't see why not)

Yes, you said that your upstream is on the same private network. So it 
should be pretty straight forward.


> 2.Does it need a local RTP proxy on the Kamailio box, particularly
> if we turn off the ASA SIP inspect stuff?

If you are all on the same private network, I would let FreeSWITCH 
handle the RTP, but you can do this a variety of ways.


> 3.Can you recommend which RTP proxy to use? There seem to be at
> least 3 that work with Kamailio. The box is CentOS 6.5, and it would 
> be nice to use known-to-work packages rather than compile from source.

> (But eh, if I haveta).

On your scenario, I'd just use FreeSWITCH for the media proxy. Again, 
many different ways to go here.


> 4.Can anyone point me to some docs to explain what ports need to
> be open between the Kamailio box and my upstream proxy/media server?
> I can be more liberal between inside and DMZ I guess.

Your upstream provider would generally tell you which rtp ports they 
would want opened.


> 5.Is static NAT in this environment going to bite me, or should
> it be OK?

I've never had an upstream provider communicate with me on private nat.

> 6.Is there any better documentation that we should be using to
> make this easier, or should I just man up and try harder?

Man up. =)
Practive makes perfect.

--
Fred Posner
The Palner Group, Inc.


___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] RTPProxy/Mediaproxy issue

[Ravi]

Dear Daniel,
Thank you again,

Ya i am investigating on this issue, by the way can you give any comments on
my questions in the previous mail?  I just wanna clarify those things to
rectify this packet loss issue. i googled about those questions but still
ended with the same confusion status and didnt got any prompt information.
And here below is the attachment, that shows RTP packet loss(using
wireshark) in my set-up. Can you please suggest me how can i troubleshoot
this RTP packet loss issue ?

And in that Attachment the IP addresses are like this:
192.168.2.235 and 192.168.2.239 are clients and 192.168.2.52  on which
RTPproxy and Kamailio are running.

Awaiting your reply.

regards,
Ravi
RTP_Packet_loss.png
  




--
View this message in context: 
http://sip-router.1086192.n5.nabble.com/RTPProxy-Mediaproxy-issue-tp125121p125313.html
Sent from the Users mailing list archive at Nabble.com.

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] pcscf - removing registration entries from hash table

[Daniel Ciprus]

Hello,

Our current setup is Kamailio as IMS core and we're observing following 
behavior:

Clients register themselves over TCP so pcscf creates hash table which keeps 
these information in memory. Once tcp reset occurs for any reason, registration 
entry stays in the memory and client re-registers himself with new pair 
ip:port. This kind of behavior creates problem because outbound SIP messages 
are being forked and requests are sent to non-existent tcp sessions which 
creates a lot of timeouts and confusion for AS.
We're using ims_usrloc_pcscf module to keep reg entries in and as I noticed, 
with usrloc module, there was an option which automatically removed entry from 
hash table once tcp session was closed which is not the case in this module.

Any suggestions how to get out of this ?

thanks for any hints/suggestions.


--
Daniel Ciprus
Integration engineer
http://www.acision.com

9954 Mayland Dr
Suite 3100
Richmond, VA 23233
USA
T: +1 804 762 5601
E: daniel.cip...@acision.com


This e-mail and any attachment is for authorised use by the intended 
recipient(s) only. It may contain proprietary material, confidential 
information and/or be subject to legal privilege. It should not be copied, 
disclosed to, retained or used by, any other party. If you are not an intended 
recipient then please promptly delete this e-mail and any attachment and all 
copies and inform the sender. Thank you for understanding.

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Kamailio as redirect

[Daniel Tryba]

On Monday 24 February 2014 14:00:01 Mike Claudi Pedersen wrote:
> i want to setup a test environment to see how kamailio handles redirection.
> i want to be able to reroute calls between servers, where do i insert the
> configuration for this?

A redirect is acomplished by manipulating $ru (or its parts $rU/$rd/...) and 
instead of relaying the request (t_relay()) sending a 302 Redirect 
(send_reply("302", "Redirect")). This has to be handled from the 
request_route.

> can i append a list of user and destination to make the configuration go
> through, to see where the call is going?

You could use the alias_db module 
http://www.kamailio.org/docs/modules/4.1.x/modules/alias_db.html

request_route {
#do stuff

   if(alias_db_lookup("dbaliases"))
   {
  send_reply("302", "Redirect");
   }
   else
   {
  send_reply("404", "Unknow destination");
   }

   exit;
}

-- 

POCOS B.V. - Croy 9c - 5653 LC Eindhoven
Telefoon: 040 293 8661 - Fax: 040 293 8658
http://www.pocos.nl/   - http://www.sipo.nl/
K.v.K. Eindhoven 17097024

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] Kamailio as redirect

[Mike Claudi Pedersen]

i want to setup a test environment to see how kamailio handles redirection.
i want to be able to reroute calls between servers, where do i insert the
configuration for this?
can i append a list of user and destination to make the configuration go
through, to see where the call is going?

im new at kamailio, and im having a really hard time finding the right
documentation to support a redirect server.

could somone please give me an example?

lets say i have 3 user
1000
1001
1002

and they are at 3 different servers
eg.
1000@192.168.1.10
1001@192.168.1.11
1002@192.168.1.12

then i call user 1002 from user 1000, through the kamailio redirect server,
which redirects to corresponding servers.


Mike Claudi Pedersen
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] [sr-dev] dialog module with DB Backend

[Carlos Ruiz Díaz]

I would suggest that you change the DBMS to something a little less
complicated than Cassandra, MySQL for example, make your tests again and
see if you can reproduce this.

In case you can't, and you get to work everything with the DBMS you chose,
it would mean that you have found a bug in the cassandra module.

I personally have been experimenting with db_cassandra, and it works quite
well for some scenarios, and it does not at all for others. Also, take into
account that you can't really maintain the Kamailio tables using the
built-in scripts (kamctl) when using Cassandra as a backend. It does not
work because Cassandra uses CQL that resembles SQL, but has a very limited
functionality and they look alike only syntactically.

Regards,



On Mon, Feb 24, 2014 at 7:19 AM, jay binks  wrote:

> So poking round the code for the dialog module
> Im not sure what im missing here.
>
>
> get_profile_size dosnt care bout the state of a dialog... so you get ALL
> dialogs that are in the hash table.
> ( which is interesting if you want to use dialog module to enforce channel
> limits etc )
>
> So you go... OK...  kamailio only expects to have "ACTIVE" dialogs in the
> hash table... kewl..
> lets assume that to be the case.
>
> but then in dlg_db_handler.c , load_dialog_info_from_db loads all dialogs
> from the DB, regardless of state.
> so all dialogs in the DB ( ones that didnt get deleted yet... but were in
> state 5 ) get re-created in kamailio
> upon startup.
>
> what this means is...
> ( assume starting with empty DB )
>
> I start kamailio, make some calls... they get synced to the DB.
> I end the calls,  kamailio removes from dialogs module internal hash, but
> the sync to DB hasnt happened yet.
>
> I kill kamailio ( or crash .. whatever )  restart kamailio and it
> re-loads all those dialogs
> and thinks they are still active calls.
>
> Im SURE Im missing something here, because it seems to be VERY common to
> use dialogs for channel limiting..
> maybe not so much using cassandra db behind the scenes, but as of yet ...
> Im still yet to find anything that makes me thing this is db_cassandra
> mis-behaving.
>
> if im wrong, please point me in the right direction.
>
> Jay
>
>
>
>
> On 24 February 2014 17:54, jay binks  wrote:
>
>> Am I REALLY the only person who has ever run into this !?
>>
>>
>> On 19 February 2014 14:08, jay binks  wrote:
>>
>>> Hi all, im using the dialog module with db_cassandra backend..
>>> I dont believe this issue is related to cassandra, but its worth
>>> mentioning anyways.
>>>
>>> so... I run kamailio, make calls, see dialogs in the DB..
>>> and I Can use "kamctl mi dlg_list" and see that dialogs go away when I
>>> hangup a call..
>>>
>>> When I query the DB Backend, I still see the queries, but they have a
>>> state of 5.
>>> I Initially thought this was a bug, but it seems dialogs in state 5 get
>>> cleaned up after a period.
>>> so I moved on.
>>>
>>> now , lets restart kamailio..
>>> kamailio loads all dialogs on startup, after kamailio starts I call
>>> "kamctl mi dlg_list" again, and it shows all my dialogs from the DB.   they
>>> DO show as "State 5"
>>> but for some reason, these dialogs appear to stick around for a long
>>> time, and the bigger issue it causes me is that my channel limiting (
>>> using get_profile_size ) seems to consider these dialogs ( in state 5 ) as
>>> being active calls.
>>>
>>> Please someone point me in the right direction... :)
>>>
>>> what am I doing wrong ?
>>> ( or is this a bug somewhere )
>>>
>>> Sincerely
>>>
>>> Jay
>>>
>>
>>
>>
>> --
>> Sincerely
>>
>> Jay
>>
>
>
>
> --
> Sincerely
>
> Jay
>
> ___
> sr-dev mailing list
> sr-...@lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
>
>


-- 
Carlos
http://caruizdiaz.com
+595981146623
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] dialog module with DB Backend

[jay binks]

So poking round the code for the dialog module
Im not sure what im missing here.


get_profile_size dosnt care bout the state of a dialog... so you get ALL
dialogs that are in the hash table.
( which is interesting if you want to use dialog module to enforce channel
limits etc )

So you go... OK...  kamailio only expects to have "ACTIVE" dialogs in the
hash table... kewl..
lets assume that to be the case.

but then in dlg_db_handler.c , load_dialog_info_from_db loads all dialogs
from the DB, regardless of state.
so all dialogs in the DB ( ones that didnt get deleted yet... but were in
state 5 ) get re-created in kamailio
upon startup.

what this means is...
( assume starting with empty DB )

I start kamailio, make some calls... they get synced to the DB.
I end the calls,  kamailio removes from dialogs module internal hash, but
the sync to DB hasnt happened yet.

I kill kamailio ( or crash .. whatever )  restart kamailio and it
re-loads all those dialogs
and thinks they are still active calls.

Im SURE Im missing something here, because it seems to be VERY common to
use dialogs for channel limiting..
maybe not so much using cassandra db behind the scenes, but as of yet ...
Im still yet to find anything that makes me thing this is db_cassandra
mis-behaving.

if im wrong, please point me in the right direction.

Jay




On 24 February 2014 17:54, jay binks  wrote:

> Am I REALLY the only person who has ever run into this !?
>
>
> On 19 February 2014 14:08, jay binks  wrote:
>
>> Hi all, im using the dialog module with db_cassandra backend..
>> I dont believe this issue is related to cassandra, but its worth
>> mentioning anyways.
>>
>> so... I run kamailio, make calls, see dialogs in the DB..
>> and I Can use "kamctl mi dlg_list" and see that dialogs go away when I
>> hangup a call..
>>
>> When I query the DB Backend, I still see the queries, but they have a
>> state of 5.
>> I Initially thought this was a bug, but it seems dialogs in state 5 get
>> cleaned up after a period.
>> so I moved on.
>>
>> now , lets restart kamailio..
>> kamailio loads all dialogs on startup, after kamailio starts I call
>> "kamctl mi dlg_list" again, and it shows all my dialogs from the DB.   they
>> DO show as "State 5"
>> but for some reason, these dialogs appear to stick around for a long
>> time, and the bigger issue it causes me is that my channel limiting (
>> using get_profile_size ) seems to consider these dialogs ( in state 5 ) as
>> being active calls.
>>
>> Please someone point me in the right direction... :)
>>
>> what am I doing wrong ?
>> ( or is this a bug somewhere )
>>
>> Sincerely
>>
>> Jay
>>
>
>
>
> --
> Sincerely
>
> Jay
>



-- 
Sincerely

Jay
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] Configuring Kamailio as an upstream proxy for FreeSwitch and which RTP proxy to choose

[Sean Kemball]

Hi

New to Kamailio and FreeSwitch, loosely familiar with SIP mechanics, and not a 
complete network idiot... but please be gentle. :)

We're trying to get Kamailio set up in front of a FreeSwitch-based SIP 
application server, to do some simple policy controls and, using one of the RTP 
proxy modules, to help handle the media side of things. Our SIP trunks come 
from our provider on a VLAN addressed as 10.x, and they provide an upstream 
proxy/media server (10.y address). The link also carries Internet traffic so 
we're running it through a Cisco ASA which breaks out the VLANs and static NATs 
the SIP stuff to our DMZ (10.z address). This is where we want to put the 
Kamailio box, where it should receive the calls and route them back through the 
ASA to the internal address (10.w range - all 10.w/x/y/z are separate, 
non-overlapping networks).

Outbound calls from the application server (there are very few) should pass 
back up to Kamailio which will validate the numbers against an approved list 
(the app should only dial a subset of numbers) and pass them to the upstream 
proxy if necessary. We need to ensure that inbound calls from outside trombone 
through our application server so that the caller doesn't get billed for any 
calls, but this should be the default I think as that side of things is handled 
by FS (the app stands up a new call and bridges it to the incoming). This 
topology should allow us to use Kamailio to hide details of the FS app from the 
outside world, and make life easier for the app developer who should just 
send/receive to the Kamailio box with no further thought or complexity.

If we put the FreeSwitch box in the DMZ where we want to put Kamailio, and then 
turn on SIP packet inspection in the ASA, calls flow but quality is poor for 
some callers. If we turn off SIP packet inspection, we get no audio - I can't 
find any clear Cisco documentation for this but I think the SIP inspection 
stuff in the ASA seems to handle RTP NAT fixups and the like too. But with no 
docs it may as well be magic, and I want to remove it if possible. With 
Kamailio in the DMZ and FS internal, we loosely followed 
http://kb.asipto.com/freeswitch:kamailio-3.3.x-freeswitch-1.2.x-sbc and hacked 
out the voicemail and Lua stuff, but couldn't get calls to flow, whether or not 
we used the SIP inspection on the ASA. We were confused why this example isn't 
define as WITH_NAT and doesn't use a local RTP proxy. Surely that would be 
needed?

Questions:

1.Should the proposed topology, with Kamailio + an RTP proxy behind a 
firewall, relaying to FS on an inside interface, work? (Can't see why not)

2.Does it need a local RTP proxy on the Kamailio box, particularly if we 
turn off the ASA SIP inspect stuff?

3.Can you recommend which RTP proxy to use? There seem to be at least 3 
that work with Kamailio. The box is CentOS 6.5, and it would be nice to use 
known-to-work packages rather than compile from source. (But eh, if I haveta).

4.Can anyone point me to some docs to explain what ports need to be open 
between the Kamailio box and my upstream proxy/media server? I can be more 
liberal between inside and DMZ I guess.

5.Is static NAT in this environment going to bite me, or should it be OK?

6.Is there any better documentation that we should be using to make this 
easier, or should I just man up and try harder?

TIA
Sean
Volunteer for our Red Puppy street appeal to help puppies
like Gordy become guide dogs.
#
This email, including any attachments, is intended solely for the addressee(s)
It is confidential and may be legally privileged.
If you are not the intended recipient, you must not copy, disclose, distribute
or otherwise use it or the information in it. Please notify the sender at once
and delete it from your system immediately.
Any views or opinions expressed are solely those of the author and do not
necessarily represent those of  Blind Foundation.
The Blind Foundation does not accept responsibility for any viruses or other
malicious code that may be transmitted with this email.
#


___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Change from_uri

[Alex Balashov]

True! As most industrial equipment out there prefers PAI > RPID > From. 

Daniel Tryba  wrote:
>On Saturday 22 February 2014 02:16:01 arun Jayaprakash wrote:
>> Alex, thank you for your pointers. I will work with Asterisk to see
>how I
>> can change the caller ID instead of messing with the UAC module.
>Thanks
>> again.
>
>You might want to check what happens when you fix the header:
>P-Preferred-Identity: "7004" 
>by simply deleting it and adding a correct one. 

--
Sent from my mobile, and thus lacking in the refinement one might expect from a 
fully fledged keyboard. 

Alex Balashov - Principal 
Evariste Systems LLC
235 E Ponce de Leon Ave
Suite 106
Decatur, GA 30030
United States
Tel: +1-678-954-0671
Web: http://www.evaristesys.com/, http://www.alexbalashov.com

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Change from_uri

[Daniel Tryba]

On Saturday 22 February 2014 02:16:01 arun Jayaprakash wrote:
> Alex, thank you for your pointers. I will work with Asterisk to see how I
> can change the caller ID instead of messing with the UAC module. Thanks
> again.

You might want to check what happens when you fix the header:
P-Preferred-Identity: "7004" 
by simply deleting it and adding a correct one. 


-- 

POCOS B.V. - Croy 9c - 5653 LC Eindhoven
Telefoon: 040 293 8661 - Fax: 040 293 8658
http://www.pocos.nl/   - http://www.sipo.nl/
K.v.K. Eindhoven 17097024

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users