sr-users

sr-users@lists.kamailio.org

10 participants
37461 discussions

[Users] Updating usrloc database
by Britton Payne 20 Jun '06

20 Jun '06

Hello, all. In our current configuration OpenSER is using a MySQL db for location information. Registrations made to openser get pushed into the db ok, but changes to the database directly (like additions) do not appear to make it to openser. Is there a way to make changes to the database become visible to openser like a fifo command or should I be using db_mode=1? We would like to be able to do this without restarting openser and dropping calls in progress. Thank you, Britton

5 4

[Users] RE: acc.so problem
by Edson 20 Jun '06

20 Jun '06

>From the first line message, it seems to me that You have some concern with Your MySQL server.... it seems that it run out of free socked... or that the user is not available... please, try to take a look on this... Edson. P.S: post to the list as well... the chances to a good help increases... ;) > -----Original Message----- > From: zhan li [mailto:zhan_li_2000@hotmail.com] > Sent: sexta-feira, 16 de junho de 2006 01:52 > To: bogdan(a)voice-system.ro > Cc: 4lists(a)gmail.com > Subject: acc.so problem > > Hello > > When I try to start the openser with acc modules, I got the following > error, > the v136545352 is very odd, I checked the version table of Location which > is 1001, I wonder what v136545352 means in error message. > > I search online, and found another people get the exactly same problem > with > mine. > > Thanks > > > > 0(0) db_init: Connection 'mysql://openser:openserrw@localhost/openser' not > found in pool > 0(0) new_connection: Opening MySQL connection: > mysql://openser:openserrw@localhost/openser > 0(0) new_connection: Connection type is Localhost via UNIX socket > 0(0) new_connection: Protocol version is 10 > 0(0) new_connection: Server version is 4.0.18-standard > 0(0) usrloc:preload_udomain: Wrong version v136545352 for table > <location>, > expected v1001 > 0(0) register_udomain(): Error while preloading domain 'location' > 0(0) pool_remove: Removing connection from the pool > 0(0) domain_fixup(): Error while registering domain > ERROR: error -1 while trying to fix configuration

2 1

Re: [Serusers] Re: mediaproxy problem
by Andrey Kouprianov 20 Jun '06

20 Jun '06

