sr-users June 2005

sr-users@lists.kamailio.org

241 participants
595 discussions

Re: [Serusers] Portal for forking call to preferred end device-sequential ringing

by Samuel Osorio Calvo

In fact, SER has a model for usrloc changes outside itself: FIFO interface. Using the ul command of this interface it is possible to add/update/remove users' information during runtime without having to restart SER. In fact, these commands update SER's cache and this information is immediately used by SER. It will be propagated to the permament DB storage depending on the mode selected. I would suggest to add a chapter of the FIFO/UNIX/TCP/XMLRPC interface to the famous Getting Started Document ;) Samuel. Unclassified. >>> "Greger V. Teigre" <greger(a)teigre.com> 06/21/05 04:53PM >>> You get into even worse problems as SER does not really have a model for usrloc changes outside itself. Thus, dependent on your db mode (memory-only, flush, write-through etc) SER will potentially overwrite your externally set q-value before stopping. If you use write-through, you probably don't get that problem, and yes, you could probably theoretically restart SER to reload the usrloc with new q-values (never validated that, though). However, with a lot of locations, it's not really feasible due to SER's start-up loading of locations (and being unavailable while doing so). Also, you will probably restart in the middle of a transaction and calls may fail (unless you use the restart safe parameter). g-) Aisling wrote: > Thank you for the replys. I will look up the post you suggested for > further info on the lcr module. One thing I just want to clarify: > > " DB-based changes is the way to go - Updating the usrloc table > outside > SER does not work as SER loads usrloc info into memory."...... > > Does this mean I must modify the database and then restart SER, > thereby > disrupting the service for other users? > > Thanks, > Aisling. > > -----Original Message----- > From: Greger V. Teigre [mailto:greger@teigre.com] > Sent: 21 June 2005 13:33 > To: Samuel Osorio Calvo; ashling.odriscoll(a)cit.ie; serusers(a)lists.iptel.org > Subject: Re: [Serusers] Portal for forking call to preferred end > device-sequential ringing > > I believe the lcr module will do q-value based sequential forking. > There > was a thread on that a while back. Search for q-value and Juha. LCR > can > be > found in head and as a backported 0.9.x module. > DB-based changes is the way to go! Doing dynamic ser.cfg changes is > not > feasible as long you have to restart ser (and thus reload contacts, > which > may take a long time). Updating the usrloc table outside SER does not > work > as SER loads usrloc info into memory. > g-) > > Samuel Osorio Calvo wrote: >> I guess a sequential forking ordered with the q value of the contact >> header field value would do what you are asking for. The user has >> just to configure the appropriate value in his/her UA to the >> preferred ringing sequence. This method is fully SIP compliant but >> what I am not sure is if SER does sequential forking in the q order >> (it wasn't a few months ago but some modifications might have added >> it...someone can tell you better than me). >> If you still want users to modify SER's database with a web >> interface, you might try to modify the q value in the usrloc >> database, of course if SER does q-ordered sequential forking, but I >> just think it adds lots of complexity to a feature which SER is >> supposed to provide together with minum user configuration in the >> endpoints. >> >> Hope it helps, >> >> Samuel. >> >> >> Unclassified. >>>>> "Aisling" <ashling.odriscoll(a)cit.ie> 06/21/05 12:54PM >>> >> Hello all, >> >> I'm hoping someone will offer an opinion as to how I should approach >> the >> following and if I am thinking along the correct lines: >> >> I am creating a web application where a user can dictate which device >> they want a call delivered to. So if I have a user with sip url >> "sip:2000@server" and they have registered with the SER server from a >> pda, pc and laptop, SER will currently parallel fork a call to all >> these >> destinations causing all softphones to ring (correct?). However I >> want a >> user to choose from a drop down menu in their browser (which I'm >> developing with servlets and JSP's) their preferred phone e.g. pda >> and then SER will fork the call to the softphone on the pda first. >> >> So basically my current plan is to retrieve the information from the >> user about their preferred phone (which will be associated with a >> particular IP address) and then dynamically modify the ser.cfg for a >> sequential forking rule for that user. I would appreciate opinions as >> to >> whether I am approaching this correctly or if there's an alternative >> method for such functionality (perhaps such as forking the call to >> the device which last registered or something)? >> >> Many Thanks, >> Aisling. >> >> >> >> >> -------------------Legal >> Disclaimer--------------------------------------- >> >> The above electronic mail transmission is confidential and intended >> only for the person to whom it is addressed. Its contents may be >> protected by legal and/or professional privilege. Should it be >> received by you in error please contact the sender at the above >> quoted email address. Any unauthorised form of reproduction of this >> message is strictly prohibited. The Institute does not guarantee the >> security of any information electronically transmitted and is not >> liable if the information contained in this communication is not a >> proper and complete record of the message as transmitted by the >> sender nor for any delay in its receipt. >> >> _______________________________________________ >> Serusers mailing list >> serusers(a)lists.iptel.org >> http://lists.iptel.org/mailman/listinfo/serusers > > > -------------------Legal > Disclaimer--------------------------------------- > > The above electronic mail transmission is confidential and intended > only > for the person to whom it is addressed. Its contents may be protected > by > legal and/or professional privilege. Should it be received by you in > error please contact the sender at the above quoted email address. Any > unauthorised form of reproduction of this message is strictly > prohibited. The Institute does not guarantee the security of any > information electronically transmitted and is not liable if the > information contained in this communication is not a proper and > complete > record of the message as transmitted by the sender nor for any delay > in > its receipt. > > > -------------------Legal > Disclaimer--------------------------------------- > > The above electronic mail transmission is confidential and intended > only for the person to whom it is addressed. Its contents may be > protected by legal and/or professional privilege. Should it be > received by you in error please contact the sender at the above > quoted email address. Any unauthorised form of reproduction of this > message is strictly prohibited. The Institute does not guarantee the > security of any information electronically transmitted and is not > liable if the information contained in this communication is not a > proper and complete record of the message as transmitted by the > sender nor for any delay in its receipt.

