sr-users

sr-users@lists.kamailio.org

46 participants
37553 discussions

[Serusers] SER voicemail installation problem
by rcarvalho＠iric.up.pt 28 May '06

28 May '06

Hi, I have installed SER witch is runnig fine, but now I'm trying to implement voicemail, but I don't understand who to do it because the information Im see its ambiguous. I tried to follow the instructions at this URL: http://www.iptel.org/ser/doc/prerelease/x1294.html where it says that I must edit Ser's Makefile.defs file and uncomment the line with '-DVOICE_MAIL' and '-D_TOTAG', but when I search those lines in that file, I cant find it! To overcome that problem, I included that flags in the makefile and then compiled again SER, however I couldnt compile the voicemail application like it instructs in that webpage because there is no ~/voicemail directory!! Is this guide too old that voicemail installation is no longer done this way? Or what have I done wrong? Im using ser-0.9.0, however in the latest release 0.9.6, Ive seen that its Makefile.defs hasnt also those flags to uncomment!! Best regards, Ricardo.

3 3

[Users] libradiusclient-ng-so.2 cann't share
by raviprakash sunkara 28 May '06

28 May '06

Hi Users.. I have problem in openser while I doing the accounting module. In that while I started the openser server its gives as " load_module : can't open module < /usr/local/lib/openser/module/acc.so> : libradiusclient-ng.so.2: can't open shared odject file : no file or directory " And " parse error fail to load " And also in enter the LD_LIBRARY_DIR in env. varible . please solve my issue bye.. -- Thanks and Regards with cheers Sunkara Ravi Prakash (Voip Developer) Hyperion Technology www.hyperion-tech.com <b>

1 0

Re: [Serusers] ser: problems with hearing voice
by Andrey Kouprianov 28 May '06

28 May '06

