Hi,
When I get a 503 response with retry-after for REGISTER,I start
a timer for the time in retry-after header but would like to know
whether there is any upper limit that I can have for this timer? Like
say 180 sec,so that if the retry-value s greater that 180 instead of
waiting,give the error response to the application.
Because when a server sends 503 with retry-header value of say 300, may
end up in waiting too long.
Thx
Anand.
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of
Premalatha Kuppan
Sent: Friday, February 05, 2010 11:43 AM
To: [email protected]
Subject: Re: [Sip-implementors] Commercial sip stack
I have some doubts regarding PJSIP:
I tried building it on my ubuntu 9.04 version. Common makefile, it was
successful.
But dono how to run and test the sip stack.
But Make filed in this directory pjsip-apps/src/python,
It says, following error,
"pjsua.h:25:20: error: Python.h: No such file or directory"
I just wonder do i need to install Python related stuff. I dono. Please
help me.
When googled, i also found there are pjsua C API and Pjsip python API.
Please help me, whether its good to take PJSIP. Whether its depend on
Python ?
Thanks,
2010/2/5 Jack W. Lix <[email protected]>
> Hi,
>
> Telesoft has a C sip stack designed with embedded systems in mind.
> Very small footprint.
>
> <http://www.telesoft-intl.com/> http://www.telesoft-intl.com/
>
> Good luck with your project,
>
> Jack
>
>
>
> >> >> ________________________________
> > >> From: Premalatha Kuppan <[email protected]>
> >> >> To: [email protected]
> >> >> Sent: Wed, February 3, 2010 5:21:12 PM
> >> >> Subject: [Sip-implementors] Commercial sip stack
> >> >>
> >> >> Hi,
> >> >>
> >> >> Can ny1 suggest me avery good commercial SIP STACK ?
> >> >>
> >> >> Which be portable, gud maintainability, small footprint and Code
> >> >> in
> C.
> >> >>
> >> >> Thanks,
> >> >> Premalatha
> >> >> _______________________________________________
> >> >> Sip-implementors mailing list
> >> >> [email protected]
> >> >>
> >> >> <https://lists.cs.columbia.edu/cucslists/listinfo/sip-implemento
> >> >> rs>
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
> >> >>
> >> >>
> >> >>
> >> >>
> >> >> _______________________________________________
> >> >> Sip-implementors mailing list
> >> >> [email protected]
> >> >>
> >> >> <https://lists.cs.columbia.edu/cucslists/listinfo/sip-implemento
> >> >> rs>
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
> >> >>
> >> > _______________________________________________
> >> > Sip-implementors mailing list
> >> > [email protected]
> >> >
> >> > <https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementor
> >> > s>
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
> >> >
> >>
> >
> >
> > ------------------------------
> >
> > _______________________________________________
> > Sip-implementors mailing list
> > [email protected]
> > <https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors>
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
> >
> > End of Sip-implementors Digest, Vol 83, Issue 10
> > ************************************************
> >
> >
>
>
> _______________________________________________
> Sip-implementors mailing list
> [email protected]
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
>
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