19 years, 4 months

[Users] avpop request and lcr ideas

by Kristin Galway

Thanks for creating this branch away from the seemingly stagnant SER project. I have in the past seen that requests for help or features have fallen on empty replies as evidenced while searching the mailing lists. I hope that this will be different here. I hope that be able to contribute back to this project once I become more versed in the inner workings as I see a very strong need for the following: Route lookups based on OCN/LERG data and carrier cost tables. (I already have the queries to do the but not the means to implement yet) This function would set say a defined number of flags to indicate outbound carriers based on cost. Having a module to do this would allow LCR lookups with fallover capabilities but based on OCN's and carrier data. Something else I would like to see is a way of using avops to set a fr_inv_timeout value. For instance: if (avp_db_load("$ruri/username", "s:voicemail")) { if (avp_check("s:voicemail", "eq/y/i")) { xlog("L_N", "\033[1m\033[36m ROUTE[0] - s:voicemail = y \033[0m\n"); # recipient has voicemail enabled. set flag(31) setflag(31); # test for a user set timeout if (avp_db_load("$ruri/username", i:vmtimeout")) { avp_write("$vmtimeout", s:callee_fr_inv_timer"); }; }; }; Thanks! Kristin ____________________________________________________ Yahoo! Sports Rekindle the Rivalries. Sign up for Fantasy Football http://football.fantasysports.yahoo.com

19 years, 4 months

[Serusers] Re: [Serdev] rel_0_9_0 release critical bugs/missing things

by Greger V. Teigre

As far I can see (using a filter on Matches versions: 0.9.3), there are no issues. The same search, but using HEAD, gives me 22 issues. Jan stated that everything he is aware of has been registered at http://bugs.sip-router.org/. I would like to make a call for submissions on http://bugs.sip-router.org/ of lacking documentation that you either have identified and started on (ref. earlier calls for documentation) or just identified (so that others may pick up the documentation effort). Let's try to make 0.9.x documentation as complete as possible now leading up to the release!! g-) Klaus Darilion wrote: > maybe on the bugtracker? > > Juha Heinanen wrote: >> is there somewhere a list of rel_0_9_0 release critical bugs/missing >> things? it would be high time to release the next stable version >> and if the lists exists, perhaps people could help to fix the loose >> ends. -- juha >> >> _______________________________________________ >> Serdev mailing list >> serdev(a)lists.iptel.org >> http://lists.iptel.org/mailman/listinfo/serdev >> >> > > _______________________________________________ > Serdev mailing list > serdev(a)lists.iptel.org > http://lists.iptel.org/mailman/listinfo/serdev

19 years, 4 months

Re: [Serusers] Portal for forking call to preferred end device -sequential ringing

by Samuel Osorio Calvo

