Thanks for all the responses.
| Quote: |
| Quote: | | I compiled the default projects for PJSIP on Windows with Visual Studio and then ran the default pjsua (VS debug version) and couldn't get it to register with the PBX. eyeBeam/X-Lite registers with the PBX just fine. |
so take a packet trace of each.. whats the difference?
|
Haven't gotten to that yet, will try next.
| Quote: |
| Quote: | It sure would be nice if there were some step-by-step tutorials out there on how to use sipp and pjsua like how to register the tool as a SIP client, then make a call or answer a call, etc.
|
There are.. sipp has great documentation, and the pjsua page ont he pjsip wiki explains all the command line options. Heck you can even just start the app and add a new ua profile at run-time.
|
Unfortunately, attempting to use the command line options or config file input to register as a SIP client for PJSIP didn't work right off the bat. Maybe you have ideas on what could be the problem. See related post:
http://www.voipuser.org/forum_topic_13051.html
| Quote: |
| Quote: | | Unfortunately, I'm not a SIP expert or developer |
You dont need to be a developer, but you do need a fairly firm grasp of how SIP works, and working knowledge of computer communications, otherwise how will you know if it works or not? |
I'm familiar with the HTTP protocol of request and response message headers and body content. I haven't studied SIP in depth but it is similar to HTTP in making SIP requests & invites and receiving responses from the server or other party. But the RTP media session stuff is the stuff I don't know for sure.
I know if SIP on the PBX is working or not. Problem is I don't know if pjsip is working right or not or if I got the config wrong. Part of the problem with compiling code is that sometimes it compiles but doesn't run right because something is missing or is wrong.