sr-users October 2005

sr-users@lists.kamailio.org

214 participants
457 discussions

by Iqbal

Hi Anyone know howto /dev/null inbound requests, from users. Reason for this is that I have a few random setups, which I no longer support, and the user has xlite and is just sending through REGISTER requests, I'd much rather they just get dumped, prefer to do it within ser, rather than some iptables/fw block. I guess I could have some blacklist table, and if From= blacklist then break...suggestions. Iqbal

18 years, 5 months

[Serusers] UA's under same NAT

by deviator

Hello! i have 0.9.5 openser + mediaproxy 1.4.2 + serweb + mysql and so on, all works fine. private and public ua's works, no problems. But i have one question. Is it possible to send rtp traffic directly to each other if a callee and a caller are under same nat ? not through mediaproxy. p.s. huge thanks to the developers of ser/openser. Nice software! RESPECT!

18 years, 5 months

[Users] MySQL 2-way replication with SER

by Daryl Sanders

Is anyone using MySQL replication 2-way replication (dual-master, multi-master) in your SER/OpenSER setup. How well does it work? Any pitfalls? - Daryl

18 years, 5 months

Re: [Users] Detecting runaway calls

by Daryl Sanders

Thanks for the info guys! It sounds like I need to do a little reading up on cseq to determine if this will even work, or find a PSTN gateway provider that supports Session-Timers. - Daryl On 10/27/05, Bogdan-Andrei Iancu <bogdan(a)voice-system.ro> wrote: > by sending re-INVITEs from the middle of the path you will increase the > cseq number differently on each side...so you will need to synchronize > the cseq value when some in-the-dialog requests are passing through your > proxy....and that's quite complicated.... > > regards, > bogdan > > Daryl Sanders wrote: > > >Would it be possible to fake a REINVITE then check the response to > >determine if a call is still in session? Just brainstorming... > > > >- Daryl > > > > > >

18 years, 5 months

[Users] lcr module

by Richard Z

Hi, I am trying to develop some features which requires to call load_gws and next_gw in a failure route. For example, in normal routing block, it forwards the call to a subscriber's ip phone locations. If nobody answer, it tries to call a pstn number. In the failure route, i called load_gws and next_gw. However it generates an error "next_gw(): No ruri_user AVP". Looking at the code, there seems to be an assumption that first time call to next_gw always happens in the normal routing block. But in my case, it calls next_gw first time in a failure route. I even tried to manually add the new uri's username to avp i:1402. It still won't work. Is it possible to call next_gw first time in a failure route? Thanks, Richard

18 years, 5 months

[Users] Call not torn down when CANCEL sent before INVITE message is finished being processed

by Tavis P

