← #7 .
Quote:
... I install and edit .bashrc
|
Please read post #6 : ".. do never add any *PATH text to .bashrc."
The text about .bashrc is to be used only with a University Computer,
with no write access to /usr/. (The text origins from year 1999 ?)
* I guess you can do # 'make install', to have /usr/local/bin/ns ?
The executable 'ns' is hard coded to know any library location.
So adding a text to .bashrc really makes no sense.
The valid SIP examples are in "sip-examples-2014.tar.gz": Read post #6.
`example.tcl´ from
http://code.dma.unipi.it/projects/ns...tcl?format=txt
... is not a valid example (for r29), I think :
[knudfl@localhost]$ ./ns-sip-r29 example.tcl
invalid command name "Agent/OCProxy"
while executing
"Agent/OCProxy create _o247 biloxi.com"
"set sipBLX [new Agent/OCProxy biloxi.com]"
(file "example.tcl" line 79)
.... Don't know why you get {invalid command name "Agent/SIPProxy"}.
? A failed build of ns-2.29.3 + sip-svn.r29__ns229.patch ?
Or you may be using the 'ns' you have from ns-2.35 ?
→ An 'ns' with no "sip" will show `invalid command name "Agent/SIPProxy".
Any questions ? Then please specify your OS :
a) Show the reply from the command $ uname -m
b) OS name and version, please.
-