I guess a sequential forking ordered with the q value of the contact header field value would do what you are asking for. The user has just to configure the appropriate value in his/her UA to the preferred ringing sequence. This method is fully SIP compliant but what I am not sure is if SER does sequential forking in the q order (it wasn't a few months ago but some modifications might have added it...someone can tell you better than me). If you still want users to modify SER's database with a web interface, you might try to modify the q value in the usrloc database, of course if SER does q-ordered sequential forking, but I just think it adds lots of complexity to a feature which SER is supposed to provide together with minum user configuration in the endpoints. Hope it helps, Samuel. Unclassified. >>> "Aisling" <ashling.odriscoll(a)cit.ie> 06/21/05 12:54PM >>> Hello all, I'm hoping someone will offer an opinion as to how I should approach the following and if I am thinking along the correct lines: I am creating a web application where a user can dictate which device they want a call delivered to. So if I have a user with sip url "sip:2000@server" and they have registered with the SER server from a pda, pc and laptop, SER will currently parallel fork a call to all these destinations causing all softphones to ring (correct?). However I want a user to choose from a drop down menu in their browser (which I'm developing with servlets and JSP's) their preferred phone e.g. pda and then SER will fork the call to the softphone on the pda first. So basically my current plan is to retrieve the information from the user about their preferred phone (which will be associated with a particular IP address) and then dynamically modify the ser.cfg for a sequential forking rule for that user. I would appreciate opinions as to whether I am approaching this correctly or if there's an alternative method for such functionality (perhaps such as forking the call to the device which last registered or something)? Many Thanks, Aisling. -------------------Legal Disclaimer--------------------------------------- The above electronic mail transmission is confidential and intended only for the person to whom it is addressed. Its contents may be protected by legal and/or professional privilege. Should it be received by you in error please contact the sender at the above quoted email address. Any unauthorised form of reproduction of this message is strictly prohibited. The Institute does not guarantee the security of any information electronically transmitted and is not liable if the information contained in this communication is not a proper and complete record of the message as transmitted by the sender nor for any delay in its receipt.

19 years, 4 months

[Serusers] iptel is hiring

by Jiri Kuthan

iptel is hiring developers who are familiar with programming in C, C++, and understand TCP/IP, SIP and ideally SER+SEMS. iptel is present in two locations: Berlin, Germany and Prague, Czech Republic. In some cases, we may consider remote work as well. Independent of the location, we are having nice offices with scenic views over the city and rooms crowded with seazoned SER developers :) I will be happy to take inquiries and applications off-line. Please include CV with work experience. Thank you! -jiri PS -- I am continously travelling, so don't be surprised if I cannot respond in real time. -- Jiri Kuthan http://iptel.org/~jiri/

19 years, 4 months

[serusers] pa module

by michael p

hi all i have some problems to include the pa module in SER. in the README it's a very quick config. i don't understand where exactly i hvae to put the function "handle_subscription("registrar");" ? i don't understand how it works tha pa module to create the tables for pa module ? (i don't find the script modules/pa/pa.sql ---- how can i find it and how i have to run it? ) thanks for the help Mike

19 years, 4 months

Re: [Serusers] Is there an AVP to alter "expires=" in REGISTERmessages?

by Samuel Osorio Calvo