With the latest CVS build of OSER, when an INVITE is sent followed by a CANCEL, before OSER has finished processing the initial INVITE, the outbound call is not torn down, and SER routes the CANCEL message to itself. Below is an ngrep trace of the exchange. I have a development cluster of mediaproxy servers setup and one of them was taken offline but left in the loop which increased the time it took for a message to be processed which is how i came across this situation (it took some seconds before the INVITE was able to be transmitted to the nexthop_proxy) -- # U 2005/10/04 01:44:43.134010 SIP_UAC:5070 -> OSER_PROXY:15061 INVITE sip:6046946333@OSER_PROXY:15061 SIP/2.0. Via: SIP/2.0/UDP 192.168.99.66:5070;branch=z9hG4bK-34d67b8f. From: tavis <sip:200110005334@OSER_PROXY:15061>;tag=6e3e1f53c3f352efo0. To: <sip:6046946333@OSER_PROXY:15061>. Call-ID: ec5b9223-f98ffe5f(a)192.168.99.66. CSeq: 101 INVITE. Max-Forwards: 70. Contact: tavis <sip:200110005334@192.168.99.66:5070>. Expires: 240. User-Agent: Sipura/SPA3000-3.1.5(GWb). Content-Length: 287. Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER. Supported: x-sipura. Content-Type: application/sdp. . v=0. o=- 25915303 25915303 IN IP4 192.168.99.66. s=-. c=IN IP4 192.168.99.66. t=0 0. m=audio 16410 RTP/AVP 18 0 4 8 101. a=rtpmap:18 G729a/8000. a=rtpmap:0 PCMU/8000. a=rtpmap:4 G723/8000. a=rtpmap:8 PCMA/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-15. a=ptime:20. a=sendrecv. # U 2005/10/04 01:44:43.135736 OSER_PROXY:15061 -> SIP_UAC:5070 SIP/2.0 407 Proxy Authentication Required. Via: SIP/2.0/UDP 192.168.99.66:5070;branch=z9hG4bK-34d67b8f;rport=5070;received=SIP_UAC. From: tavis <sip:200110005334@OSER_PROXY:15061>;tag=6e3e1f53c3f352efo0. To: <sip:6046946333@OSER_PROXY:15061>;tag=688bd636d693eb2ab143ccbaf0db2c7a.8474. Call-ID: ec5b9223-f98ffe5f(a)192.168.99.66. CSeq: 101 INVITE. Proxy-Authenticate: Digest realm="hq.galnet.ca", nonce="4341dfb7e0cfaa398a6f425c02262325f943b20e", qop="auth". Content-Length: 0. . # U 2005/10/04 01:44:43.147960 SIP_UAC:5070 -> OSER_PROXY:15061 ACK sip:6046946333@OSER_PROXY:15061 SIP/2.0. Via: SIP/2.0/UDP 192.168.99.66:5070;branch=z9hG4bK-34d67b8f. From: tavis <sip:200110005334@OSER_PROXY:15061>;tag=6e3e1f53c3f352efo0. To: <sip:6046946333@OSER_PROXY:15061>;tag=688bd636d693eb2ab143ccbaf0db2c7a.8474. Call-ID: ec5b9223-f98ffe5f(a)192.168.99.66. CSeq: 101 ACK. Max-Forwards: 70. Contact: tavis <sip:200110005334@192.168.99.66:5070>. User-Agent: Sipura/SPA3000-3.1.5(GWb). Content-Length: 0. . # U 2005/10/04 01:44:43.154728 SIP_UAC:5070 -> OSER_PROXY:15061 INVITE sip:6046946333@OSER_PROXY:15061 SIP/2.0. Via: SIP/2.0/UDP 192.168.99.66:5070;branch=z9hG4bK-249e2787. From: tavis <sip:200110005334@OSER_PROXY:15061>;tag=6e3e1f53c3f352efo0. To: <sip:6046946333@OSER_PROXY:15061>. Call-ID: ec5b9223-f98ffe5f(a)192.168.99.66. CSeq: 102 INVITE. Max-Forwards: 70. Proxy-Authorization: Digest username="200110005334",realm="hq.galnet.ca",nonce="4341dfb7e0cfaa398a6f425c02262325f943b20e",uri="sip:6046946333@OSER_PROXY:15061",algorithm=MD5,response="6867ef34181ba7cedbcbf8dd869f53ab",qop=auth,nc=00000001,cnonce="750e43e5". Contact: tavis <sip:200110005334@192.168.99.66:5070>. Expires: 240. User-Agent: Sipura/SPA3000-3.1.5(GWb). Content-Length: 287. Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER. Supported: x-sipura. Content-Type: application/sdp. . v=0. o=- 25915303 25915303 IN IP4 192.168.99.66. s=-. c=IN IP4 192.168.99.66. t=0 0. m=audio 16410 RTP/AVP 18 0 4 8 101. a=rtpmap:18 G729a/8000. a=rtpmap:0 PCMU/8000. a=rtpmap:4 G723/8000. a=rtpmap:8 PCMA/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-15. a=ptime:20. a=sendrecv. # U 2005/10/04 01:44:43.648366 SIP_UAC:5070 -> OSER_PROXY:15061 INVITE sip:6046946333@OSER_PROXY:15061 SIP/2.0. Via: SIP/2.0/UDP 192.168.99.66:5070;branch=z9hG4bK-249e2787. From: tavis <sip:200110005334@OSER_PROXY:15061>;tag=6e3e1f53c3f352efo0. To: <sip:6046946333@OSER_PROXY:15061>. Call-ID: ec5b9223-f98ffe5f(a)192.168.99.66. CSeq: 102 INVITE. Max-Forwards: 70. Proxy-Authorization: Digest username="200110005334",realm="hq.galnet.ca",nonce="4341dfb7e0cfaa398a6f425c02262325f943b20e",uri="sip:6046946333@OSER_PROXY:15061",algorithm=MD5,response="6867ef34181ba7cedbcbf8dd869f53ab",qop=auth,nc=00000001,cnonce="750e43e5". Contact: tavis <sip:200110005334@192.168.99.66:5070>. Expires: 240. User-Agent: Sipura/SPA3000-3.1.5(GWb). Content-Length: 287. Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER. Supported: x-sipura. Content-Type: application/sdp. . v=0. o=- 25915303 25915303 IN IP4 192.168.99.66. s=-. c=IN IP4 192.168.99.66. t=0 0. m=audio 16410 RTP/AVP 18 0 4 8 101. a=rtpmap:18 G729a/8000. a=rtpmap:0 PCMU/8000. a=rtpmap:4 G723/8000. a=rtpmap:8 PCMA/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-15. a=ptime:20. a=sendrecv. # U 2005/10/04 01:44:44.155113 SIP_UAC:5070 -> OSER_PROXY:15061 CANCEL sip:6046946333@OSER_PROXY:15061 SIP/2.0. Via: SIP/2.0/UDP 192.168.99.66:5070;branch=z9hG4bK-249e2787. From: tavis <sip:200110005334@OSER_PROXY:15061>;tag=6e3e1f53c3f352efo0. To: <sip:6046946333@OSER_PROXY:15061>. Call-ID: ec5b9223-f98ffe5f(a)192.168.99.66. CSeq: 102 CANCEL. Max-Forwards: 70. Proxy-Authorization: Digest username="200110005334",realm="hq.galnet.ca",nonce="4341dfb7e0cfaa398a6f425c02262325f943b20e",uri="sip:6046946333@OSER_PROXY:15061",algorithm=MD5,response="512097281b4fba990adf2cc6c273f033",qop=auth,nc=00000002,cnonce="750e43e5". User-Agent: Sipura/SPA3000-3.1.5(GWb). Content-Length: 0. . # U 2005/10/04 01:44:44.285994 OSER_PROXY:15061 -> SIP_UAC:5070 SIP/2.0 483 Too many hops. Via: SIP/2.0/UDP 192.168.99.66:5070;rport=5070;received=SIP_UAC;branch=z9hG4bK-249e2787. From: tavis <sip:200110005334@OSER_PROXY:15061>;tag=6e3e1f53c3f352efo0. To: <sip:6046946333@OSER_PROXY:15061>;tag=688bd636d693eb2ab143ccbaf0db2c7a.32f9. Call-ID: ec5b9223-f98ffe5f(a)192.168.99.66. CSeq: 102 CANCEL. Content-Length: 0. . # U 2005/10/04 01:44:44.648305 SIP_UAC:5070 -> OSER_PROXY:15061 INVITE sip:6046946333@OSER_PROXY:15061 SIP/2.0. Via: SIP/2.0/UDP 192.168.99.66:5070;branch=z9hG4bK-249e2787. From: tavis <sip:200110005334@OSER_PROXY:15061>;tag=6e3e1f53c3f352efo0. To: <sip:6046946333@OSER_PROXY:15061>. Call-ID: ec5b9223-f98ffe5f(a)192.168.99.66. CSeq: 102 INVITE. Max-Forwards: 70. Proxy-Authorization: Digest username="200110005334",realm="hq.galnet.ca",nonce="4341dfb7e0cfaa398a6f425c02262325f943b20e",uri="sip:6046946333@OSER_PROXY:15061",algorithm=MD5,response="11a15f9ef4fdb1c9ab05566cad92d67e",qop=auth,nc=00000002,cnonce="750e43e5". Contact: tavis <sip:200110005334@192.168.99.66:5070>. Expires: 240. User-Agent: Sipura/SPA3000-3.1.5(GWb). Content-Length: 287. Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER. Supported: x-sipura. Content-Type: application/sdp. . v=0. o=- 25915303 25915303 IN IP4 192.168.99.66. s=-. c=IN IP4 192.168.99.66. t=0 0. m=audio 16410 RTP/AVP 18 0 4 8 101. a=rtpmap:18 G729a/8000. a=rtpmap:0 PCMU/8000. a=rtpmap:4 G723/8000. a=rtpmap:8 PCMA/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-15. a=ptime:20. a=sendrecv. # U 2005/10/04 01:44:44.688471 OSER_PROXY:15061 -> SIP_UAC:5070 SIP/2.0 100 trying -- your call is important to us. Via: SIP/2.0/UDP 192.168.99.66:5070;branch=z9hG4bK-249e2787;rport=5070;received=SIP_UAC. From: tavis <sip:200110005334@OSER_PROXY:15061>;tag=6e3e1f53c3f352efo0. To: <sip:6046946333@OSER_PROXY:15061>. Call-ID: ec5b9223-f98ffe5f(a)192.168.99.66. CSeq: 102 INVITE. Content-Length: 0. . # U 2005/10/04 01:44:44.689012 OSER_PROXY:15061 -> NEXTHOP_PROXY:5060 INVITE sip:16046946333@NEXTHOP_PROXY SIP/2.0. Record-Route: <sip:OSER_PROXY:15061;ftag=6e3e1f53c3f352efo0;lr=on>. Via: SIP/2.0/UDP OSER_PROXY:15061;branch=z9hG4bK11ea.6c311116.0. Via: SIP/2.0/UDP 192.168.99.66:5070;rport=5070;received=SIP_UAC;branch=z9hG4bK-249e2787. From: tavis <sip:200110005334@OSER_PROXY:15061>;tag=6e3e1f53c3f352efo0. To: <sip:6046946333@OSER_PROXY:15061>. Call-ID: ec5b9223-f98ffe5f(a)192.168.99.66. CSeq: 102 INVITE. Max-Forwards: 15. Contact: tavis <sip:200110005334@SIP_UAC:5070>. Expires: 240. User-Agent: Sipura/SPA3000-3.1.5(GWb). Content-Length: 288. Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER. Supported: x-sipura. Content-Type: application/sdp. . v=0. o=- 25915303 25915303 IN IP4 192.168.99.66. s=-. c=IN IP4 OSER_PROXY. t=0 0. m=audio 35328 RTP/AVP 18 0 4 8 101. a=rtpmap:18 G729a/8000. a=rtpmap:0 PCMU/8000. a=rtpmap:4 G723/8000. a=rtpmap:8 PCMA/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-15. a=ptime:20. a=sendrecv. # U 2005/10/04 01:44:45.396833 OSER_PROXY:15061 -> NEXTHOP_PROXY:5060 INVITE sip:16046946333@NEXTHOP_PROXY SIP/2.0. Record-Route: <sip:OSER_PROXY:15061;ftag=6e3e1f53c3f352efo0;lr=on>. Via: SIP/2.0/UDP OSER_PROXY:15061;branch=z9hG4bK11ea.6c311116.0. Via: SIP/2.0/UDP 192.168.99.66:5070;rport=5070;received=SIP_UAC;branch=z9hG4bK-249e2787. From: tavis <sip:200110005334@OSER_PROXY:15061>;tag=6e3e1f53c3f352efo0. To: <sip:6046946333@OSER_PROXY:15061>. Call-ID: ec5b9223-f98ffe5f(a)192.168.99.66. CSeq: 102 INVITE. Max-Forwards: 15. Contact: tavis <sip:200110005334@SIP_UAC:5070>. Expires: 240. User-Agent: Sipura/SPA3000-3.1.5(GWb). Content-Length: 288. Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER. Supported: x-sipura. Content-Type: application/sdp. . v=0. o=- 25915303 25915303 IN IP4 192.168.99.66. s=-. c=IN IP4 OSER_PROXY. t=0 0. m=audio 35328 RTP/AVP 18 0 4 8 101. a=rtpmap:18 G729a/8000. a=rtpmap:0 PCMU/8000. a=rtpmap:4 G723/8000. a=rtpmap:8 PCMA/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-15. a=ptime:20. a=sendrecv. # U 2005/10/04 01:44:46.090526 NEXTHOP_PROXY:5060 -> OSER_PROXY:15061 SIP/2.0 183 Inband Information. Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, REFER, NOTIFY, REGISTER. Via: SIP/2.0/UDP OSER_PROXY:15061;branch=z9hG4bK11ea.6c311116.0. Via: SIP/2.0/UDP 192.168.99.66:5070;rport=5070;received=SIP_UAC;branch=z9hG4bK-249e2787. Record-Route: <sip:OSER_PROXY:15061;ftag=6e3e1f53c3f352efo0;lr=on>. To: <sip:6046946333@OSER_PROXY:15061>;tag=40032033. From: tavis <sip:200110005334@OSER_PROXY:15061>;tag=6e3e1f53c3f352efo0. Call-ID: ec5b9223-f98ffe5f(a)192.168.99.66. X-SHOUT-Channel: INBOUND 1:15:21:1. CSeq: 102 INVITE. Contact: sip:anonymous@NEXTHOP_PROXY. User-Agent: SHOUT 3.3.1p3v71. Content-Type: application/sdp. Content-Length: 174. . v=0. o=- 0 0 IN IP4 NEXTHOP_PROXY. s=SIP call via SHOUT. c=IN IP4 NEXTHOP_PROXY. t=0 0. m=audio 19004 RTP/AVP 18 101. a=rtpmap:18 G729/8000. a=rtpmap:101 telephone-event/8000. # U 2005/10/04 01:44:46.104387 OSER_PROXY:15061 -> SIP_UAC:5070 SIP/2.0 183 Inband Information. Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, REFER, NOTIFY, REGISTER. Via: SIP/2.0/UDP 192.168.99.66:5070;rport=5070;received=SIP_UAC;branch=z9hG4bK-249e2787. Record-Route: <sip:OSER_PROXY:15061;ftag=6e3e1f53c3f352efo0;lr=on>. To: <sip:6046946333@OSER_PROXY:15061>;tag=40032033. From: tavis <sip:200110005334@OSER_PROXY:15061>;tag=6e3e1f53c3f352efo0. Call-ID: ec5b9223-f98ffe5f(a)192.168.99.66. X-SHOUT-Channel: INBOUND 1:15:21:1. CSeq: 102 INVITE. Contact: sip:anonymous@NEXTHOP_PROXY. User-Agent: SHOUT 3.3.1p3v71. Content-Type: application/sdp. Content-Length: 176. . v=0. o=- 0 0 IN IP4 NEXTHOP_PROXY. s=SIP call via SHOUT. c=IN IP4 OSER_PROXY. t=0 0. m=audio 35328 RTP/AVP 18 101. a=rtpmap:18 G729/8000. a=rtpmap:101 telephone-event/8000. # U 2005/10/04 01:44:46.190376 OSER_PROXY:15061 -> SIP_UAC:5070 SIP/2.0 183 Inband Information. Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, REFER, NOTIFY, REGISTER. Via: SIP/2.0/UDP 192.168.99.66:5070;rport=5070;received=SIP_UAC;branch=z9hG4bK-249e2787. Record-Route: <sip:OSER_PROXY:15061;ftag=6e3e1f53c3f352efo0;lr=on>. To: <sip:6046946333@OSER_PROXY:15061>;tag=40032033. From: tavis <sip:200110005334@OSER_PROXY:15061>;tag=6e3e1f53c3f352efo0. Call-ID: ec5b9223-f98ffe5f(a)192.168.99.66. X-SHOUT-Channel: INBOUND 1:15:21:1. CSeq: 102 INVITE. Contact: sip:anonymous@NEXTHOP_PROXY. User-Agent: SHOUT 3.3.1p3v71. Content-Type: application/sdp. Content-Length: 176. . v=0. o=- 0 0 IN IP4 NEXTHOP_PROXY. s=SIP call via SHOUT. c=IN IP4 OSER_PROXY. t=0 0. m=audio 35328 RTP/AVP 18 101. a=rtpmap:18 G729/8000. a=rtpmap:101 telephone-event/8000. ## U 2005/10/04 01:44:46.702880 OSER_PROXY:15061 -> SIP_UAC:5070 SIP/2.0 183 Inband Information. Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, REFER, NOTIFY, REGISTER. Via: SIP/2.0/UDP 192.168.99.66:5070;rport=5070;received=SIP_UAC;branch=z9hG4bK-249e2787. Record-Route: <sip:OSER_PROXY:15061;ftag=6e3e1f53c3f352efo0;lr=on>. To: <sip:6046946333@OSER_PROXY:15061>;tag=40032033. From: tavis <sip:200110005334@OSER_PROXY:15061>;tag=6e3e1f53c3f352efo0. Call-ID: ec5b9223-f98ffe5f(a)192.168.99.66. X-SHOUT-Channel: INBOUND 1:15:21:1. CSeq: 102 INVITE. Contact: sip:anonymous@NEXTHOP_PROXY. User-Agent: SHOUT 3.3.1p3v71. Content-Type: application/sdp. Content-Length: 176. . v=0. o=- 0 0 IN IP4 NEXTHOP_PROXY. s=SIP call via SHOUT. c=IN IP4 OSER_PROXY. t=0 0. m=audio 35328 RTP/AVP 18 101. a=rtpmap:18 G729/8000. a=rtpmap:101 telephone-event/8000.

