That way someone can point out what I’m missing possibly. When writing a server, choose a port that is not already dedicated to some other service. When I get a free moment I will edit this post and list all ports, and general config settings that are allowing my chan_sip to fully work…which in theory should be similar to pjsip from a port perspective. The server program begins by creating a new ServerSocketobject to listen on a specific port (see the statement in bold in the following code segment). ![]() But yes, please let me know if I’m missing something. Many people have expressed that if I have a working chan_sip implementation, and convert to pjsip, that myself and others should be good to go, since it’s all sip and the ports that sip uses. I honestly want to know if I’m possibly missing something, please teach me, and redirect me to the port set that would exist outside of what the chan_sip implementation uses, because quite possibly, I’m missing something and that would be great for me to know, for when I go forward. Is there some sort of extended port set on pjsip that lies outside of the port set for chan_sip I don’t know about…maybe I’m looking at this wrong, but from a protocol perspective that makes no sense to me since it’s still sip but with a different driver. If I convert my extensions to pjsip it should all just work since the same fundamental ports that my Chan sip is using and working with should be what pjsip uses outside of if I decide pjsip should reside on 5060 or 5061. To me the sip protocol is the sip protocol. Can you elaborate on the “right” ports since its 5060 or 5061 that could be used and all the players such as rtp ports 10000-20000, etc and all the other ports I don’t have memorized but utilize for my working chan_sip implementation. That beans pushing to knock my shack down, Jed said. But yeah the first 4 days spent with trying both at the time, led me to more success with chan_sip. But those pressure-filled situations are not limited to school. As well a little time to knock down Fortigates VoIP ALG implementation, since it was messing with sip/rtp and freepBx. knock serveripaddress 3333 4444 5555 & & ssh -i ubuntu. There was a few days needed to make sure all the correct ports were Used and open on the edge device to the truck pilot provider. Port knocking does not generally lower the security of an unix system. ![]() I was able to get chan_sip working from day 5, and it’s working for 700 phones across 30 sites for about 3 years now. I’m not denying it works great, just expressing my experience.
0 Comments
Leave a Reply. |