I totally agree on the solution, luck with the vendor.... Samuel. Unclassified. >>> Java Rockx <javarockx(a)gmail.com> 06/21/05 01:40PM >>> Thanks for the feedback all. I've been considering what to do with this issue, and I decided that it is better to (but more painful) to have the vendor fix their firmware than it is for me to alter SER's functionality in a way as to move it away from RFC compliance. The save_extended_expires suggestion would be an easy fix, but the right thing to do is fix the problem rather than the symptom. Regards, Paul On 6/21/05, Samuel Osorio Calvo <samuel.osorio(a)nl.thalesgroup.com> wrote: > > I was taking a more detailled look at the code and it seems that the > Contact header will not be added into the reply if you use > save_noreply+sl_send_reply because the Contact buffer is added inside the > registrar module....but I recall that it worked. I suggest you to give it a > try and see the answer with ethereal|ngrep|* maybe it is taken after when > constructing the answer from the sipmsg. > Anyhow it would be easy to add a save_extended_expires command that makes > what you need but, as I said, people can start using these SIP patches to > build even more non-compliant proxies with SER.... > > Samuel. > > > Unclassified. > >>> "Greger V. Teigre" <greger(a)teigre.com> 06/21/05 07:19AM >>> > You're right of course :-) > Samuel's approach is more correct, but I'm not sure you will be able to > generate the correct reply using save_noreply and sl_reply (with Contact) ?! > Does save_noreply generate the reply? > g-) > > ---- Original Message ---- > From: Java Rockx > To: Greger V. Teigre > Cc: serusers > Sent: Monday, June 20, 2005 02:21 PM > Subject: Re: [Serusers] Is there an AVP to alter "expires=" in > REGISTERmessages? > > > Greger, > > > > That would be possible, but the way SER generates the 200OK reply, it > > would contain the altered "expires=" value. By doing so, the ATA > > would take that new value and use it, so if the ATA sent the REGISTER > > with an expires=300 and SER replied with a 200OK and a contact header > > containing expires=360, the ATA would not send another REGISTER for > > 360 seconds. > > > > I was fooling around with sip_msg.c and reply.c were I padded the > > expires with 60 seconds before saving to usrloc and then removing the > > pad before sending the reply and it works, but I would just feel > > better by not altering the source code. > > > > I guess I'd just feel more comfortable if SER had some sort of AVP or > > modparam for the registrar module that did this automagically. > > > > Regards, > > Paul > > > > > > On 6/20/05, Greger V. Teigre <greger(a)teigre.com> wrote: > > It was supposed to be short, but maybe too short. I meant doing the > > subst on the REGISTER message before save. > > g-) > > ---- Original Message ---- > > From: Greger V. Teigre > > To: Java Rockx ; serusers > > Sent: Monday, June 20, 2005 09:01 AM > > Subject: Re: [Serusers] Is there an AVP to alter "expires=" in > > REGISTERmessages? > > > >> Hi Paul, > >> Would it be possible to "do it upside down" ? ;-) I.e. do a > >> subst("/^Expires:(.*)[0-9]$/ Expires: yourvalue+60/gi"); > >> g-) > >> > >> ---- Original Message ---- > >> From: Java Rockx > >> To: serusers > >> Sent: Sunday, June 19, 2005 04:28 PM > >> Subject: [Serusers] Is there an AVP to alter "expires=" in REGISTER > >> messages? > >> > >>> Hi All. > >>> > >>> We've got some ATAs that don't quite re-REGISTER in a timely fashion > >>> and therefore SER expires the usrloc record a few seconds before the > >>> ATA sends another REGISTER message. > >>> > >>> Is there an AVP or something to add, for example, 60 seconds to the > >>> "expires=" value in the REGISTER message prior to calling save()? By > >>> doing so, these "broken" ATAs would re-REGISTER before SER removes > >>> the usrloc record from cache. > >>> > >>> Regards, > >>> Paul > >>> > >>> > >>> > >>> > >>> _______________________________________________ > >>> Serusers mailing list > >>> serusers(a)lists.iptel.org > >>> http://lists.iptel.org/mailman/listinfo/serusers > >> > >> > >> > >> _______________________________________________ > >> Serusers mailing list > >> serusers(a)lists.iptel.org > >> http://lists.iptel.org/mailman/listinfo/serusers > >

19 years, 4 months