18 years, 5 months

Re: [Users] Insert name into from header of SIP messages

by Brandon Price

Following that logic should I not be able to just replace the display and leave the uri as is with... uac_replace_from("$avp(s:cnam)",""); I have of coarse already trid that with no success. On Oct 28, 2005, at 3:38 PM, Norman Brandinger wrote: > If you break your callerid into 2 parts, you should be able to use > something like the following: > > AVP display: "John Doe" > AVP uri: "sip:18005551212@example.com" > > uac_replace_from("$avp(s:display)","$avp(s:uri)"); > > The above information has been documented at http://www.openser.org/ > docs/modules/1.0.x/uac.html > > Regards, > Norm > > Brandon Price wrote: > >> We are storing cnam (callerid name) values in a mysql database for >> use with openser. I have openser pulling the values from the >> database using avpops but I need to know how to insert the value >> into the from so that it will be passed to my sip user agents. >> Related code posed below >> >> modparam >> ("avpops","db_scheme","cnam_scheme:username_col=phonenumber;table=cna >> m_cache;value_col=cnam;value_type=string") >> modparam("avpops", "avp_aliases", "cnam=s:cnam") >> >> avp_db_load("$from/cnam_scheme","cnam/$cnam_scheme"); #sample >> query -- select cnam from cnam_cache where phonenumber='13143212222' >> >> this should now store that value in $cnam. >> now how do I put that value for example "John Smith" in the from >> portion of sip messaging so that it displays on the users sip >> phone, or phone attached to an ata? >> >> >> >> _______________________________________________ >> Users mailing list >> Users(a)openser.org >> http://openser.org/cgi-bin/mailman/listinfo/users >> >> >> > >