Thank you Hakan!! That's great news! I still cant get my hands free to deal with this issue. However, I looked up my FreeBSD ports and python mysqldb support lib is there. :) I'll try to run mediaproxy asap and let the list know about the outcome. Regards, Andrey. On 6/20/06, Hakan YASTI <hakanyasti(a)gmail.com> wrote: > Hi Andrey, > > It has worked. After I installed > py24-MySQLdb-1.2.1.p2 Access a MySQL database through Python > it is working now. > Thanks for your kind interest. > Best Regards, > Hakan. > > > ----- Original Message ----- > From: "Andrey Kouprianov" <andrey.kouprianov(a)gmail.com> > To: <serusers(a)iptel.org> > Sent: Sunday, June 18, 2006 2:58 PM > Subject: Re: [Serusers] Re: mediaproxy problem > > > > Will try!! :) > > > > Thanx a lot! > > > > On 6/18/06, rusl <rusl(a)jpfortune.org> wrote: > >> > >> You need to have the python " MySQLdb" module installed. > >> > >> On Sunday 18. June 2006 11:45, Andrey Kouprianov wrote: > >> > Yup. Me too. I hope to get some comments on this... :) > >> > > >> > Anyone? > >> > > >> > On 6/17/06, Hakan YASTI <hakanyasti(a)gmail.com> wrote: > >> > > Hi Andrey, > >> > > > >> > > I have the same problem with proxy dispatcher. Have got a solution > >> > > for > >> > > your problem. I couldn't see any solution for your problem. > >> > > > >> > > Hope to hera soon. > >> > > > >> > > Best Regards, > >> > > Hakan. > >> > > > >> > > > >> > > > >> > > > >> > > Hi, > >> > > >> > I have tried to install mediaproxy 1.7.2. So, i did. Configuration > >> > > >> > > was > >> > > >> > about the same as 1.4.2, however, "mediaproxy start", just > >> > > >> > > started > >> > > >> > mediaproxy.py, but not proxydispatcher.py. Version 1.4.2 started > >> > > >> > > them > >> > > >> > both w/o any problem. Trying to start proxydispatcher.py > >> > > >> > > independently > >> > > >> > did not give any results. /var/run/proxydispatcher.sock is > >> > > >> > > simply not > >> > > >> > there anymore. There are no logs or whatsoever, that I could show > >> > > >> > > you, > >> > > >> > because I did not find any. Anyway, here's the config > >> > > >> > > (NOTE: > >> > > >> > mediaproxy's running on the same machine as SER): > >> > > >> > [Dispatcher] > >> > start > >> > > >> > > = yes > >> > > >> > socket = /var/run/proxydispatcher.sock > >> > listen = <my IP address> > >> > group > >> > > >> > > = wheel > >> > > >> > defaultProxy = /var/run/mediaproxy.sock > >> > > >> > [MediaProxy] > >> > start = > >> > > >> > > yes > >> > > >> > socket = /var/run/mediaproxy.sock > >> > group = wheel > >> > listen = <my IP > >> > > >> > > address> > >> > > >> > allow = <my IP address>, 127.0.0.1 > >> > proxyIP = <my IP > >> > > >> > > address> > >> > > >> > portRange = 60000:65000 > >> > TOS = 0xb8 > >> > idleTimeout = 60 > >> > holdTimeout = > >> > > >> > > 3600 > >> > > >> > forceClose = 10800 > >> > > >> > [Accounting] > >> > dbaccounting = off > >> > > >> > //<my IP address> > >> > > >> > > is IP of SER/mediaproxy machine > >> > > >> > // the rest is irrelevant > >> > > >> > Please, also note > >> > > >> > > that I dont have a DNS SRV entry for media proxy. > >> > > >> > Could that cause the > >> > > >> > > problem? > >> > > >> > One way or another, I had to downgrade back to 1.4.2. Any > >> > > >> > > suggestions? > >> > > >> > Thanx in advance. > >> > > >> > Andrey. > >> > > >> > _______________________________________________ > >> > 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 1

[Serusers] sipsak says: error: cannot handle this redirect
by jp＠speakplease.com 20 Jun '06

20 Jun '06

I'm quite new with this whole SIP thing (surprise surprise) I'm trying to learn and build a system but i can't seem to get even the most simple redirects to work. I did get it to work earlier, but then it stopped working and now i can't get it to work again. any help please? since i'm not that hack with the linux either i reinstalled it in case i had made stupid mistakes (couldn't get phpmyadmin to work at that point but that's another story...) when i do this: sipsak -vv -s sip:7770088@192.168.1.102 sipsak says: message received: ** received redirect error: cannot handle this redirect: SIP/2.0 300 Redirect Via: SIP/2.0/UDP 192.168.1.111:1235;branch=z9hG4bK.457b3839;rport=1236;alias From: sip:sipsak@192.168.1.111:1235;tag=4b93b8d3 To: sip:7770088@192.168.1.102;tag=b27e1a1d33761e85846fc98f5f3a7e58.dd84 Call-ID: 1267972307(a)192.168.1.111 CSeq: 1 OPTIONS Contact: sip:7770088@sip.varphonex.com:5060 Server: Sip EXpress router (0.9.6 (i386/linux)) Content-Length: 0 Warning: 392 192.168.1.102:5060 "Noisy feedback tells: pid=30758 req_src_ip=192.168.1.111 req_src_port=1236 in_uri=sip:7770088@192.168.1.102 out_uri=sip:7770088@sip.varphonex.com:5060 via_cnt==1" the redirect i'm using is the redirect example from ser documentation (changed the rewrite uri to 7770088@sip.varphonex.com:5060) I'm trying to get my voip phone to connect to varphonex through ser. thanks in advance! -JP

2 1

[Serusers] Radius acc ERROR
by Kostas Marneris 20 Jun '06

20 Jun '06

Hi all, I've already successfully configured SER for syslog accounting, but now I'm trying to turn it to RADIUS accounting. - I changed the modules/acc/Makefile file (uncomment the following lines) : DEFS+=-DRAD_ACC include ../../Makefile.radius - re-compile & install (make & copy the new acc.so to the lib path). - ser.cfg : loadmodule "/opt/ser-0.9.6/lib/ser/modules/acc.so" modparam("acc", "radius_config", "/opt/radiusclient-ng/etc/radiusclient-ng/radiusclient.conf") When I try to restart SER (serctl restart) I get the following error mesg : Jun 20 14:45:12 xxx ser[19502]: ERROR: acc: can't get code for the Failed attribute value Jun 20 14:45:12 xxx ser[19502]: init_mod(): Error while initializing module acc any hint ? error on radiusclient conf / SER modparam conf ? thank you

1 0

[Serusers] checking source ip and dest ip
by İlker Aktuna (Koç.net) 20 Jun '06

20 Jun '06

Hi, I need to check source ip of a SIP message and also destination IP to which the message will be sent. i.e. I will use mediaproxy only if the one of the ip addresses match 10.0.0.0 / 255.0.0.0 is it possible ? Thanks, ilker <http://387555.sigclick.mailinfo.com/sigclick/0B080506/07014D00/08080B4F/001…> _____________________________________________________________________________________________________________________________________________ Bu e-posta mesaji kisiye ozel olup, gizli bilgiler iceriyor olabilir. Eger bu e-posta mesaji size yanlislikla ulasmissa, icerigini hic bir sekilde kullanmayiniz ve ekli dosyalari acmayiniz. Bu durumda lutfen e-posta mesajini kullaniciya hemen geri gonderiniz ve tum kopyalarini mesaj kutunuzdan siliniz. Bu e-posta mesaji, hic bir sekilde, herhangi bir amac icin cogaltilamaz, yayinlanamaz ve para karsiligi satilamaz. Bu e-posta mesaji viruslere karsi anti-virus sistemleri tarafindan taranmistir. Ancak yollayici, bu e-posta mesajinin - virus koruma sistemleri ile kontrol ediliyor olsa bile - virus icermedigini garanti etmez ve meydana gelebilecek zararlardan dogacak hicbir sorumlulugu kabul etmez. This message is intended solely for the use of the individual or entity to whom it is addressed , and may contain confidential information. If you are not the intended recipient of this message or you receive this mail in error, you should refrain from making any use of the contents and from opening any attachment. In that case, please notify the sender immediately and return the message to the sender, then, delete and destroy all copies. This e-mail message, can not be copied, published or sold for any reason. This e-mail message has been swept by anti-virus systems for the presence of computer viruses. In doing so, however, sender cannot warrant that virus or other forms of data corruption may not be present and do not take any responsibility in any occurrence. _____________________________________________________________________________________________________________________________________________

2 1

[Serusers] PSTN connectivity
by ravi reddy 20 Jun '06

20 Jun '06

Hi SER users , At present iam using SER-0.9.6 as proxy,registrar ,and the sip to sip calls i tested are o.k and is perfectly going and now when i tried to connect to PSTN it showing 500 internal server error i dont understand whether it is the mistake of cisco sip gateway or SER 's here is the sip messages which i get when i tried to call SIP to PSTN . I HAD GIVEN SIP TEST CLIENTS USER ID AS 32331000 AND THE LOCAL PSTN NO. ARE LIKE THIS :eg: 22458792 My Domain/Realm=81.21.33.35 and iam using onsip ser.cfg as the ser config file if (uri=~"^sip:011[0-9]*@") { # International PSTN route(4); route(5); break; }; if (!lookup("location")) { if (uri=~"^sip:[0-9]{8}@") { # Domestic PSTN route(4); route(5); break; }; and the pstn connectivity lines are like this: and here are the sip messages when i tried to call pstn number my pstn gateway which iam testing now is 81.21.38.21 # U 81.21.34.34:5068 -> 81.21.33.35:5060 INVITE sip:22485400@81.21.33.35 SIP/2.0. Via: SIP/2.0/UDP 192.168.0.74:5068;branch=z9hG4bKccadffff3fd60000. From: "ravi" <sip:32331001@81.21.33.35>;tag=26b000000d350000. To: <sip:22485400@81.21.33.35>. Contact: <sip:32331001@192.168.0.74:5068>. Supported: replaces. Call-ID: 9ad9ffff49050000(a)192.168.0.74. CSeq: 46532 INVITE. User-Agent: Grandstream HT496 1.0.2.16. Max-Forwards: 70. Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE. Content-Type: application/sdp. Content-Length: 305. . v=0. o=32331001 8000 8000 IN IP4 192.168.0.74. s=SIP Call. c=IN IP4 192.168.0.74. t=0 0. m=audio 8000 RTP/AVP 8 0 18 4 2 99. a=sendrecv. a=rtpmap:8 PCMA/8000. a=rtpmap:0 PCMU/8000. a=rtpmap:18 G729/8000. a=rtpmap:4 G723/8000. a=rtpmap:2 G726-32/8000. a=rtpmap:99 iLBC/8000. a=fmtp:99 mode=20. a=ptime:20. # U 81.21.33.35:5060 -> 81.21.34.34:5068 SIP/2.0 407 Proxy Authentication Required. Via: SIP/2.0/UDP 192.168.0.74:5068;branch=z9hG4bKccadffff3fd60000;received= 81.21.34.34. From: "ravi" <sip:32331001@81.21.33.35>;tag=26b000000d350000. To: <sip:22485400@81.21.33.35>;tag=74961b5b71b6ddce908b9155b956083f.c903. Call-ID: 9ad9ffff49050000(a)192.168.0.74. CSeq: 46532 INVITE. Proxy-Authenticate: Digest realm="81.21.33.35", nonce="4497c732a5a6f0ff3fb62bd9ac4561a02e4975c9". Content-Length: 0. Warning: 392 81.21.33.35:5060 "Noisy feedback tells: pid=27570 req_src_ip= 81.21.34.34 req_src_port=5068 in_uri=sip:22485400@81.21.33.35 out_uri= sip:22485400@81.21.33.35 via_cnt==1". . # U 81.21.34.34:5068 -> 81.21.33.35:5060 ACK sip:22485400@81.21.33.35 SIP/2.0. Via: SIP/2.0/UDP 192.168.0.74:5068;branch=z9hG4bKccadffff3fd60000. From: "ravi" <sip:32331001@81.21.33.35>;tag=26b000000d350000. To: <sip:22485400@81.21.33.35>;tag=74961b5b71b6ddce908b9155b956083f.c903. Contact: <sip:32331001@192.168.0.74:5068>. Call-ID: 9ad9ffff49050000(a)192.168.0.74. CSeq: 46532 ACK. User-Agent: Grandstream HT496 1.0.2.16. Max-Forwards: 70. Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE. Content-Length: 0. . # U 81.21.34.34:5068 -> 81.21.33.35:5060 INVITE sip:22485400@81.21.33.35 SIP/2.0. Via: SIP/2.0/UDP 192.168.0.74:5068;branch=z9hG4bK1be8ffffc8ecffff. From: "ravi" <sip:32331001@81.21.33.35>;tag=26b000000d350000. To: <sip:22485400@81.21.33.35>. Contact: <sip:32331001@192.168.0.74:5068>. Supported: replaces. Proxy-Authorization: Digest username="32331001", realm="81.21.33.35", algorithm=MD5, uri="sip:22485400@81.21.33.35", nonce="4497c732a5a6f0ff3fb62bd9ac4561a02e4975c9", response="af0c7b754d60bf28e493637995ac5675". Call-ID: 9ad9ffff49050000(a)192.168.0.74. CSeq: 46533 INVITE. User-Agent: Grandstream HT496 1.0.2.16. Max-Forwards: 70. Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE. Content-Type: application/sdp. Content-Length: 305. . v=0. o=32331001 8000 8001 IN IP4 192.168.0.74. s=SIP Call. c=IN IP4 192.168.0.74. t=0 0. m=audio 8000 RTP/AVP 8 0 18 4 2 99. a=sendrecv. a=rtpmap:8 PCMA/8000. a=rtpmap:0 PCMU/8000. a=rtpmap:18 G729/8000. a=rtpmap:4 G723/8000. a=rtpmap:2 G726-32/8000. a=rtpmap:99 iLBC/8000. a=fmtp:99 mode=20. a=ptime:20. # U 81.21.34.6:5062 -> 81.21.33.35:5060 .... # U 81.21.33.35:5060 -> 81.21.34.34:5068 SIP/2.0 100 trying -- your call is important to us. Via: SIP/2.0/UDP 192.168.0.74:5068 ;branch=z9hG4bK1be8ffffc8ecffff;rport=5068;received=81.21.34.34. From: "ravi" <sip:32331001@81.21.33.35>;tag=26b000000d350000. To: <sip:22485400@81.21.33.35>. Call-ID: 9ad9ffff49050000(a)192.168.0.74. CSeq: 46533 INVITE. Content-Length: 0. Warning: 392 81.21.33.35:5060 "Noisy feedback tells: pid=27568 req_src_ip= 81.21.34.34 req_src_port=5068 in_uri=sip:22485400@81.21.33.35 out_uri= sip:22485400@81.21.38.21 via_cnt==1". . # U 81.21.33.35:5060 -> 81.21.38.21:5060 INVITE sip:22485400@81.21.38.21 SIP/2.0. Record-Route: <sip:22485400@81.21.33.35 :5060;nat=yes;ftag=26b000000d350000;lr=on>. Via: SIP/2.0/UDP 81.21.33.35;branch=z9hG4bK7de4.ed7d9ff3.0. Via: SIP/2.0/UDP 192.168.0.74:5068;rport=5068;received=81.21.34.34 ;branch=z9hG4bK1be8ffffc8ecffff. From: "ravi" <sip:32331001@81.21.33.35>;tag=26b000000d350000. To: <sip:22485400@81.21.33.35>. Contact: <sip:32331001@81.21.34.34:5068>. Supported: replaces. Call-ID: 9ad9ffff49050000(a)192.168.0.74. CSeq: 46533 INVITE. User-Agent: Grandstream HT496 1.0.2.16. Max-Forwards: 16. Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE. Content-Type: application/sdp. Content-Length: 321. . v=0. o=32331001 8000 8001 IN IP4 192.168.0.74. s=SIP Call. c=IN IP4 81.21.33.3581.21.33.35. t=0 0. m=audio 3505035050 RTP/AVP 8 0 18 4 2 99. a=sendrecv. a=rtpmap:8 PCMA/8000. a=rtpmap:0 PCMU/8000. a=rtpmap:18 G729/8000. a=rtpmap:4 G723/8000. a=rtpmap:2 G726-32/8000. a=rtpmap:99 iLBC/8000. a=fmtp:99 mode=20. a=ptime:20. # U 81.21.38.21:5060 -> 81.21.33.35:5060 SIP/2.0 100 Trying. Via: SIP/2.0/UDP 81.21.33.35;branch=z9hG4bK7de4.ed7d9ff3.0,SIP/2.0/UDP 192.168.0.74:5068;rport=5068;received=81.21.34.34 ;branch=z9hG4bK1be8ffffc8ecffff. From: "ravi" <sip:32331001@81.21.33.35>;tag=26b000000d350000. To: <sip:22485400@81.21.33.35>;tag=7D687D1C-202E. Date: Tue, 20 Jun 2006 09:56:36 GMT. Call-ID: 9ad9ffff49050000(a)192.168.0.74. Server: Cisco-SIPGateway/IOS-12.x. CSeq: 46533 INVITE. Allow-Events: telephone-event. Content-Length: 0. . # U 81.21.38.21:5060 -> 81.21.33.35:5060 SIP/2.0 500 Internal Server Error. Via: SIP/2.0/UDP 81.21.33.35;branch=z9hG4bK7de4.ed7d9ff3.0,SIP/2.0/UDP 192.168.0.74:5068;rport=5068;received=81.21.34.34 ;branch=z9hG4bK1be8ffffc8ecffff. From: "ravi" <sip:32331001@81.21.33.35>;tag=26b000000d350000. To: <sip:22485400@81.21.33.35>;tag=7D687D1C-202E. Date: Tue, 20 Jun 2006 09:56:36 GMT. Call-ID: 9ad9ffff49050000(a)192.168.0.74. Server: Cisco-SIPGateway/IOS-12.x. CSeq: 46533 INVITE. Allow-Events: telephone-event. Content-Length: 0. . # U 81.21.33.35:5060 -> 81.21.38.21:5060 ACK sip:22485400@81.21.38.21 SIP/2.0. Via: SIP/2.0/UDP 81.21.33.35;branch=z9hG4bK7de4.ed7d9ff3.0. From: "ravi" <sip:32331001@81.21.33.35>;tag=26b000000d350000. Call-ID: 9ad9ffff49050000(a)192.168.0.74. To: <sip:22485400@81.21.33.35>;tag=7D687D1C-202E. CSeq: 46533 ACK. Content-Length: 0. . # U 81.21.33.35:5060 -> 81.21.34.34:5068 SIP/2.0 500 Internal Server Error. Via: SIP/2.0/UDP 192.168.0.74:5068;rport=5068;received=81.21.34.34 ;branch=z9hG4bK1be8ffffc8ecffff. From: "ravi" <sip:32331001@81.21.33.35>;tag=26b000000d350000. To: <sip:22485400@81.21.33.35>;tag=7D687D1C-202E. Date: Tue, 20 Jun 2006 09:56:36 GMT. Call-ID: 9ad9ffff49050000(a)192.168.0.74. Server: Cisco-SIPGateway/IOS-12.x. CSeq: 46533 INVITE. Allow-Events: telephone-event. Content-Length: 0. . # U 81.21.34.34:5068 -> 81.21.33.35:5060 ACK sip:22485400@81.21.33.35 SIP/2.0. Via: SIP/2.0/UDP 192.168.0.74:5068;branch=z9hG4bK1be8ffffc8ecffff. From: "ravi" <sip:32331001@81.21.33.35>;tag=26b000000d350000. To: <sip:22485400@81.21.33.35>;tag=7D687D1C-202E. Contact: <sip:32331001@192.168.0.74:5068>. Proxy-Authorization: Digest username="32331001", realm="81.21.33.35", algorithm=MD5, uri="sip:22485400@81.21.33.35", nonce="4497c732a5a6f0ff3fb62bd9ac4561a02e4975c9", response="e09e9b23688cc3847829da66fe1fc145". Call-ID: 9ad9ffff49050000(a)192.168.0.74. CSeq: 46533 ACK. User-Agent: Grandstream HT496 1.0.2.16. Max-Forwards: 70. Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE. Content-Length: 0. . # U 81.21.33.35:5060 -> 81.21.34.34:5068 SIP/2.0 500 Internal Server Error. Via: SIP/2.0/UDP 192.168.0.74:5068;rport=5068;received=81.21.34.34 ;branch=z9hG4bK1be8ffffc8ecffff. From: "ravi" <sip:32331001@81.21.33.35>;tag=26b000000d350000. To: <sip:22485400@81.21.33.35>;tag=7D687D1C-202E. Date: Tue, 20 Jun 2006 09:56:36 GMT. Call-ID: 9ad9ffff49050000(a)192.168.0.74. Server: Cisco-SIPGateway/IOS-12.x. CSeq: 46533 INVITE. Allow-Events: telephone-event. Content-Length: 0. . # U 81.21.33.35:5060 -> 81.21.34.34:5068 SIP/2.0 500 Internal Server Error. Via: SIP/2.0/UDP 192.168.0.74:5068;rport=5068;received=81.21.34.34 ;branch=z9hG4bK1be8ffffc8ecffff. From: "ravi" <sip:32331001@81.21.33.35>;tag=26b000000d350000. To: <sip:22485400@81.21.33.35>;tag=7D687D1C-202E. Date: Tue, 20 Jun 2006 09:56:36 GMT. Call-ID: 9ad9ffff49050000(a)192.168.0.74. Server: Cisco-SIPGateway/IOS-12.x. CSeq: 46533 INVITE. Allow-Events: telephone-event. Content-Length: 0. I hope you guys will help in this issue Thanks in Advance. Regards' Ravi

1 0

[Serusers] Compiling problem
by Alois Schafferhofer 20 Jun '06

20 Jun '06

Hi. I want to compile SER 0.9.5. Therefore, I need the packages -- libmysqlclient-dev and -- libxml2-dev The problem is, that I can't find these packages for Suse 9.3. Can someone give me an address where I can download these packages? Regards, Alois

2 1

[Users] Response to Nat problem
by Cseke Tamas 20 Jun '06

20 Jun '06

Hello! We've a problem with a provisional response. The invite is sent through NAT , and the response will be sent to incorrect port. The invite is sent from 193.77.152.140:53559 to ser, (it is a natted firewall. It not insert Via header, don't understand sip) The topmost via is: Via: SIP/2.0/UDP 10.10.1.2:5080;branch=z9hG4bK-a47f2525b20ab1a953a7c74174551819;received=193.77.152.140 The server recognize, that it is received from 193.77.152.140, but the reply will be sent to 193.77.152.140:5080 according to the RFC 3261 the port used in the response is , what present in the via header. How can i force that the response will be sent to the source port (52559)? Thanks, Tamas