[Users] Re: no solution yet :( that's why i've decided to write to you

by Daniel-Constantin Mierla

You have to create a dialing plan for openser also. In your script, after the block: if (!uri==myself) { # mark routing logic in request append_hf("P-hint: outbound\r\n"); route(1); break; }; (Just four your information, you don't need "if (uri==myself)" because will be true all the time) Back to dialing plan, you have to add some rules like: if(uri=~"^sip:05[0-9]+@") { # call to mobile rewritehost("192.168.1.35 <mailto:20105353490056@192.168.1.35%29>"); prefix("201"); route(1); break; } Daniel On 06/20/05 11:00, Ozan Blotter wrote: > Dear Team, > > I know this is annoying to post nearly same things but still no answer > :( Is it really so hard or can anybody tell me why this is not working. > > > Basically the system is as : > > ATA 1 : 12345 (registered and can call 54321, no problem) This is > Zyxel P2002. > ATA 2 : 54321 (registered and can call 12345, no problem) This is > Zyxel P2002 too. > ANALOG FXO : 201 (registered as 201, for test purposes i only > registered one port of it) This is Eusso 7104-S 4 Port Analog FXO and > i can add 3 more ports as available. > > With Brekeke's Ondo SIP Proxy, i created a simple dial-plan and it > worked, even i can add more prefixes no problem. But in SER i cannot > :( I'm using OpenSER. Normally it's like when i want to call a GSM, > proxy simply adds a prefix 201 which is same with registered sip > number for regarding analog port and forwards it (looks like > sip:20105353490056@192.168.1.35) > <mailto:20105353490056@192.168.1.35%29> to Gateway and Gateway simply > strips 201 from it and dials 05353490056, yes it connects. But what > this same does not work on SER, any ideas because it's very boring to > play all day and night ? > > Thanks.... > > This is my current SER.CFG as it comes with OPENSER. Can you please > help me to add lines where or/and add remove somethings... > > [root@localhost openser]# cat ser.cfg > # > # $Id: openser.cfg,v 1.1.1.1 2005/06/13 16:47:30 bogdan_iancu Exp $ > # > # simple quick-start config script > # > > # ----------- global configuration parameters ------------------------ > > #debug=3 # debug level (cmd line: -dddddddddd) > #fork=yes > #log_stderror=no # (cmd line: -E) > > /* Uncomment these lines to enter debugging mode > fork=no > log_stderror=yes > */ > > check_via=no # (cmd. line: -v) > dns=no # (cmd. line: -r) > rev_dns=no # (cmd. line: -R) > #port=5060 > #children=4 > fifo="/tmp/openser_fifo" > > # ------------------ module loading ---------------------------------- > > # Uncomment this if you want to use SQL database > #loadmodule "/usr/local/lib/ser/modules/mysql.so" > > loadmodule "/usr/lib/openser/modules/sl.so" > loadmodule "/usr/lib/openser/modules/tm.so" > loadmodule "/usr/lib/openser/modules/rr.so" > loadmodule "/usr/lib/openser/modules/maxfwd.so" > loadmodule "/usr/lib/openser/modules/usrloc.so" > loadmodule "/usr/lib/openser/modules/registrar.so" > loadmodule "/usr/lib/openser/modules/textops.so" > > # Uncomment this if you want digest authentication > # mysql.so must be loaded ! > #loadmodule "/usr/lib/openser/modules/auth.so" > #loadmodule "/usr/lib/openser/modules/auth_db.so" > > # ----------------- setting module-specific parameters --------------- > > # -- usrloc params -- > > modparam("usrloc", "db_mode", 0) > > # Uncomment this if you want to use SQL database > # for persistent storage and comment the previous line > #modparam("usrloc", "db_mode", 2) > > # -- auth params -- > # Uncomment if you are using auth module > # > #modparam("auth_db", "calculate_ha1", yes) > # > # If you set "calculate_ha1" parameter to yes (which true in this config), > # uncomment also the following parameter) > # > #modparam("auth_db", "password_column", "password") > > # -- rr params -- > # add value to ;lr param to make some broken UAs happy > modparam("rr", "enable_full_lr", 1) > > # ------------------------- request routing logic ------------------- > > # main routing logic > > route{ > > # initial sanity checks -- messages with > # max_forwards==0, or excessively long requests > if (!mf_process_maxfwd_header("10")) { > sl_send_reply("483","Too Many Hops"); > break; > }; > if (msg:len >= 2048 ) { > sl_send_reply("513", "Message too big"); > break; > }; > > > # we record-route all messages -- to make sure that > # subsequent messages will go through our proxy; that's > # particularly good if upstream and downstream entities > # use different transport protocol > if (!method=="REGISTER") record_route(); > > # subsequent messages withing a dialog should take the > # path determined by record-routing > if (loose_route()) { > # mark routing logic in request > append_hf("P-hint: rr-enforced\r\n"); > route(1); > break; > }; > > if (!uri==myself) { > # mark routing logic in request > append_hf("P-hint: outbound\r\n"); > route(1); > break; > }; > > # if the request is for other domain use UsrLoc > # (in case, it does not work, use the following command > # with proper names and addresses in it) > if (uri==myself) { > > if (method=="REGISTER") { > > # Uncomment this if you want to use digest authentication > # if (!www_authorize("openser.org", "subscriber")) { > # www_challenge("openser.org", "0"); > # break; > # }; > > save("location"); > break; > }; > > lookup("aliases"); > if (!uri==myself) { > append_hf("P-hint: outbound alias\r\n"); > route(1); > break; > }; > > # native SIP destinations are handled using our USRLOC DB > if (!lookup("location")) { > sl_send_reply("404", "Not Found"); > break; > }; > }; > append_hf("P-hint: usrloc applied\r\n"); > route(1); > } > > route[1] > { > # send it out now; use stateful forwarding as it works reliably > # even for UDP2TCP > if (!t_relay()) { > sl_reply_error(); > }; > } > > [root@localhost openser]# > >------------------------------------------------------------------------ > >_______________________________________________ >Team mailing list >Team(a)openser.org >http://openser.org/cgi-bin/mailman/listinfo/team > >

19 years, 4 months

Re: [Serusers] Is there an AVP to alter "expires=" in REGISTERmessages?

by Java Rockx

Thanks for the feedback all. I've been considering what to do with this issue, and I decided that it is better to (but more painful) to have the vendor fix their firmware than it is for me to alter SER's functionality in a way as to move it away from RFC compliance. The save_extended_expires suggestion would be an easy fix, but the right thing to do is fix the problem rather than the symptom. Regards, Paul On 6/21/05, Samuel Osorio Calvo <samuel.osorio(a)nl.thalesgroup.com> wrote: > > I was taking a more detailled look at the code and it seems that the > Contact header will not be added into the reply if you use > save_noreply+sl_send_reply because the Contact buffer is added inside the > registrar module....but I recall that it worked. I suggest you to give it a > try and see the answer with ethereal|ngrep|* maybe it is taken after when > constructing the answer from the sipmsg. > Anyhow it would be easy to add a save_extended_expires command that makes > what you need but, as I said, people can start using these SIP patches to > build even more non-compliant proxies with SER.... > > Samuel. > > > Unclassified. > >>> "Greger V. Teigre" <greger(a)teigre.com> 06/21/05 07:19AM >>> > You're right of course :-) > Samuel's approach is more correct, but I'm not sure you will be able to > generate the correct reply using save_noreply and sl_reply (with Contact) ?! > Does save_noreply generate the reply? > g-) > > ---- Original Message ---- > From: Java Rockx > To: Greger V. Teigre > Cc: serusers > Sent: Monday, June 20, 2005 02:21 PM > Subject: Re: [Serusers] Is there an AVP to alter "expires=" in > REGISTERmessages? > > > Greger, > > > > That would be possible, but the way SER generates the 200OK reply, it > > would contain the altered "expires=" value. By doing so, the ATA > > would take that new value and use it, so if the ATA sent the REGISTER > > with an expires=300 and SER replied with a 200OK and a contact header > > containing expires=360, the ATA would not send another REGISTER for > > 360 seconds. > > > > I was fooling around with sip_msg.c and reply.c were I padded the > > expires with 60 seconds before saving to usrloc and then removing the > > pad before sending the reply and it works, but I would just feel > > better by not altering the source code. > > > > I guess I'd just feel more comfortable if SER had some sort of AVP or > > modparam for the registrar module that did this automagically. > > > > Regards, > > Paul > > > > > > On 6/20/05, Greger V. Teigre <greger(a)teigre.com> wrote: > > It was supposed to be short, but maybe too short. I meant doing the > > subst on the REGISTER message before save. > > g-) > > ---- Original Message ---- > > From: Greger V. Teigre > > To: Java Rockx ; serusers > > Sent: Monday, June 20, 2005 09:01 AM > > Subject: Re: [Serusers] Is there an AVP to alter "expires=" in > > REGISTERmessages? > > > >> Hi Paul, > >> Would it be possible to "do it upside down" ? ;-) I.e. do a > >> subst("/^Expires:(.*)[0-9]$/ Expires: yourvalue+60/gi"); > >> g-) > >> > >> ---- Original Message ---- > >> From: Java Rockx > >> To: serusers > >> Sent: Sunday, June 19, 2005 04:28 PM > >> Subject: [Serusers] Is there an AVP to alter "expires=" in REGISTER > >> messages? > >> > >>> Hi All. > >>> > >>> We've got some ATAs that don't quite re-REGISTER in a timely fashion > >>> and therefore SER expires the usrloc record a few seconds before the > >>> ATA sends another REGISTER message. > >>> > >>> Is there an AVP or something to add, for example, 60 seconds to the > >>> "expires=" value in the REGISTER message prior to calling save()? By > >>> doing so, these "broken" ATAs would re-REGISTER before SER removes > >>> the usrloc record from cache. > >>> > >>> Regards, > >>> Paul > >>> > >>> > >>> > >>> > >>> _______________________________________________ > >>> Serusers mailing list > >>> serusers(a)lists.iptel.org > >>> http://lists.iptel.org/mailman/listinfo/serusers > >> > >> > >> > >> _______________________________________________ > >> Serusers mailing list > >> serusers(a)lists.iptel.org > >> http://lists.iptel.org/mailman/listinfo/serusers > >

19 years, 4 months

[Serusers] new voicamail.so

by Llanos Serna García-Conde

19 years, 4 months

← Newer
1
...
20
21
22
23
24
25
26
...
60
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users June 2005