18 years, 5 months

[Serusers] Please note the "HOW TO" for MYSQL connect issue

by Dhiman D Chowdhury

Dear friends, If you are like me faced with an issue describe below and could not find the answer for it. Please note the recommendation below. setup: Redhat Linux 9.0 and Mysql 3.23 Issue: 1. while trying to connect from shell prompt; #mysql Eorr 1045: Access denied for root@localhost (using password: No). Note: you will see this message in different times perhaps when using: # mysql.sh create or similar commands. Recommendation: There is a bug in Mysql version 3.23: Please visit the url below: http://bugs.mysql.com/bug.php?id=11822 To overcome the issue: Simply use the following command: mysql -h 127.0.0.1 -u root -p [issue it as needed] Thanks Dhiman

18 years, 5 months

[Users] problems with mediaproxy

by Gustavo Hernandez Baratta

Hi all! I´m trying to setup mediaproxy but making calls this error occur with proxydispatcher: Starting SER MediaProxy server: mediaproxyListening for commands on local socket `/var/run/proxydispatcher.sock' Default mediaproxy server is on `XX.XXX.XXX.XXX:25060' : : ---------------------------------------- Exception happened during processing of request from Traceback (most recent call last): File "/usr/lib/python2.2/SocketServer.py", line 458, in process_request_thread self.finish_request(request, client_address) File "/usr/lib/python2.2/SocketServer.py", line 253, in finish_request self.RequestHandlerClass(request, client_address, self) File "/usr/lib/python2.2/SocketServer.py", line 514, in __init__ self.handle() File "/usr/local/mediaproxy/modules/dispatcher.py", line 303, in handle result = self.execute(command) File "/usr/local/mediaproxy/modules/dispatcher.py", line 347, in execute proxy = MediaProxy('domain://%s' % domain).address File "/usr/local/mediaproxy/modules/dispatcher.py", line 578, in __init__ self.address = proxy File "/usr/local/mediaproxy/modules/dispatcher.py", line 583, in __setattr__ if name in readonly and self.__dict__.has_key(name): TypeError: 'in <string>' requires character as left operand ---------------------------------------- : ---------------------------------------- Exception happened during processing of request from Traceback (most recent call last): File "/usr/lib/python2.2/SocketServer.py", line 458, in process_request_thread self.finish_request(request, client_address) File "/usr/lib/python2.2/SocketServer.py", line 253, in finish_request self.RequestHandlerClass(request, client_address, self) File "/usr/lib/python2.2/SocketServer.py", line 514, in __init__ self.handle() File "/usr/local/mediaproxy/modules/dispatcher.py", line 303, in handle result = self.execute(command) File "/usr/local/mediaproxy/modules/dispatcher.py", line 347, in execute proxy = MediaProxy('domain://%s' % domain).address File "/usr/local/mediaproxy/modules/dispatcher.py", line 578, in __init__ self.address = proxy File "/usr/local/mediaproxy/modules/dispatcher.py", line 583, in __setattr__ if name in readonly and self.__dict__.has_key(name): TypeError: 'in <string>' requires character as left operand ---------------------------------------- Ideas? Thanks a lot, gus