Yes you do. RTP (for voice and video) protocol normally uses ports 8000 for media transfer and 8001 for media control. If you are using X-lite, then port 8000 is used definitely. A client like eyeBeam, may choose from range of ports (i dont really know which exactly, but I always see ports in the range of 6000-7000). And Skype, for instance, can use ANY port available. Anyway, you can monitor ports <= 1024 and open the rest. Those are well known and they are the target. There are some ports > 1024 that Windows uses for it's services and you might want to find our what those (because, i dont really know :) are and monitor them as well. Good luck. On 5/23/06, Americania .it <americania(a)hotmail.com> wrote: > Hi, > I can' hear any voice when I call from a pc outside the Lan where ser is > installed (I've got a router-firewall): I've port 5060 UDP/TCP forwarded to > my ser server . > Do I have to open other ports ? > > Thanks > > > _______________________________________________ > Serusers mailing list > Serusers(a)lists.iptel.org > http://lists.iptel.org/mailman/listinfo/serusers >

4 3

[Serusers] 0.9.7-pre3 make install question
by Steve Blair 28 May '06

28 May '06

I just performed a cvs update of my 0.9.6 system. make proper, make clean both completed OK. make and make install produced a number of errors like the following. It is not clear what is producing these errors. Has anyone experienced this issue? If so do you have any idea what might be causing this type of error? Thanks,Steve make: $ sudo make Makefile.rules:84: action.d: No such file or directory Makefile.rules:84: crc.d: No such file or directory Makefile.rules:84: daemonize.d: No such file or directory Makefile.rules:84: data_lump.d: No such file or directory Makefile.rules:84: data_lump_rpl.d: No such file or directory Makefile.rules:84: dprint.d: No such file or directory Makefile.rules:84: dset.d: No such file or directory Makefile.rules:84: error.d: No such file or directory Makefile.rules:84: fifo_server.d: No such file or directory Makefile.rules:84: flags.d: No such file or directory Makefile.rules:84: forward.d: No such file or directory Makefile.rules:84: hash_func.d: No such file or directory Makefile.rules:84: ip_addr.d: No such file or directory Makefile.rules:84: main.d: No such file or directory Makefile.rules:84: md5.d: No such file or directory Makefile.rules:84: md5utils.d: No such file or directory Makefile.rules:84: modparam.d: No such file or directory Makefile.rules:84: msg_translator.d: No such file or directory Makefile.rules:84: pass_fd.d: No such file or directory Makefile.rules:84: proxy.d: No such file or directory Makefile.rules:84: qvalue.d: No such file or directory Makefile.rules:84: re.d: No such file or directory Makefile.rules:84: receive.d: No such file or directory Makefile.rules:84: resolve.d: No such file or directory Makefile.rules:84: route.d: No such file or directory Makefile.rules:84: route_struct.d: No such file or directory Makefile.rules:84: script_cb.d: No such file or directory Makefile.rules:84: socket_info.d: No such file or directory Makefile.rules:84: sr_module.d: No such file or directory Makefile.rules:84: stats.d: No such file or directory Makefile.rules:84: tcp_main.d: No such file or directory Makefile.rules:84: tcp_read.d: No such file or directory Makefile.rules:84: timer.d: No such file or directory Makefile.rules:84: tsend.d: No such file or directory Makefile.rules:84: udp_server.d: No such file or directory Makefile.rules:84: unixsock_server.d: No such file or directory Makefile.rules:84: usr_avp.d: No such file or directory Makefile.rules:84: mem/f_malloc.d: No such file or directory Makefile.rules:84: mem/mem.d: No such file or directory Makefile.rules:84: mem/memtest.d: No such file or directory Makefile.rules:84: mem/q_malloc.d: No such file or directory Makefile.rules:84: mem/shm_mem.d: No such file or directory Makefile.rules:84: mem/vq_malloc.d: No such file or directory Makefile.rules:84: parser/hf.d: No such file or directory Makefile.rules:84: parser/msg_parser.d: No such file or directory Makefile.rules:84: parser/parse_allow.d: No such file or directory Makefile.rules:84: parser/parse_content.d: No such file or directory Makefile.rules:84: parser/parse_cseq.d: No such file or directory Makefile.rules:84: parser/parse_disposition.d: No such file or directory Makefile.rules:84: parser/parse_diversion.d: No such file or directory Makefile.rules:84: parser/parse_event.d: No such file or directory Makefile.rules:84: parser/parse_expires.d: No such file or directory Makefile.rules:84: parser/parse_fline.d: No such file or directory Makefile.rules:84: parser/parse_from.d: No such file or directory Makefile.rules:84: parser/parse_hname2.d: No such file or directory Makefile.rules:84: parser/parse_hostport.d: No such file or directory Makefile.rules:84: parser/parse_methods.d: No such file or directory Makefile.rules:84: parser/parse_nameaddr.d: No such file or directory Makefile.rules:84: parser/parse_param.d: No such file or directory Makefile.rules:84: parser/parser_f.d: No such file or directory Makefile.rules:84: parser/parse_rpid.d: No such file or directory Makefile.rules:84: parser/parse_rr.d: No such file or directory Makefile.rules:84: parser/parse_sipifmatch.d: No such file or directory Makefile.rules:84: parser/parse_to.d: No such file or directory Makefile.rules:84: parser/parse_uri.d: No such file or directory Makefile.rules:84: parser/parse_via.d: No such file or directory Makefile.rules:84: parser/digest/digest.d: No such file or directory Makefile.rules:84: parser/digest/digest_parser.d: No such file or directory Makefile.rules:84: parser/digest/param_parser.d: No such file or directory Makefile.rules:84: parser/contact/contact.d: No such file or directory Makefile.rules:84: parser/contact/parse_contact.d: No such file or directory Makefile.rules:84: db/db.d: No such file or directory Makefile.rules:84: db/db_fifo.d: No such file or directory Makefile.rules:84: lex.yy.d: No such file or directory Makefile.rules:84: cfg.tab.d: No such file or directory make install: make[1]: Entering directory `/usr/sip_router/modules/tm' ../../Makefile.rules:84: callid.d: No such file or directory ../../Makefile.rules:84: dlg.d: No such file or directory ../../Makefile.rules:84: h_table.d: No such file or directory ../../Makefile.rules:84: lock.d: No such file or directory ../../Makefile.rules:84: sip_msg.d: No such file or directory ../../Makefile.rules:84: t_cancel.d: No such file or directory ../../Makefile.rules:84: t_dlg.d: No such file or directory ../../Makefile.rules:84: test.d: No such file or directory ../../Makefile.rules:84: t_fifo.d: No such file or directory ../../Makefile.rules:84: t_funcs.d: No such file or directory ../../Makefile.rules:84: t_fwd.d: No such file or directory ../../Makefile.rules:84: t_hooks.d: No such file or directory ../../Makefile.rules:84: timer.d: No such file or directory ../../Makefile.rules:84: t_lookup.d: No such file or directory ../../Makefile.rules:84: tm.d: No such file or directory ../../Makefile.rules:84: tm_load.d: No such file or directory ../../Makefile.rules:84: t_msgbuilder.d: No such file or directory ../../Makefile.rules:84: t_reply.d: No such file or directory ../../Makefile.rules:84: t_st

2 1

[Serusers] ser over NAT
by selma＠uofk.edu 28 May '06

28 May '06

Hi to all I'm using ser software sip proxy server, with micronet ipphone as UA, I want to send calls behind NAT router ,knowing that my UA is behind the NAT ,But the proxy server is in same host with the NAT DEVICE(same ip address), all the UA using uotbound proxy & did n't support STUN. can you help me. waiting for your reply salma VOIP Administrator University of Khartoum Sudan

1 0

[Serusers] Monitoring SER
by David 28 May '06

28 May '06

Hi, My company has deployed SER on a very large scale across the US and I would like to develop a way to monitor critical parts of SER and the servers that SER runs on. I have several questions regarding monitoring SER. 1. Can SER be SNMP enabled via something like SMUX or AgentX from net-snmp? 2. Does SER have any native SNMP support or other monitoring/logging hooks built in? 3. Do any mibs exist for SER / SIP? 4. I am also still trying to find out if SER has anyway to detect when a user looses registration either via SER internals or external watchdog scripts etc. Thanks David

2 1

[Serusers] Call-ID discrepancy
by Sam Lee 28 May '06

28 May '06

Hi All, I notice during the NGREP session , there is this field called Call-ID . It is something like this format :- 9ce97fd3-1a800040(a)172.16.1.123 <mailto:9ce97fd3-1a800040@172.16.1.123> . According to the RFC , it is said that this field is generated by the UA who started the request. I was just wondering, how did they get the IP Address at the back ? Which IP Address did they reference it from ? >From the RFC, it also says that the all request/response in the dialog should use the same Call-ID. When they say this, does it mean the entire field with the ip address (eg. 9ce97fd3-1a800040(a)172.16.1.123 ) or just the front part of it (eg. 9ce97fd3-1a800040 ) ? I notice that during a dialog session from a UA to the server going to the PSTN gateway, it was refering to this Call-ID until the point when the request was forwarded to the PSTN gateway. When the PSTN gateway replies, it replied with a same Call-ID with a different IP address at the back (9ce97fd3-1a800040(a)123.234.123.234 ) 172.16.1.123 - Private address of the UA 123.234.123.234 - Public address of the UA Strange ? Give your comment. Somehow i feel that this implementation is wrong. Regards, Sam

2 1

Re: [Serusers] backup route
by Giuseppe Parlato 27 May '06

27 May '06

May 24 17:02:17 dns ser: parse error (328,9-11): parse error May 24 17:02:17 dns ser: parse error (328,9-11): May 24 17:02:17 dns ser: WARNING:fm_free: free(0) called May 24 17:02:17 dns ser: ERROR: bad config file (2 errors) May 24 17:02:17 dns ser: ser startup failed Giuseppe ----- Original Message ----- From: "Giuseppe Parlato" <gparlato(a)tnet.it> To: "Vince Hoffman" <> Cc: <> Sent: Wednesday, May 24, 2006 5:06 PM Subject: Re: [Serusers] backup route > Yes, I have > > debug=3 # debug level (cmd line: -dddddddddd) > fork=yes > log_stderror=no # (cmd line: -E) > > > > ----- Original Message ----- > From: "Vince Hoffman" <vhoffman(a)mnet.co.uk> > To: "Giuseppe Parlato" <gparlato(a)tnet.it>; "Tobias Lindgren" > <tobias.lindgren(a)ip-only.se> > Cc: <serusers(a)iptel.org> > Sent: Wednesday, May 24, 2006 4:38 PM > Subject: RE: [Serusers] backup route > > > Do you have > debug=8 # debug level (cmd line: -dddddddddd) > fork=no > log_stderror=yes # (cmd line: -E) > > in your ser.cfg ? > if not then have a look in syslog and see if its logged the details > there. > > Vince > > ------------------------------------- > mnet Internet Limited > Support Services > > Helpdesk: 0870 3335577 > Fax: +44 (0)20 7324 3900 > Email: support(a)mnet.co.uk > Web: www.mnet.co.uk > > 132-140 Goswell Road > London EC1V 7DY > > > -----Original Message----- > From: Giuseppe Parlato [mailto:gparlato@tnet.it] > Sent: 24 May 2006 15:30 > To: Tobias Lindgren > Cc: serusers(a)iptel.org > Subject: Re: [Serusers] backup route > > Starting ser: ERROR: bad config file (2 errors) > > ser -c > ..... > config file ok, exiting... !!!really going crazy > > > Giuseppe > > ----- Original Message ----- > From: "Tobias Lindgren" <tobias.lindgren(a)ip-only.se> > To: "Giuseppe Parlato" <gparlato(a)tnet.it> > Cc: <> > Sent: Wednesday, May 24, 2006 4:19 PM > Subject: Re: [Serusers] backup route > > >> Hi, >> >> "ser -c" will tell you exactly which row that's not correct, also it >> will in many cases tell you what you have done wrong. >> >> Br, >> Tobias >> >> Giuseppe Parlato said the following on 2006-05-24 16:11: >>> help please, I'm going crazy. I still get 2 errors... where? >>> the new configuration: >>> >>> if (lookup("location")) { >>> rewritehost("mydomain.com"); >>> } else { >>> if ((uri=~"^sip:6200[0-9]+@") && (!uri=~"^sip:6200200@") && >>> (!uri=~"^sip:6200100@") ) { >>> rewritehost("routerA"); >>> forward(uri:host, uri:port); >>> break; >>> } else { >>> if ((uri=~"^sip:80[0-9]+@") | (uri=~"^sip:1[0-9][0-9]@") > | >>> (uri=~"^sip:1515@")) { >>> route(3); >>> break; >>> } >>> }; >>> }; >>> >>> >>> route[3] { >>> rewritehost("routerB"); >>> forward(uri:host, uri:port); >>> t_on_failure("3"); >>> t_relay(); >>> } >>> >>> failure_route[3] { >>> rewritehost("routerC"); >>> forward(uri:host, uri:port); >>> append_branch(); >>> t_relay(); >>> } >>> >>> >>> >>> how do I have to use } or }; ?? >>> >>> >>> Giuseppe >>> >>> >>> ----- Original Message ----- >>> From: "Giuseppe Parlato" <gparlato(a)tnet.it> >>> To: <serusers(a)iptel.org> >>> Cc: "Tobias Lindgren" <tobias.lindgren(a)ip-only.se> >>> Sent: Tuesday, May 23, 2006 1:20 PM >>> Subject: Re: [Serusers] backup route >>> >>> >>>> yes.. t_on_failure is "4" .. but when I restart ser I get 8 errors > in >>>> config file, is there any way to check where these errors are? >>>> >>>> route[3] { >>>> >>>> if ((uri=~"^sip:80[0-9]+@") | (uri=~"^sip:1[0-9][0-9]@") | >>>> (uri=~"^sip:1515@")) { >>>> route(4); >>>> } >>>> >>>> route[4] { >>>> rewritehost("routerA cisco IP"); >>>> forward(uri:host, uri:port); >>>> t_on_failure("4"); >>>> t_relay(); >>>> } >>>> >>>> failure_route[4] { >>>> rewritehost("routerB cisco IP"); >>>> forward(uri:host, uri:port); >>>> append_branch(); >>>> t_relay(); >>>> } >>>> >>>> >>>> Giuseppe >>>> >>>> ----- Original Message ----- >>>> From: "Tobias Lindgren" <tobias.lindgren(a)ip-only.se> >>>> To: "Giuseppe Parlato" <gparlato(a)tnet.it> >>>> Cc: <serusers(a)iptel.org> >>>> Sent: Tuesday, May 23, 2006 12:39 PM >>>> Subject: Re: [Serusers] backup route >>>> >>>> >>>>> Yep, that works fine. >>>>> >>>>> But t_on_failuer("X") == failure_route[X], so t_on_failure should > be 4, >>>>> if you use failure_route[4]. >>>>> >>>>> /T >>>>> >>>>> Giuseppe Parlato said the following on 2006-05-23 12:25: >>>>>> actually this is a subroute.. >>>>>> >>>>>> route[3] { >>>>>> if ((uri=~"^sip:80[0-9]+@") | (uri=~"^sip:1[0-9][0-9]@") | >>>>>> (uri=~"^sip:1515@")) { >>>>>> rewritehost("ip"); >>>>>> forward(uri:host, uri:port); >>>>>> break; >>>>>> }; >>>>>> >>>>>> .. called by he main route >>>>>> >>>>>> if ((uri=~"^sip:1200[0-9]+@") && (!uri=~"^sip:1200200@") && >>>>>> (!uri=~"^sip:1200100@") ) { >>>>>> rewritehost("ip"); >>>>>> forward(uri:host, uri:port); >>>>>> break; >>>>>> >>>>>> } else { >>>>>> route(3); >>>>>> break; >>>>>> >>>>>> ..can I do like this?? call a subroute [4] from e subroute [3]? >>>>>> >>>>>> if ((uri=~"^sip:80[0-9]+@") | (uri=~"^sip:1[0-9][0-9]@") | >>>>>> (uri=~"^sip:1515@")) { >>>>>> route(4); >>>>>> } >>>>>> route[4] { >>>>>> rewritehostport("192.168.0.1:5060"); >>>>>> t_on_failure("1"); >>>>>> t_relay(); >>>>>> } >>>>>> >>>>>> failure_route[4] { >>>>>> rewritehostport("192.168.0.2:5060"); >>>>>> append_branch(); >>>>>> t_relay(); >>>>>> } >>>>>> >>>>>> >>>>>> Giuseppe >>>>>> >>>>>> ----- Original Message ----- >>>>>> From: "Tobias Lindgren" <tobias.lindgren(a)ip-only.se> >>>>>> To: "Giuseppe Parlato" <gparlato(a)tnet.it> >>>>>> Cc: <serusers(a)iptel.org> >>>>>> Sent: Tuesday, May 23, 2006 9:56 AM >>>>>> Subject: Re: [Serusers] backup route >>>>>> >>>>>> >>>>>>> Hello, >>>>>>> >>>>>>> You can use the "route[]" and "failure_route[]" functions in > ser.cfg. >>>>>>> >>>>>>> A short example: >>>>>>> if ((uri=~"^sip:80[0-9]+@") | (uri=~"^sip:1[0-9][0-9]@") | >>>>>>> (uri=~"^sip:1515@")) { >>>>>>> route(1); >>>>>>> } >>>>>>> route[1] { >>>>>>> rewritehostport("192.168.0.1:5060"); >>>>>>> t_on_failure("1"); >>>>>>> t_relay(); >>>>>>> } >>>>>>> >>>>>>> failure_route[1] { >>>>>>> rewritehostport("192.168.0.2:5060"); >>>>>>> append_branch(); >>>>>>> t_relay(); >>>>>>> } >>>>>>> >>>>>>> This above would relay on that you have the "tm.so" module > loaded. >>>>>>> Also, >>>>>>> the tm-module has some parameters for timeouts and stuff (such as >>>>>>> fr_timer) which you should laborate with. >>>>>>> >>>>>>> Good luck! >>>>>>> >>>>>>> Br, >>>>>>> Tobias >>>>>>> >>>>>>> Giuseppe Parlato said the following on 2006-05-22 18:04: >>>>>>>> When calling some numbers I have to forward calls to a router >>>>>>>> cisco (then it wil forward calls out through isdn) or to a > backup >>>>>>>> router >>>>>>>> cisco if the first one is busy. The route to primary cisco > router >>>>>>>> works >>>>>>>> but I don't know how to implement the backup route in ser.cfg ? > how >>>>>>>> can >>>>>>>> I configure a backup route in sip server? >>>>>>>> I hope someone can answer me soon, I'm in trouble :| >>>>>>>> >>>>>>>> >>>>>>>> if ((uri=~"^sip:80[0-9]+@") | (uri=~"^sip:1[0-9][0-9]@") | >>>>>>>> (uri=~"^sip:1515@")) { >>>>>>>> rewritehost("router IP"); >>>>>>>> forward(uri:host, uri:port); >>>>>>>> break; >>>>>>>> }; >>>>>>>> >>>>>>>> Thanks >>>>>>>> >>>>>>>> Giuseppe >>>>>>>> >>>>>>>> >>>>>>>> > ------------------------------------------------------------------------ >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Serusers mailing list >>>>>>>> Serusers(a)iptel.org >>>>>>>> http://mail.iptel.org/mailman/listinfo/serusers >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> No virus found in this incoming message. >>>>>>> Checked by AVG Free Edition. >>>>>>> Version: 7.1.392 / Virus Database: 268.6.1/344 - Release Date: >>>>>>> 19/05/2006 >>>>>>> >>>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> No virus found in this incoming message. >>>>> Checked by AVG Free Edition. >>>>> Version: 7.1.392 / Virus Database: 268.7.0/345 - Release Date: >>>>> 22/05/2006 >>>>> >>>>> >>>> >>> >> >> >> -- >> No virus found in this incoming message. >> Checked by AVG Free Edition. >> Version: 7.1.394 / Virus Database: 268.7.0/346 - Release Date: > 23/05/2006 >> > > _______________________________________________ > Serusers mailing list > Serusers(a)lists.iptel.org > http://lists.iptel.org/mailman/listinfo/serusers > > > > This message has been scanned for viruses by 3Labs - www.mnet.net.uk > > > -- > No virus found in this incoming message. > Checked by AVG Free Edition. > Version: 7.1.394 / Virus Database: 268.7.0/346 - Release Date: 23/05/2006 >

3 6

[Serusers] too many hops response
by Guty 27 May '06

27 May '06

When I try to conect to SER whit any client, i receive a "too many hops" response. I've tried with eyebeam in a win XP PC, an in the same pc where I've SER whit kphone, an the result is the same. Any clue? Thanks, Gustavo PD: im running ser presence snapshot.

1 0

Re: [Serusers] ser: problems with hearing voice
by Americania .it 27 May '06

27 May '06

>From: Ladislav Andel <ladia6(a)centrum.cz> >To: "Americania .it" <americania(a)hotmail.com> >Subject: Re: [Serusers] ser: problems with hearing voice >Date: Sat, 27 May 2006 01:05:57 +0200 > >Hi, >can you draw your network scenario (just where is SER, SIP phones and NAT >devices in the network) ? It'll be easier to see the problem. >Since you run SER behind NAT (am I right?) nathelper checks for private >addresses {RFC1918) and so the logic of ser.cfg is not then appropriate. >Can you send your ser.cfg? Have you read at onsip.org the getting started >document? > >Next time catch your SIP messages on the server by: >ngrep -d any -W byline -O /tmp/trace.log port 5060 >or >tcpdump -p -s 0 -i any -e port 5060 -w /tmp/trace.log > >Ladislav > >Americania .it wrote: >>I've opened port 8000/8001 on my router .. >> >>I've installed Portrptr to monitor wich ports are used by 3cx Phone (it >>says 5062 5063). >>I've opened 5060 to 5070 udp) too. >>Nothing has changed : no voice. >> >>I've tried XLite : same thing , no voice. >> >>I've tried to make a call from my Lan where Ser is installed to an user >>outside and he can hear me but I can't hear him. >> >>If I enstablish a call from an outside user to another outside user .. no >>voice at all! >> >>I attach X-Lite log for this case: >> >>What can I do now ??? >> >> >> >>SEND TIME: 3474935 >>SEND >> 80.105.2.110:5060 >>INVITE sip:vicky@80.105.2.110 SIP/2.0 >>Via: SIP/2.0/UDP >>192.168.0.102:5060;rport;branch=z9hG4bK2C92FDF50A36406697C9FDB48723EC39 >>From: claudio <sip:claudio@80.105.2.110>;tag=512156865 >>To: <sip:vicky@80.105.2.110> >>Contact: <sip:claudio@192.168.0.102:5060> >>Call-ID: 374B53F3-8081-45B1-AD92-4075AF931C00(a)192.168.0.102 >>CSeq: 21421 INVITE >>Max-Forwards: 70 >>Content-Type: application/sdp >>User-Agent: X-Lite release 1105x >>Content-Length: 308 >> >>v=0 >>o=claudio 3474591 3474934 IN IP4 192.168.0.102 >>s=X-Lite >>c=IN IP4 192.168.0.102 >>t=0 0 >>m=audio 8000 RTP/AVP 0 8 3 98 97 101 >>a=rtpmap:0 pcmu/8000 >>a=rtpmap:8 pcma/8000 >>a=rtpmap:3 gsm/8000 >>a=rtpmap:98 iLBC/8000 >>a=rtpmap:97 speex/8000 >>a=rtpmap:101 telephone-event/8000 >>a=fmtp:101 0-15 >>a=sendrecv >> >>RECEIVE TIME: 3475635 >>RECEIVE << 80.105.2.110:5060 >>SIP/2.0 100 trying -- your call is important to us >>Via: SIP/2.0/UDP >>192.168.0.102:5060;rport=39267;branch=z9hG4bK2C92FDF50A36406697C9FDB48723EC39;received=62.101.126.230 >> >>From: claudio <sip:claudio@80.105.2.110>;tag=512156865 >>To: <sip:vicky@80.105.2.110> >>Call-ID: 374B53F3-8081-45B1-AD92-4075AF931C00(a)192.168.0.102 >>CSeq: 21421 INVITE >>Server: Sip EXpress router (0.9.4 (i386/linux)) >>Content-Length: 0 >>Warning: 392 10.0.0.133:5060 "Noisy feedback tells: pid=9102 >>req_src_ip=62.101.126.230 req_src_port=39267 in_uri=sip:vicky@80.105.2.110 >>out_uri=sip:vicky@87.1.193.94:5060 via_cnt==1" >> >> >>RECEIVE TIME: 3476404 >>RECEIVE << 80.105.2.110:5060 >>SIP/2.0 180 Ringing >>Via: SIP/2.0/UDP >>192.168.0.102:5060;received=62.101.126.230;rport=39267;branch=z9hG4bK2C92FDF50A36406697C9FDB48723EC39 >> >>Record-Route: <sip:10.0.0.133;ftag=512156865;lr=on> >>From: claudio <sip:claudio@80.105.2.110>;tag=512156865 >>To: <sip:vicky@80.105.2.110>;tag=806313b969ebda11a7f5000d613deeec >>Call-ID: 374B53F3-8081-45B1-AD92-4075AF931C00(a)192.168.0.102 >>CSeq: 21421 INVITE >>Contact: <sip:vicky@87.1.193.94:5060> >>Max-Forwards: 16 >>Server: SIPPER for 3CX Phone >>Allow: INVITE, ACK, CANCEL, BYE, NOTIFY >>Content-Length: 0 >> >> >>RECEIVE TIME: 3480857 >>RECEIVE << 80.105.2.110:5060 >>SIP/2.0 200 OK >>Via: SIP/2.0/UDP >>192.168.0.102:5060;received=62.101.126.230;rport=39267;branch=z9hG4bK2C92FDF50A36406697C9FDB48723EC39 >> >>Record-Route: <sip:10.0.0.133;ftag=512156865;lr=on> >>From: claudio <sip:claudio@80.105.2.110>;tag=512156865 >>To: <sip:vicky@80.105.2.110>;tag=806313b969ebda11a7f5000d613deeec >>Call-ID: 374B53F3-8081-45B1-AD92-4075AF931C00(a)192.168.0.102 >>CSeq: 21421 INVITE >>Contact: <sip:vicky@87.1.193.94:5060> >>Max-Forwards: 16 >>Server: SIPPER for 3CX Phone >>Allow: INVITE, ACK, CANCEL, BYE, NOTIFY >>Content-Type: application/sdp >>Content-Length: 261 >> >>v=0 >>o=root 5424921 5424921 IN IP4 192.168.1.2 >>s=call >>c=IN IP4 10.0.0.133 >>t=0 0 >>m=audio 35268 RTP/AVP 0 8 3 97 101 >>a=rtpmap:0 PCMU/8000 >>a=rtpmap:8 PCMA/8000 >>a=rtpmap:3 GSM/8000 >>a=rtpmap:97 iLBC/8000 >>a=rtpmap:101 telephone-event/8000 >>a=nortpproxy:yes >> >>SEND TIME: 3480866 >>SEND >> 10.0.0.133:5060 >>ACK sip:vicky@87.1.193.94:5060 SIP/2.0 >>Via: SIP/2.0/UDP >>192.168.0.102:5060;rport;branch=z9hG4bK28E629C6EC9342FFA3B89AF152782C9D >>From: claudio <sip:claudio@80.105.2.110>;tag=512156865 >>To: <sip:vicky@80.105.2.110>;tag=806313b969ebda11a7f5000d613deeec >>Contact: <sip:claudio@192.168.0.102:5060> >>Route: <sip:10.0.0.133;ftag=512156865;lr=on> >>Call-ID: 374B53F3-8081-45B1-AD92-4075AF931C00(a)192.168.0.102 >>CSeq: 21421 ACK >>Max-Forwards: 70 >>Content-Length: 0 >> >> >>RECEIVE TIME: 3493387 >>RECEIVE << 80.105.2.110:5060 >> >>SEND TIME: 3500646 >>SEND >> 80.105.2.110:5060 >>REGISTER sip:80.105.2.110 SIP/2.0 >>Via: SIP/2.0/UDP >>192.168.0.102:5060;rport;branch=z9hG4bKC9C44D63BB0344C4B10F04D9C36AD603 >>From: claudio <sip:claudio@80.105.2.110>;tag=425214505 >>To: claudio <sip:claudio@80.105.2.110> >>Contact: "claudio" <sip:claudio@192.168.0.102:5060> >>Call-ID: 63C1074ADB2E448487DECC8994F610F3(a)80.105.2.110 >>CSeq: 48998 REGISTER >>Expires: 160 >>Max-Forwards: 70 >>User-Agent: X-Lite release 1105x >>Content-Length: 0 >> >> >>SEND TIME: 3502150 >>SEND >> 80.105.2.110:5060 >>REGISTER sip:80.105.2.110 SIP/2.0 >>Via: SIP/2.0/UDP >>192.168.0.102:5060;rport;branch=z9hG4bKC9C44D63BB0344C4B10F04D9C36AD603 >>From: claudio <sip:claudio@80.105.2.110>;tag=425214505 >>To: claudio <sip:claudio@80.105.2.110> >>Contact: "claudio" <sip:claudio@192.168.0.102:5060> >>Call-ID: 63C1074ADB2E448487DECC8994F610F3(a)80.105.2.110 >>CSeq: 48998 REGISTER >>Expires: 160 >>Max-Forwards: 70 >>User-Agent: X-Lite release 1105x >>Content-Length: 0 >> >> >>RECEIVE TIME: 3502580 >>RECEIVE << 80.105.2.110:5060 >>SIP/2.0 401 Unauthorized >>Via: SIP/2.0/UDP >>192.168.0.102:5060;rport=39267;branch=z9hG4bKC9C44D63BB0344C4B10F04D9C36AD603;received=62.101.126.230 >> >>From: claudio <sip:claudio@80.105.2.110>;tag=425214505 >>To: claudio >><sip:claudio@80.105.2.110>;tag=2a08c327b8d597781b526eaf86695180.f298 >>Call-ID: 63C1074ADB2E448487DECC8994F610F3(a)80.105.2.110 >>CSeq: 48998 REGISTER >>WWW-Authenticate: Digest realm="80.105.2.110", >>nonce="447770198404c4bc9438e9ce6159814a63b777d4" >>Server: Sip EXpress router (0.9.4 (i386/linux)) >>Content-Length: 0 >>Warning: 392 10.0.0.133:5060 "Noisy feedback tells: pid=9102 >>req_src_ip=62.101.126.230 req_src_port=39267 in_uri=sip:80.105.2.110 >>out_uri=sip:80.105.2.110 via_cnt==1" >> >> >>SEND TIME: 3502583 >>SEND >> 80.105.2.110:5060 >>REGISTER sip:80.105.2.110 SIP/2.0 >>Via: SIP/2.0/UDP >>192.168.0.102:5060;rport;branch=z9hG4bKC8C6FD549B75482F9BBE53C7AE958465 >>From: claudio <sip:claudio@80.105.2.110>;tag=425214505 >>To: claudio <sip:claudio@80.105.2.110> >>Contact: "claudio" <sip:claudio@192.168.0.102:5060> >>Call-ID: 63C1074ADB2E448487DECC8994F610F3(a)80.105.2.110 >>CSeq: 48999 REGISTER >>Expires: 160 >>Authorization: Digest >>username="claudio",realm="80.105.2.110",nonce="447770198404c4bc9438e9ce6159814a63b777d4",response="24188c3172d488f1296a7c2ad2a048d6",uri="sip:80.105.2.110" >> >>Max-Forwards: 70 >>User-Agent: X-Lite release 1105x >>Content-Length: 0 >> >> >>RECEIVE TIME: 3502841 >>RECEIVE << 80.105.2.110:5060 >>SIP/2.0 200 OK >>Via: SIP/2.0/UDP >>192.168.0.102:5060;rport=39267;branch=z9hG4bKC8C6FD549B75482F9BBE53C7AE958465;received=62.101.126.230 >> >>From: claudio <sip:claudio@80.105.2.110>;tag=425214505 >>To: claudio >><sip:claudio@80.105.2.110>;tag=2a08c327b8d597781b526eaf86695180.24dd >>Call-ID: 63C1074ADB2E448487DECC8994F610F3(a)80.105.2.110 >>CSeq: 48999 REGISTER >>Contact: <sip:claudio@62.101.126.230:39267>;expires=160 >>Server: Sip EXpress router (0.9.4 (i386/linux)) >>Content-Length: 0 >>Warning: 392 10.0.0.133:5060 "Noisy feedback tells: pid=9102 >>req_src_ip=62.101.126.230 req_src_port=39267 in_uri=sip:80.105.2.110 >>out_uri=sip:80.105.2.110 via_cnt==1" >> >>____________________________________________________________________________ >> >>____________________________________________________________________________ >> >> >> >> >>>From: "Andrey Kouprianov" <andrey.kouprianov(a)gmail.com> >>>To: serusers(a)iptel.org >>>Subject: Re: [Serusers] ser: problems with hearing voice >>>Date: Wed, 24 May 2006 00:24:05 +0700 >>> >>>Yes you do. RTP (for voice and video) protocol normally uses ports >>>8000 for media transfer and 8001 for media control. If you are using >>>X-lite, then port 8000 is used definitely. A client like eyeBeam, may >>>choose from range of ports (i dont really know which exactly, but I >>>always see ports in the range of 6000-7000). And Skype, for instance, >>>can use ANY port available. >>> >>>Anyway, you can monitor ports <= 1024 and open the rest. Those are >>>well known and they are the target. There are some ports > 1024 that >>>Windows uses for it's services and you might want to find our what >>>those (because, i dont really know :) are and monitor them as well. >>> >>>Good luck. >>> >>>On 5/23/06, Americania .it <americania(a)hotmail.com> wrote: >>>>Hi, >>>>I can' hear any voice when I call from a pc outside the Lan where ser >>>>is >>>>installed (I've got a router-firewall): I've port 5060 UDP/TCP >>>>forwarded to >>>>my ser server . >>>>Do I have to open other ports ? >>>> >>>>Thanks >>>> >>>> >>>>_______________________________________________ >>>>Serusers mailing list >>>>Serusers(a)lists.iptel.org >>>>http://lists.iptel.org/mailman/listinfo/serusers >>>> >>>_______________________________________________ >>>Serusers mailing list >>>Serusers(a)lists.iptel.org >>>http://lists.iptel.org/mailman/listinfo/serusers >> >> >>_______________________________________________ >>Serusers mailing list >>Serusers(a)lists.iptel.org >>http://lists.iptel.org/mailman/listinfo/serusers >> >> >

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users