16 Sep
2013
16 Sep
'13
11:30 p.m.
Hello,
you can call save() for 200ok received from downstream. In case you deal
with nat or multiple local sockets, you need to call the functions for
fixing the registration as well as storing the local socket.
The processing can be like:
- forward register
- if getting 200ok, call save() for it
- if local timeout, call save in failure route -- you will have to call
it via a sub-route, because save() is only allowed in request route and
reply route, although failure_route should be safe for it
- if other reply from downstram, let it go to the phone
Cheers,
Daniel
On 9/16/13 9:08 PM, Steve Davies wrote:
On 16 September 2013 21:03, Olle E. Johansson <oej(a)edvina.net
<mailto:oej@edvina.net>> wrote:
I say you're making it too complex. Let the proxy be a proxy and
force the client to behave properly.
The client is an ordinary SIP phone. I don't have any control over
its behaviour. But I'm not sure in what way it is behaving improperly?
Steve
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Trainings - Berlin, Oct 21-24; Miami, Nov 11-13, 2013
- more details about Kamailio trainings at http://www.asipto.com -