2 1

RE: [Serusers] Mediaproxy problem - how to disable P2P rtp connection
by İlker Aktuna (Koç.net) 20 Jun '06

20 Jun '06

Hi, I have found the problem. (in fact it was not a problem) The client was using the alternate media connection information which is peer-2-peer. How can I prevent P2P connection ? I need to remove "media attribute (a): alt:1" from the SIP INVITE messages, but how ? Thanks, ilker ________________________________ From: serusers-bounces(a)lists.iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of İlker Aktuna (Koç.net) Sent: Monday, June 19, 2006 6:13 PM To: serusers(a)iptel.org Subject: RE: [Serusers] Mediaproxy problem Hi, Please help me with the following problem. Do I need SRV dns records even if I don't use load balancing ? Thanks, ilker ________________________________ From: serusers-bounces(a)lists.iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of İlker Aktuna (Koç.net) Sent: Monday, June 19, 2006 4:31 PM To: serusers(a)iptel.org Subject: [Serusers] Mediaproxy problem Hi, I just installed mediaproxy 1.7.2 At this time, I am not interested in using more than one rtp server for loadbalancing. That's why I didn't add any DNS SRV records to my DNS. Would that be a problem ? If it's not a problem, then what's the problem described below? When I call from one client to the other one, I see that the SDP messages are modified as required (media connection infromation is changed to the media proxy server) But after first few RTP packets all RTP is routed to the alternate connection which is direct connection to the client (peer-2-peer) Thanks for your comments, ilker C "-//W3C//DTD HTML 4.0 Transitional//EN"> Hi, Please help me with the following problem. Do I need SRV dns records even if I don't use load balancing ? Thanks, ilker ________________________________ From: serusers-bounces(a)lists.iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of İlker Aktuna (Koç.net) Sent: Monday, June 19, 2006 4:31 PM To: serusers(a)iptel.org Subject: [Serusers] Mediaproxy problem Hi, I just installed mediaproxy 1.7.2 At this time, I am not interested in using more than one rtp server for loadbalancing. That's why I didn't add any DNS SRV records to my DNS. Would that be a problem ? If it's not a problem, then what's the problem described below? When I call from one client to the other one, I see that the SDP messages are modified as required (media connection infromation is changed to the media proxy server) But after first few RTP packets all RTP is routed to the alternate connection which is direct connection to the client (peer-2-peer) Thanks for your comments, ilker C "-//W3C//DTD HTML 4.0 Transitional//EN"> Hi, I have found the problem. (in fact it was not a problem) The client was using the alternate media connection information which is peer-2-peer. How can I prevent P2P connection ? I need to remove "media attribute (a): alt:1" from the SIP INVITE messages, but how ? Thanks, ilker ________________________________ From: serusers-bounces(a)lists.iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of İlker Aktuna (Koç.net) Sent: Monday, June 19, 2006 6:13 PM To: serusers(a)iptel.org Subject: RE: [Serusers] Mediaproxy problem Hi, Please help me with the following problem. Do I need SRV dns records even if I don't use load balancing ? Thanks, ilker ________________________________ From: serusers-bounces(a)lists.iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of İlker Aktuna (Koç.net) Sent: Monday, June 19, 2006 4:31 PM To: serusers(a)iptel.org Subject: [Serusers] Mediaproxy problem Hi, I just installed mediaproxy 1.7.2 At this time, I am not interested in using more than one rtp server for loadbalancing. That's why I didn't add any DNS SRV records to my DNS. Would that be a problem ? If it's not a problem, then what's the problem described below? When I call from one client to the other one, I see that the SDP messages are modified as required (media connection infromation is changed to the media proxy server) But after first few RTP packets all RTP is routed to the alternate connection which is direct connection to the client (peer-2-peer) Thanks for your comments, ilker C "-//W3C//DTD HTML 4.0 Transitional//EN"> Hi, Please help me with the following problem. Do I need SRV dns records even if I don't use load balancing ? Thanks, ilker ________________________________ From: serusers-bounces(a)lists.iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of İlker Aktuna (Koç.net) Sent: Monday, June 19, 2006 4:31 PM To: serusers(a)iptel.org Subject: [Serusers] Mediaproxy problem Hi, I just installed mediaproxy 1.7.2 At this time, I am not interested in using more than one rtp server for loadbalancing. That's why I didn't add any DNS SRV records to my DNS. Would that be a problem ? If it's not a problem, then what's the problem described below? When I call from one client to the other one, I see that the SDP messages are modified as required (media connection infromation is changed to the media proxy server) But after first few RTP packets all RTP is routed to the alternate connection which is direct connection to the client (peer-2-peer) Thanks for your comments, ilker <http://387555.sigclick.mailinfo.com/sigclick/03090E00/07074E03/00090C49/002…> _____________________________________________________________________________________________________________________________________________ Bu e-posta mesaji kisiye ozel olup, gizli bilgiler iceriyor olabilir. Eger bu e-posta mesaji size yanlislikla ulasmissa, icerigini hic bir sekilde kullanmayiniz ve ekli dosyalari acmayiniz. Bu durumda lutfen e-posta mesajini kullaniciya hemen geri gonderiniz ve tum kopyalarini mesaj kutunuzdan siliniz. Bu e-posta mesaji, hic bir sekilde, herhangi bir amac icin cogaltilamaz, yayinlanamaz ve para karsiligi satilamaz. Bu e-posta mesaji viruslere karsi anti-virus sistemleri tarafindan taranmistir. Ancak yollayici, bu e-posta mesajinin - virus koruma sistemleri ile kontrol ediliyor olsa bile - virus icermedigini garanti etmez ve meydana gelebilecek zararlardan dogacak hicbir sorumlulugu kabul etmez. This message is intended solely for the use of the individual or entity to whom it is addressed , and may contain confidential information. If you are not the intended recipient of this message or you receive this mail in error, you should refrain from making any use of the contents and from opening any attachment. In that case, please notify the sender immediately and return the message to the sender, then, delete and destroy all copies. This e-mail message, can not be copied, published or sold for any reason. This e-mail message has been swept by anti-virus systems for the presence of computer viruses. In doing so, however, sender cannot warrant that virus or other forms of data corruption may not be present and do not take any responsibility in any occurrence. _____________________________________________________________________________________________________________________________________________

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