18 years, 5 months

[Users] version 1.0.0 released

by Daniel-Constantin Mierla

Hi everybody, the version 1.0.0 has been released. The branch 'rel_1_0_0' is created and must be used by anybody wanting the get v1.0.0 out from CVS (cvs co -r rel_1_0_0 sip-server). There are a lot of new features in this release, starting from TLS, pseudo-variables in core and continuing with enhancements in avpops and other module. This release is the first open source sip server with TLS support, although there is still to work on it (e.g., multi domain support) it allow secure sip signaling communications between servers and clients. An unified format of pseudo-variables has been adopted in core and many modules, basic functionality for future dialog support is present in RR module, avpops includes functions for string operations (concatenation, prefix, suffix, substitute), arithmetic and bitwise operations, among others. A new module, uac_redirect, has been introduced to handle redirect replies (3xx) on server, with proper accounting and filter rules. See the full list of new features at: http://www.openser.org/release-1.0.0.php A roughly change log can be browsed online at: http://cvs.sourceforge.net/viewcvs.py/openser/sip-server/ChangeLog?view=mar… There are two categories of released packages: - classic openser, without TLS support - the name of the package does not contain the -tls- word - TLS-ed version of openser - the name of the package contain the -tls- word The tarball with the sources can be downloaded from: http://openser.org/pub/openser/1.0.0/src/ The basic binary packages are deployed to the download site: http://openser.org/pub/openser/1.0.0/bin/ http://openser.org/pub/openser/1.0.0/packages/ We are still collecting other packages from contributors which already volunteered, so expect new distributions to be represented there in the next days. The module documentations are up-to-date, the site and tutorials need a quick review in the next days.

18 years, 5 months

Jump to page:

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 October 2005