sr-users

sr-users@lists.kamailio.org

4 participants
37456 discussions

RE: [Users] SIP Clients Can't REGISTER
by Hamid Ali Asgari 19 Jun '06

19 Jun '06

The client can't register, still it doesn't allow registration. Attached is the ngrep output you mentioned. Thanks, Hamid Ngrep Output: # U 85.15.7.17:3166 -> 85.15.7.18:5060 REGISTER sip:shatel.ir SIP/2.0..From: sip:101@shatel.ir;tag=5fa04040..To: sip:101@shatel.ir..Call-Id: 9401fb256987b29da88b308b1 1ce64ed..Cseq: 1 REGISTER..Contact: <sip:101@85.15.7.17;LINEID=6f5beb97d08670a1c8328ce1526ae928>..Expires: 300..Date: Mon, 19 J un 2006 11:02:02 GMT..Max-Forwards: 20..User-Agent: sipX/2.5.2 (WinNT)..Accept-Language: en..Via: SIP/2.0/UDP 85.15.7.17;branch =z9hG4bK-a4ba80ab4920a96042a782f74c40944d..Content-Length: 0.... # U 85.15.7.17:3166 -> 85.15.7.18:5060 REGISTER sip:shatel.ir SIP/2.0..From: sip:101@shatel.ir;tag=5fa04040..To: sip:101@shatel.ir..Call-Id: 9401fb256987b29da88b308b1 1ce64ed..Cseq: 1 REGISTER..Contact: <sip:101@85.15.7.17;LINEID=6f5beb97d08670a1c8328ce1526ae928>..Expires: 300..Date: Mon, 19 J un 2006 11:02:02 GMT..Max-Forwards: 20..User-Agent: sipX/2.5.2 (WinNT)..Accept-Language: en..Via: SIP/2.0/UDP 85.15.7.17;branch =z9hG4bK-a4ba80ab4920a96042a782f74c40944d..Content-Length: 0.... # U 85.15.7.17:3166 -> 85.15.7.18:5060 REGISTER sip:shatel.ir SIP/2.0..From: sip:101@shatel.ir;tag=5fa04040..To: sip:101@shatel.ir..Call-Id: 9401fb256987b29da88b308b1 1ce64ed..Cseq: 1 REGISTER..Contact: <sip:101@85.15.7.17;LINEID=6f5beb97d08670a1c8328ce1526ae928>..Expires: 300..Date: Mon, 19 J un 2006 11:02:02 GMT..Max-Forwards: 20..User-Agent: sipX/2.5.2 (WinNT)..Accept-Language: en..Via: SIP/2.0/UDP 85.15.7.17;branch =z9hG4bK-a4ba80ab4920a96042a782f74c40944d..Content-Length: 0.... # U 85.15.7.18:5060 -> 85.15.7.17:5060 SIP/2.0 401 Unauthorized..From: sip:101@shatel.ir;tag=5fa04040..To: sip:101@shatel.ir;tag=a2c1e7c3808498f2cb2d193cd520e0fc.60d6 ..Call-Id: 9401fb256987b29da88b308b11ce64ed..Cseq: 1 REGISTER..Via: SIP/2.0/UDP 85.15.7.17;branch=z9hG4bK-a4ba80ab4920a96042a78 2f74c40944d..WWW-Authenticate: Digest realm="shatel.ir", nonce="449677461ef22770698d74f5dde4b0c2f00cf44f"..Server: OpenSer (1.0 .1 (i386/linux))..Content-Length: 0..Warning: 392 85.15.7.18:5060 "Noisy feedback tells: pid=13352 req_src_ip=85.15.7.17 req_s rc_port=3166 in_uri=sip:shatel.ir out_uri=sip:shatel.ir via_cnt==1".... # U 85.15.7.18:5060 -> 85.15.7.17:5060 SIP/2.0 401 Unauthorized..From: sip:101@shatel.ir;tag=5fa04040..To: sip:101@shatel.ir;tag=a2c1e7c3808498f2cb2d193cd520e0fc.60d6 ..Call-Id: 9401fb256987b29da88b308b11ce64ed..Cseq: 1 REGISTER..Via: SIP/2.0/UDP 85.15.7.17;branch=z9hG4bK-a4ba80ab4920a96042a78 2f74c40944d..WWW-Authenticate: Digest realm="shatel.ir", nonce="4496774acfd59b6e20c1968fc0bff804d526ce03"..Server: OpenSer (1.0 .1 (i386/linux))..Content-Length: 0..Warning: 392 85.15.7.18:5060 "Noisy feedback tells: pid=13352 req_src_ip=85.15.7.17 req_s rc_port=3166 in_uri=sip:shatel.ir out_uri=sip:shatel.ir via_cnt==1".... -----Original Message----- From: Daniel-Constantin Mierla [mailto:daniel@voice-system.ro] Sent: Monday, June 19, 2006 4:32 PM To: Hamid Ali Asgari Cc: users(a)openser.org Subject: Re: [Users] SIP Clients Can't REGISTER Hello, On 06/19/06 14:38, Hamid Ali Asgari wrote: > Hi, > Thanks for the reply. > I commented out the entry you mentioned: > > #101(a)mydomain.com Auth-Type := Accept, Sip-Group == "suspended", > #Service-Type == "Group-Check" > > What happens now is that the radius will check for a group named SUSPENDED > and will reject because it won't match the 101 user: > > >From RADIUS debug: > users: Matched entry DEFAULT at line 152 > users: Matched entry DEFAULT at line 255 > ----------------------------------------------------------- > Users:152: DEFAULT Auth-Type = System > Fall-Through = 1 > Users:255: DEFAULT Auth-Type := Reject, Service-Type == "Group-Check" > > Any thoughts? > this is ok, it is the response that the user is not in the suspended group. The processing should go further in openser configuration script. Do you encounter other issues with calls/registrations? Cheers, Daniel > Hamid > > > > > -----Original Message----- > From: Daniel-Constantin Mierla [mailto:daniel@voice-system.ro] > Sent: Monday, June 19, 2006 12:54 PM > To: Hamid Ali Asgari > Cc: 'Edson'; users(a)openser.org > Subject: Re: [Users] SIP Clients Can't REGISTER > > If look carefully in the configuration file of the tutorial, it checks > for users belonging to "suspended" group. As you have in 'users' file: > > 101(a)mydomain.com Auth-Type := Accept, Sip-Group == "suspended", > Service-Type == "Group-Check" > > Reply-Message = "Authorized" > > means that user 101 is in suspended group and it is not allowed to > register or initiate calls. So remove this line for your 'users' file. > > Also, when you test, just watch the network traffic on you sip server, > it will reveal the reply code so you can spot easily which statement was > hit in the config file: ngrep -d any port 5060 > > Cheers, > Daniel > >

2 1

RE: [Serusers] Mediaproxy problem
by İlker Aktuna (Koç.net) 19 Jun '06

19 Jun '06

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/010C0605/07024D06/0203064C/007…> _____________________________________________________________________________________________________________________________________________ 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

[Serusers] Mediaproxy problem
by İlker Aktuna (Koç.net) 19 Jun '06

19 Jun '06

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/0A090604/07074E00/0906054D/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. _____________________________________________________________________________________________________________________________________________

1 0

Re: [Serusers] SER doesn't generate NOTIFY
by Vaclav Kubart 19 Jun '06

19 Jun '06

Look into "presence handbook" (on ftp://ftp.iptel.org/pub/ser/presence). If you want to throw authorization out, you can set PA module parameter "auth" to "none". Vaclav On Mon, Jun 19, 2006 at 03:21:39PM +0200, Alois Schafferhofer wrote: > And how can the subscription get authorized? > > Thank you! > > Alois > > > >From: Vaclav Kubart <vaclav.kubart(a)iptel.org> > >To: Alois Schafferhofer <schaffi_lui(a)hotmail.com> > >CC: serusers(a)lists.iptel.org > >Subject: Re: [Serusers] SER doesn't generate NOTIFY > >Date: Mon, 19 Jun 2006 15:13:43 +0200 > > > >Hi, > >it seems that the subscription is not authorized (response is "202 > >Accepted") and thus the subscriber is not notified on changes. > > Vaclav > > > >On Mon, Jun 19, 2006 at 02:45:41PM +0200, Alois Schafferhofer wrote: > >> Hi, > >> > >> I use Presence Snapshot 4.1 on Linux 9.3. > >> SER doesn't generate a NOTIFY when status changes. In MySQL database, I > >can > >> see the change: > >> table: Presentity_Contact > >> basic: online/offline > >> status:"" > >> > >> I wonder why basic is online/offline and status is "". Is this correct? > >In > >> my messages, i send basic=open/closed. > >> > >> In my config-file, I set the timer_interval to 5 seconds. > >> > >> What am I doing wrong? > >> > >> Regards, > >> Alois > >> > >> SUBSCRIBE sip:PDA_User@fh-joanneum.at SIP/2.0..Via: SIP/2.0/UDP > >> 10.15.200.22:5060;rport;branch=z9hG4bK67417..Max-Forwards: 70..To: > >> <sip:PDA_User@fh-joanneum.at>..From: > >> <sip:esca@fh-joanneum.at>;tag=z9hG4bK64795000..Call-ID: > >> 720365631452@10.15.200.22..CSeq: 1 SUBSCRIBE..Contact: > >> <sip:esca@10.15.200.22>..Expires: 3600..User-Agent: mjsip stack > >1.6..Event: > >> presence..Accept: application/cpimpidf+xml..Content-Length: 0.... > >> > >> SIP/2.0 202 Accepted..Via: SIP/2.0/UDP > >> > >10.15.200.22:5060;rport=5060;branch=z9hG4bK67417..To:<sip:PDA_User@fhjoanneum.at>;tag=589230a54cd08b3768529724501fae28-4f39..From: > >> > ><sip:esca@fh-joanneum.at>;tag=z9hG4bK64795000..Call-ID:720365631452@10.15.200.22..CSeq: > >> 1 SUBSCRIBE..Expires: 3600..Contact: <sip:10.15.200.57:5060>..Server: > >Sip > >> EXpress router (0.10.99-dev35-pa-4.1 (i386/linux))..Content-Length: > >> 0..Warning: 392 10.15.200.57:5060 "Noisy feedba > >> ck tells: pid=17547 req_src_ip=10.15.200.22 req_src_port=5060 > >> in_uri=sip:PDA_User@fhjoanneum. > >> at out_uri=sip:PDA_User@fh-joanneum.at via_cnt==1".... > >> > >> NOTIFY sip:esca@10.15.200.22 SIP/2.0..Via: SIP/2.0/UDP > >> > >10.15.200.57;branch=z9hG4bK720f.274f52a6.0..To:<sip:esca@fhjoanneum.at>;tag=z9hG4bK64795000..From: > >> > ><sip:PDA_User@fh-joanneum.at>;tag=589230a54cd08b3768529724501fae28-4f39..CSeq:1 > >> NOTIFY..Call-ID: 720365631452@10.15.200.22..Content-Length: 0.. > >> User-Agent: Sip EXpress router(0.10.99-dev35-pa-4.1 > >(i386/linux))..Event: > >> presence..Contact: > >> <sip:10.15.200.57:5060>..Subscription-State: pending;expires=3600.... > >> > >> U 10.15.200.22:5060 -> 10.15.200.57:5060 > >> SIP/2.0 200 OK..Via: SIP/2.0/UDP > >> 10.15.200.57;branch=z9hG4bK720f.274f52a6.0..To: > >> <sip:esca@fh-joanneum.at>;tag=z9hG4bK64795000..From: <sip:PDA_User@fh > >> -joanneum.at>;tag=589230a54cd08b3768529724501fae28-4f39..Call-ID: > >> 720365631452@10.15.200.22..CSeq: 1 NOTIFY..Server: mjsip stack > >> 1.6..Content-Length:0. > >> > >> > >> > >> PUBLISH sip:PDA_User@fh-joanneum.at SIP/2.0..Via: SIP/2.0/UDP > >> 10.0.0.3:5060;branch=z9hG4bK843798674..Max-Forwards: 70..From: > >> <sip:PDA_User@fhjoanneum > >> .at>;tag=850624414..To: <sip:PDA_User@fh-joanneum.at>..Call-ID: > >> 1836804380-820133259- > >> 1969969487..CSeq: 6 PUBLISH..Contact: <sip:PDA_User@fh-joanneum.a > >> t>..Content-Type: application/pidf+xml..Content-Length: 226..Expires: > >> 7200..Event: > >> presence..User-Agent: SIP .NET 1.0 evaluation version, www.independ > >> entsoft.com..SIP-If-Match: 0x409c3088x10cc41b0x4496b143....<?xml > >> version="1.0" > >> encoding="utf-8"?> > >> <presence xmlns="urn:ietf:params:xml:ns:pidf" > >> entity="pres:PDA_user@fh-joanneum.at"> > >> <tuple id="4e9a7335-5f7f-4a3c-91a7-fd761e9138b0"> > >> <status><basic>open</basic> > >> </status> > >> </tuple> > >> </presence>.. > >> > >> SIP/2.0 200 OK..Via: SIP/2.0/UDP 10.0.0.3:5060;branch=z9hG4bK843798674.. > >> From:<sip:PDA_User@fh-joanneum.at>;tag=850624414..To: > >> > ><sip:PDA_User@fh-joanneum.at>;tag=589230a54cd08b3768529724501fae28-ed6b..Call-ID: > >> 1836804380-820133259- > >> 1969969487..CSeq: 6 PUBLISH..Expires: > >> 120..SIP-Tag:0x409c3088x10cc41b0x4496b143..Contact: > >> <sip:10.0.0.11:5060>..Server: Sip EXpress router > >> (0.10.99-dev35-pa-4.1(i386/linux))..Content-Length: 0..Warning: 392 > >> 10.0.0.11: > >> 5060 "Noisy feedback tells: pid=17551 req_src_ip=10.0.0.3 > >req_src_port=5060 > >> in_uri=sip:PDA_User@fh-joanneum.at out_uri=sip:PDA_User@fh-joanneum.at > >> via_cnt==1" > >> > >> > >> > >> > >> # modparam("msilo","registrar","sip:registrar@test-domain.com") > >> modparam("msilo","use_contact",0) > >> modparam("msilo","expire_time",7200) > >> # -- usrloc params -- > >> # -- auth params -- > >> # Uncomment if you are using auth module > >> # > >> modparam("auth_db", "calculate_ha1", yes) > >> # > >> # If you set "calculate_ha1" parameter to yes (which true in this > >config), > >> # uncomment also the following parameter) > >> # > >> modparam("auth_db", "password_column", "password") > >> # -- rr params -- > >> # add value to ;lr param to make some broken UAs happy > >> modparam("rr", "enable_full_lr", 1) > >> modparam("rls", "min_expiration", 200) > >> modparam("rls", "max_expiration", 300) > >> modparam("rls", "default_expiration", 300) > >> modparam("rls", "auth", "none") #"implicit" > >> modparam("rls", "xcap_root", "http://localhost/xcap") > >> modparam("rls", "reduce_xcap_needs", 1) > >> modparam("rls", "db_mode", 1) > >> modparam("rls", "db_url", "mysql://ser:heslo@localhost:3306/ser") > >> modparam("pa", "default_expires", 3600) > >> modparam("pa", "use_db", 1) > >> #modparam("pa", "pa_domain", "fh-joanneum.at") > >> modparam("pa", "use_offline_winfo", 1) # allow storing authorization > >> requests for offline users into database > >> modparam("pa", "offline_winfo_timer", 600) # how often try to remove old > >> stored authorization requests > >> modparam("pa", "offline_winfo_expiration", 600) # how long stored > >> authorization requests live > >> modparam("pa", "db_url", "mysql://ser:heslo@localhost:3306/ser") > >> modparam("pa", "auth", "xcap") # mode of PA authorization: none, > >> implicit or xcap > >> modparam("pa", "auth_xcap_root", "http://localhost/xcap") > >> modparam("pa", "winfo_auth", "none") # do not authorize watcherinfo > >> subscriptions > >> modparam("pa", "use_callbacks", 1) # use only published information if > >set > >> to 0 > >> modparam("pa", "accept_internal_subscriptions", 1) # don't accept > >internal > >> subscriptions from RLS, ... > >> modparam("pa", "watcherinfo_notify", 1) > >> modparam("pa", "max_subscription_expiration", 3600) # maximum value of > >> Expires for subscriptions > >> modparam("pa", "max_publish_expiration", 120) # maximum value of Expires > >for > >> publications > >> modparam("pa", "timer_interval", 5) > >> > >> modparam("presence_b2b", "presence_route", > >> "<sip:127.0.0.1;transport=tcp;lr>") > >> # route for generated SUBSCRIBE requests for presence > >> modparam("presence_b2b", "on_error_retry_time", 60) # waiting time from > >> error to new attepmt about SUBSCRIBE > >> modparam("presence_b2b", "wait_for_term_notify", 33) # how long wait for > >> NOTIFY > >> with Subscription-Status=terminated after unsubscribe > >> modparam("presence_b2b", "resubscribe_delta", 30) # how long before > >> expiration send renewal SUBSCRIBE request > >> modparam("presence_b2b", "min_resubscribe_time", 60) # minimal time to > >send > >> renewal SUBSCRIBE request from receiving previous response > >> modparam("presence_b2b", "default_expiration", 3600) # default > >expiration > >> timeout > >> modparam("presence_b2b", "handle_presence_subscriptions", 1) # process > >> internal subscriptions to presence events > >> modparam("usrloc", "db_mode", 1) > >> modparam("domain", "db_mode", 1) > >> modparam("domain|uri_db|acc|auth_db|usrloc|msilo", "db_url", > >> "mysql://ser:heslo@localhost:3306/ser") > >> modparam("domain", "domain_table", "domain") > >> #modparam("domain", "domain_column", "domain") > >> modparam("fifo", "fifo_file", "/tmp/ser_fifo") > >> > >> > >> route{ > >> # XML RPC > >> if (method == "POST" || method == "GET") { > >> create_via(); > >> log(1, "Created via()"); > >> dispatch_rpc(); > >> log(1, "Dispatched rps()"); > >> break; > >> log(1, "break XML RPC"); > >> } > >> # initial sanity checks -- messages with > >> # max_forwards==0, or excessively long requests > >> if (!mf_process_maxfwd_header("10")) { > >> sl_send_reply("483","Too Many Hops"); > >> break; > >> }; > >> if (msg:len >= max_len ) { > >> sl_send_reply("513", "Message too big"); > >> break; > >> }; > >> # we record-route all messages -- to make sure that > >> # subsequent messages will go through our proxy; that's > >> # particularly good if upstream and downstream entities > >> # use different transport protocol > >> if (!method=="REGISTER") record_route(); > >> # subsequent messages withing a dialog should take the > >> # path determined by record-routing > >> if (loose_route()) { > >> # mark routing logic in request > >> append_hf("P-hint: rr-enforced\r\n"); > >> route(1); > >> break; > >> }; > >> if (uri==myself) { > >> log(1, "URI == myself"); > >> if (method=="SUBSCRIBE") { > >> log(1, "SUBSCRIBE received"); > >> if (!t_newtran()) { > >> sl_reply_error(); > >> break; > >> }; > >> # new subscription > >> if (@to.tag=="") { > >> log(1, "new SUBSCRIPTION"); > >> if ((@msg.supported=~"eventlist")) { > >> log(1, "msg.supported=eventlist"); > >> # Supported header field > >> # -> may be RLS subscription > >> if (is_simple_rls_target("$uid-list")) { > >> log(1, "it is simple > >> subscription!\n"); > >> # handle_rls_subscription("1"); > >> # takes From UID and makes XCAP > >> query > >> # for user's list named > >> "default" > >> if (@to.tag=="") { > >> # only for new > >> subscriptions (with empty to tag > >> if > >> (!query_resource_list("default")) { > >> t_reply("500", > >> "XCAP query error"); > >> break; > >> } > >> } > >> } > >> if (!have_flat_list()) { > >> # query_resource_list failed or > >> was not called > >> # do standard RLS query acording > >> to To/AOR > >> query_rls_services(); > >> } > >> if (have_flat_list()) { > >> handle_rls_subscription("1"); > >> break; > >> } > >> } > >> # SUBSCRIBE to existing user > >> # xlog("L_ERR", "PA: handling subscription: %tu > >> from: %fu\n"); > >> log(1, "handle SUBSCRIBE request\n"); > >> handle_subscription("registrar"); > >> log(1, "handled subscription\n"); > >> log(1, "break 1"); > >> break; > >> } > >> else { # renewal subscription > >> log(1, "else - renewal subscription"); > >> if (!handle_rls_subscription("0")) { > >> log(1, "!handle rls subscription"); > >> handle_subscription("registrar"); > >> log(1, "handled subscription 2"); > >> } > >> log(1, "break 2"); > >> break; > >> } > >> } > >> if (method=="REGISTER") { > >> log(1, "REGISTER received"); > >> # if (!www_authorize("fh-joanneum.at", "credentials")) { > >> # www_challenge("fh-joanneum.at", "0"); > >> # break; > >> # }; > >> save("location"); > >> log(1, "saved location"); > >> break; > >> }; > >> > >> > >> if (method=="PUBLISH") { > >> log(1, "PUBLISH received"); > >> if (!t_newtran()) { > >> sl_reply_error(); > >> break; > >> }; > >> log(1, "handle publish request\n"); > >> handle_publish("registrar"); > >> log(1, "handled publish\n"); > >> break; > >> }; > >> > >> if (method=="NOTIFY") { > >> log(1, "NOTIFY received"); > >> if (!t_newtran()) { > >> log(1, "newtran error\n"); > >> sl_reply_error(); > >> break; > >> }; > >> if (!handle_notify()) { > >> log(1, "unable to handle notification - lui"); > >> t_reply("481", "Unable to handle notification"); > >> } > >> break; > >> }; > >> > >> > >> # message authorization > >> if (method=="MESSAGE") { > >> log(1, "MESSAGE authorization\n"); > >> if (!authorize_message("http://localhost/xcap")) { > >> sl_reply("403", "Forbidden"); > >> break; > >> } > >> } > >> # native SIP destinations are handled using our USRLOC DB > >> if (!lookup("location")) { > >> log(1, "!lookup location gö"); > >> sl_send_reply("404", "Not Found"); > >> break; > >> }; > >> }; > >> # append_hf("P-hint: usrloc applied\r\n"); > >> log(1, "route (1)"); > >> route(1); > >> } > >> route[1] > >> { > >> # send it out now; use stateful forwarding as it works reliably > >> # even for UDP2TCP > >> if (!t_relay()) { > >> log(1, "!t_relay - sl reply error"); > >> sl_reply_error(); > >> }; > >> } > >> > >> > >> _______________________________________________ > >> Serusers mailing list > >> Serusers(a)lists.iptel.org > >> http://lists.iptel.org/mailman/listinfo/serusers >

1 0

[Serusers] pa_domain
by Alois Schafferhofer 19 Jun '06

19 Jun '06

Hi. I installed the compiled version of SER 0.9.5 on Linux 9.3. I just copied the files into the right directories. Now I have a problem to connect to MySQL database. In the Log-message, I can see the line: pa_domain=sip.handhelds.org But I need another pa_domain and I think that this is the problem. How can I change pa_domain? ser[17044]: Maxfwd module- initializing ser[17044]: db_url=0x82077c0 ser[17044]: db_url=mysql://ser:heslo@127.0.0.1:3306/ser ser[17044]: db_url.len=36 ser[17044]: pa_domain=sip.handhelds.org ser[17044]: pa_mod: use_db=1 db_url.s=mysql://ser:heslo@127.0.0.1:3306/ser pa_domain=sip.handhelds.org ser[17044]: pa_mod_init done ser[17044]: subscribe_fixup: pdomain name is registrar ser[17044]: new_connection(): Client does not support authentication protocol requested by server; consider upgrading MySQL client ser[17044]: db_init(): Could not create a connection ser[17044]: ERROR: auth_db_ver: unable to open database connection ser[17044]: auth_db:str_fixup(): Error while querying table version ser[17044]: ERROR: fix_expr : fix_actions error ser[17044]: db_close(): Invalid parameter value Best regards, Alois

2 1

[Serusers] SER doesn't generate NOTIFY
by Alois Schafferhofer 19 Jun '06

19 Jun '06

Hi, I use Presence Snapshot 4.1 on Linux 9.3. SER doesn't generate a NOTIFY when status changes. In MySQL database, I can see the change: table: Presentity_Contact basic: online/offline status:"" I wonder why basic is online/offline and status is "". Is this correct? In my messages, i send basic=open/closed. In my config-file, I set the timer_interval to 5 seconds. What am I doing wrong? Regards, Alois SUBSCRIBE sip:PDA_User@fh-joanneum.at SIP/2.0..Via: SIP/2.0/UDP 10.15.200.22:5060;rport;branch=z9hG4bK67417..Max-Forwards: 70..To: <sip:PDA_User@fh-joanneum.at>..From: <sip:esca@fh-joanneum.at>;tag=z9hG4bK64795000..Call-ID: 720365631452@10.15.200.22..CSeq: 1 SUBSCRIBE..Contact: <sip:esca@10.15.200.22>..Expires: 3600..User-Agent: mjsip stack 1.6..Event: presence..Accept: application/cpimpidf+xml..Content-Length: 0.... SIP/2.0 202 Accepted..Via: SIP/2.0/UDP 10.15.200.22:5060;rport=5060;branch=z9hG4bK67417..To:<sip:PDA_User@fhjoanneum.at>;tag=589230a54cd08b3768529724501fae28-4f39..From: <sip:esca@fh-joanneum.at>;tag=z9hG4bK64795000..Call-ID:720365631452@10.15.200.22..CSeq: 1 SUBSCRIBE..Expires: 3600..Contact: <sip:10.15.200.57:5060>..Server: Sip EXpress router (0.10.99-dev35-pa-4.1 (i386/linux))..Content-Length: 0..Warning: 392 10.15.200.57:5060 "Noisy feedba ck tells: pid=17547 req_src_ip=10.15.200.22 req_src_port=5060 in_uri=sip:PDA_User@fhjoanneum. at out_uri=sip:PDA_User@fh-joanneum.at via_cnt==1".... NOTIFY sip:esca@10.15.200.22 SIP/2.0..Via: SIP/2.0/UDP 10.15.200.57;branch=z9hG4bK720f.274f52a6.0..To:<sip:esca@fhjoanneum.at>;tag=z9hG4bK64795000..From: <sip:PDA_User@fh-joanneum.at>;tag=589230a54cd08b3768529724501fae28-4f39..CSeq:1 NOTIFY..Call-ID: 720365631452@10.15.200.22..Content-Length: 0.. User-Agent: Sip EXpress router(0.10.99-dev35-pa-4.1 (i386/linux))..Event: presence..Contact: <sip:10.15.200.57:5060>..Subscription-State: pending;expires=3600.... U 10.15.200.22:5060 -> 10.15.200.57:5060 SIP/2.0 200 OK..Via: SIP/2.0/UDP 10.15.200.57;branch=z9hG4bK720f.274f52a6.0..To: <sip:esca@fh-joanneum.at>;tag=z9hG4bK64795000..From: <sip:PDA_User@fh -joanneum.at>;tag=589230a54cd08b3768529724501fae28-4f39..Call-ID: 720365631452@10.15.200.22..CSeq: 1 NOTIFY..Server: mjsip stack 1.6..Content-Length:0. PUBLISH sip:PDA_User@fh-joanneum.at SIP/2.0..Via: SIP/2.0/UDP 10.0.0.3:5060;branch=z9hG4bK843798674..Max-Forwards: 70..From: <sip:PDA_User@fhjoanneum .at>;tag=850624414..To: <sip:PDA_User@fh-joanneum.at>..Call-ID: 1836804380-820133259- 1969969487..CSeq: 6 PUBLISH..Contact: <sip:PDA_User@fh-joanneum.a t>..Content-Type: application/pidf+xml..Content-Length: 226..Expires: 7200..Event: presence..User-Agent: SIP .NET 1.0 evaluation version, www.independ entsoft.com..SIP-If-Match: 0x409c3088x10cc41b0x4496b143....<?xml version="1.0" encoding="utf-8"?> <presence xmlns="urn:ietf:params:xml:ns:pidf" entity="pres:PDA_user@fh-joanneum.at"> <tuple id="4e9a7335-5f7f-4a3c-91a7-fd761e9138b0"> <status><basic>open</basic> </status> </tuple> </presence>.. SIP/2.0 200 OK..Via: SIP/2.0/UDP 10.0.0.3:5060;branch=z9hG4bK843798674.. From:<sip:PDA_User@fh-joanneum.at>;tag=850624414..To: <sip:PDA_User@fh-joanneum.at>;tag=589230a54cd08b3768529724501fae28-ed6b..Call-ID: 1836804380-820133259- 1969969487..CSeq: 6 PUBLISH..Expires: 120..SIP-Tag:0x409c3088x10cc41b0x4496b143..Contact: <sip:10.0.0.11:5060>..Server: Sip EXpress router (0.10.99-dev35-pa-4.1(i386/linux))..Content-Length: 0..Warning: 392 10.0.0.11: 5060 "Noisy feedback tells: pid=17551 req_src_ip=10.0.0.3 req_src_port=5060 in_uri=sip:PDA_User@fh-joanneum.at out_uri=sip:PDA_User@fh-joanneum.at via_cnt==1" # modparam("msilo","registrar","sip:registrar@test-domain.com") modparam("msilo","use_contact",0) modparam("msilo","expire_time",7200) # -- usrloc params -- # -- auth params -- # Uncomment if you are using auth module # modparam("auth_db", "calculate_ha1", yes) # # If you set "calculate_ha1" parameter to yes (which true in this config), # uncomment also the following parameter) # modparam("auth_db", "password_column", "password") # -- rr params -- # add value to ;lr param to make some broken UAs happy modparam("rr", "enable_full_lr", 1) modparam("rls", "min_expiration", 200) modparam("rls", "max_expiration", 300) modparam("rls", "default_expiration", 300) modparam("rls", "auth", "none") #"implicit" modparam("rls", "xcap_root", "http://localhost/xcap") modparam("rls", "reduce_xcap_needs", 1) modparam("rls", "db_mode", 1) modparam("rls", "db_url", "mysql://ser:heslo@localhost:3306/ser") modparam("pa", "default_expires", 3600) modparam("pa", "use_db", 1) #modparam("pa", "pa_domain", "fh-joanneum.at") modparam("pa", "use_offline_winfo", 1) # allow storing authorization requests for offline users into database modparam("pa", "offline_winfo_timer", 600) # how often try to remove old stored authorization requests modparam("pa", "offline_winfo_expiration", 600) # how long stored authorization requests live modparam("pa", "db_url", "mysql://ser:heslo@localhost:3306/ser") modparam("pa", "auth", "xcap") # mode of PA authorization: none, implicit or xcap modparam("pa", "auth_xcap_root", "http://localhost/xcap") modparam("pa", "winfo_auth", "none") # do not authorize watcherinfo subscriptions modparam("pa", "use_callbacks", 1) # use only published information if set to 0 modparam("pa", "accept_internal_subscriptions", 1) # don't accept internal subscriptions from RLS, ... modparam("pa", "watcherinfo_notify", 1) modparam("pa", "max_subscription_expiration", 3600) # maximum value of Expires for subscriptions modparam("pa", "max_publish_expiration", 120) # maximum value of Expires for publications modparam("pa", "timer_interval", 5) modparam("presence_b2b", "presence_route", "<sip:127.0.0.1;transport=tcp;lr>") # route for generated SUBSCRIBE requests for presence modparam("presence_b2b", "on_error_retry_time", 60) # waiting time from error to new attepmt about SUBSCRIBE modparam("presence_b2b", "wait_for_term_notify", 33) # how long wait for NOTIFY with Subscription-Status=terminated after unsubscribe modparam("presence_b2b", "resubscribe_delta", 30) # how long before expiration send renewal SUBSCRIBE request modparam("presence_b2b", "min_resubscribe_time", 60) # minimal time to send renewal SUBSCRIBE request from receiving previous response modparam("presence_b2b", "default_expiration", 3600) # default expiration timeout modparam("presence_b2b", "handle_presence_subscriptions", 1) # process internal subscriptions to presence events modparam("usrloc", "db_mode", 1) modparam("domain", "db_mode", 1) modparam("domain|uri_db|acc|auth_db|usrloc|msilo", "db_url", "mysql://ser:heslo@localhost:3306/ser") modparam("domain", "domain_table", "domain") #modparam("domain", "domain_column", "domain") modparam("fifo", "fifo_file", "/tmp/ser_fifo") route{ # XML RPC if (method == "POST" || method == "GET") { create_via(); log(1, "Created via()"); dispatch_rpc(); log(1, "Dispatched rps()"); break; log(1, "break XML RPC"); } # initial sanity checks -- messages with # max_forwards==0, or excessively long requests if (!mf_process_maxfwd_header("10")) { sl_send_reply("483","Too Many Hops"); break; }; if (msg:len >= max_len ) { sl_send_reply("513", "Message too big"); break; }; # we record-route all messages -- to make sure that # subsequent messages will go through our proxy; that's # particularly good if upstream and downstream entities # use different transport protocol if (!method=="REGISTER") record_route(); # subsequent messages withing a dialog should take the # path determined by record-routing if (loose_route()) { # mark routing logic in request append_hf("P-hint: rr-enforced\r\n"); route(1); break; }; if (uri==myself) { log(1, "URI == myself"); if (method=="SUBSCRIBE") { log(1, "SUBSCRIBE received"); if (!t_newtran()) { sl_reply_error(); break; }; # new subscription if (@to.tag=="") { log(1, "new SUBSCRIPTION"); if ((@msg.supported=~"eventlist")) { log(1, "msg.supported=eventlist"); # Supported header field # -> may be RLS subscription if (is_simple_rls_target("$uid-list")) { log(1, "it is simple subscription!\n"); # handle_rls_subscription("1"); # takes From UID and makes XCAP query # for user's list named "default" if (@to.tag=="") { # only for new subscriptions (with empty to tag if (!query_resource_list("default")) { t_reply("500", "XCAP query error"); break; } } } if (!have_flat_list()) { # query_resource_list failed or was not called # do standard RLS query acording to To/AOR query_rls_services(); } if (have_flat_list()) { handle_rls_subscription("1"); break; } } # SUBSCRIBE to existing user # xlog("L_ERR", "PA: handling subscription: %tu from: %fu\n"); log(1, "handle SUBSCRIBE request\n"); handle_subscription("registrar"); log(1, "handled subscription\n"); log(1, "break 1"); break; } else { # renewal subscription log(1, "else - renewal subscription"); if (!handle_rls_subscription("0")) { log(1, "!handle rls subscription"); handle_subscription("registrar"); log(1, "handled subscription 2"); } log(1, "break 2"); break; } } if (method=="REGISTER") { log(1, "REGISTER received"); # if (!www_authorize("fh-joanneum.at", "credentials")) { # www_challenge("fh-joanneum.at", "0"); # break; # }; save("location"); log(1, "saved location"); break; }; if (method=="PUBLISH") { log(1, "PUBLISH received"); if (!t_newtran()) { sl_reply_error(); break; }; log(1, "handle publish request\n"); handle_publish("registrar"); log(1, "handled publish\n"); break; }; if (method=="NOTIFY") { log(1, "NOTIFY received"); if (!t_newtran()) { log(1, "newtran error\n"); sl_reply_error(); break; }; if (!handle_notify()) { log(1, "unable to handle notification - lui"); t_reply("481", "Unable to handle notification"); } break; }; # message authorization if (method=="MESSAGE") { log(1, "MESSAGE authorization\n"); if (!authorize_message("http://localhost/xcap")) { sl_reply("403", "Forbidden"); break; } } # native SIP destinations are handled using our USRLOC DB if (!lookup("location")) { log(1, "!lookup location gö"); sl_send_reply("404", "Not Found"); break; }; }; # append_hf("P-hint: usrloc applied\r\n"); log(1, "route (1)"); route(1); } route[1] { # send it out now; use stateful forwarding as it works reliably # even for UDP2TCP if (!t_relay()) { log(1, "!t_relay - sl reply error"); sl_reply_error(); }; }

2 1

RE: [Serusers] How to send instant message programmatically
by srinivas.sriram＠wipro.com 19 Jun '06

19 Jun '06

Hi Greger I have checked with sipp , with that we can send messages. But What is my requirement is i have write the code for constructing SIP "MESSAGE" message for a given sip uri. This I have to call form one of the ser module. Total what I am trying is to send a IM message when there is a missed call for a particular SIP uri. In SER there is a code for writing into the data base of the sip uri , when there is a missed call for that Uri. At this point we have to send IM message. Thank you, Regards, Sriram Srinivas. ________________________________ From: Greger V. Teigre [mailto:greger@teigre.com] Sent: Monday, June 19, 2006 5:35 PM To: Srinivas Sriram (WT01 - IP-Multimedia Carrier & Ent Networks) Cc: serusers(a)iptel.org Subject: Re: [Serusers] How to send instant message programmatically You are better off generating the message outside SER. SER is not a UAS. Have a look at sipsak or sipp (both found at sourceforge, I think). g-) srinivas.sriram(a)wipro.com wrote: Hello, I am using SER-0.9.6. How to send instant message programmatically, how to build sip message and which function can by used(like t_uac, t_request). Can you help where and which to be changed in ser code. Thank you, Regards, Sriram Srinivas. The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com ________________________________ _______________________________________________ Serusers mailing list Serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com

2 1

Re: [Users] SIP Clients Can't REGISTER
by Daniel-Constantin Mierla 19 Jun '06

19 Jun '06

Hello, On 06/19/06 14:38, Hamid Ali Asgari wrote: > Hi, > Thanks for the reply. > I commented out the entry you mentioned: > > #101(a)mydomain.com Auth-Type := Accept, Sip-Group == "suspended", > #Service-Type == "Group-Check" > > What happens now is that the radius will check for a group named SUSPENDED > and will reject because it won't match the 101 user: > > >From RADIUS debug: > users: Matched entry DEFAULT at line 152 > users: Matched entry DEFAULT at line 255 > ----------------------------------------------------------- > Users:152: DEFAULT Auth-Type = System > Fall-Through = 1 > Users:255: DEFAULT Auth-Type := Reject, Service-Type == "Group-Check" > > Any thoughts? > this is ok, it is the response that the user is not in the suspended group. The processing should go further in openser configuration script. Do you encounter other issues with calls/registrations? Cheers, Daniel > Hamid > > > > > -----Original Message----- > From: Daniel-Constantin Mierla [mailto:daniel@voice-system.ro] > Sent: Monday, June 19, 2006 12:54 PM > To: Hamid Ali Asgari > Cc: 'Edson'; users(a)openser.org > Subject: Re: [Users] SIP Clients Can't REGISTER > > If look carefully in the configuration file of the tutorial, it checks > for users belonging to "suspended" group. As you have in 'users' file: > > 101(a)mydomain.com Auth-Type := Accept, Sip-Group == "suspended", > Service-Type == "Group-Check" > > Reply-Message = "Authorized" > > means that user 101 is in suspended group and it is not allowed to > register or initiate calls. So remove this line for your 'users' file. > > Also, when you test, just watch the network traffic on you sip server, > it will reveal the reply code so you can spot easily which statement was > hit in the config file: ngrep -d any port 5060 > > Cheers, > Daniel > > > > > On 06/18/06 12:23, Hamid Ali Asgari wrote: > >> Hi, >> >> I get the following: >> >> [root@localhost radiusclient-ng]# radiusclient -f >> /usr/local/etc/radiusclient-ng/radiusclient.conf >> 'User-Name=101(a)mydomain.com' 'Password=101';echo $? >> >> Reply-Message = 'Authenticated' >> >> 1 >> >> I guess the radiusclient is working fine since I am receiving the >> RADIUS packets on the freeradius debugs. >> >> I suspect the following entries in the debug: >> >> rad_recv: Access-Request packet from host 127.0.0.1:32901, id=197, >> length=64 >> >> User-Name = "101@mydomain" >> >> Sip-Group = "*suspended*" >> >> Service-Type = Group-Check >> >> NAS-Port = 0 >> >> NAS-IP-Address = 127.0.0.1 >> >> Why is openser setting the group to SUSPENDED???? Since there is no >> group named _suspended_ on the radius that may be the reason the >> radius is rejecting: >> >> RADIUS Users file: >> >> ### --- avps --- >> >> 101(a)mydomain.com Auth-Type := Accept, Service-Type == "SIP-Callee-AVPs" >> >> Sip-Avp += "#3#1", >> >> Sip-Avp += "#4:08:00", >> >> Sip-Avp += "#5:16:00", >> >> Sip-Avp += "#6:Mon,Wed,Thu,Fri" >> >> 102(a)mydomain.com Auth-Type := Accept, Service-Type == "SIP-Callee-AVPs" >> >> Sip-Avp += "#3#1", >> >> Sip-Avp += "#4:08:00", >> >> Sip-Avp += "#5:16:00", >> >> Sip-Avp += "#6:Mon,Wed,Thu,Free" >> >> DEFAULT Auth-Type := Accept, Service-Type == "SIP-Callee-AVPs" >> >> ### --- group checking --- >> >> ### --- user 101 --- >> >> 101(a)mydomain.com Auth-Type := Accept, Sip-Group == "voip", >> Service-Type == "Group-Check" >> >> Reply-Message = "Authorized" >> >> 101(a)mydomain.com Auth-Type := Accept, Sip-Group == "suspended", >> Service-Type == "Group-Check" >> >> Reply-Message = "Authorized" >> >> 101(a)mydomain.com Auth-Type := Accept, Sip-Group == "pstn", >> Service-Type == "Group-Check" >> >> Reply-Message = "Authorized" >> >> ### --- user 102 --- >> >> 102(a)mydomain.com Auth-Type := Accept, Sip-Group == "voip", >> Service-Type == "Group-Check" >> >> Reply-Message = "Authorized" >> >> DEFAULT Auth-Type := Reject, Service-Type == "Group-Check" >> >> ### --- user authentication --- >> >> 101(a)mydomain.com Auth-Type := Digest, User-Password == "101" >> >> Reply-Message = "Authenticated", >> >> Sip-Avp += "rpid:101", >> >> Sip-Avp += "#2:192.168.10.17", >> >> # Sip-Avp += "#2:192.168.2.11" >> >> 102(a)mydomain.com Auth-Type := Digest, User-Password == "102" >> >> Reply-Message = "Authenticated", >> >> Sip-Avp += "rpid:102", >> >> # Sip-Avp += "#2:192.168.2.12" >> >> ------------------------------------------------------------------------ >> >> *From:* Edson [mailto:4lists@gmail.com] >> *Sent:* Thursday, June 15, 2006 4:19 PM >> *To:* 'Hamid Ali Asgari'; users(a)openser.org >> *Subject:* RE: [Users] SIP Clients Can't REGISTER >> >> Take a look on the user credentials on Radius DB. Radius is rejecting >> the authentication, so there should be some mismatch between Your >> login credentials and what Radius has in its DB. >> >> Try to run this command and see what's the result (linux version): >> >> radiusclient -f <conf-dir-of-radiusclient-ng>/radiusclient.conf -p 123 >> 'User-Name=some(a)valid.user' 'Password=Guess';echo $? >> >> It should return: >> >> Reply-Message = 'Authenticated' >> >> Edson. >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Users mailing list >> Users(a)openser.org >> http://openser.org/cgi-bin/mailman/listinfo/users >> >> > > >

1 0

Re: [Serusers] Unresolvable Destination
by Greger V. Teigre 19 Jun '06

19 Jun '06

Oh yes, you just have to lookup the uri with domain name and translate it to an actual location (i.e. using lookup("location") or lookup("aliases")) Have a look at the SER Getting Started document from http://onsip.org/ (that one was for Olivier ;-) It will guide you through setting up SER. g-) Alois Schafferhofer wrote: > Thank you. > > Therefore I have two questions. > > Does it work without DNS server? > What about a Pocket PC? It can't be member of Active Directory. > > I hope, these questions don't seem too stupid for you. > > Regards, > Alois > > >> From: "Greger V. Teigre" <greger(a)teigre.com> >> To: Alois Schafferhofer <schaffi_lui(a)hotmail.com> >> CC: serusers(a)lists.iptel.org >> Subject: Re: [Serusers] Unresolvable Destination >> Date: Sat, 17 Jun 2006 20:58:46 +0200 >> >> This means that fh-joanneum.at is not possible to DNS resolve. A sip >> uri needs to be resolvable. g-) >> >> Alois Schafferhofer wrote: >>> Hi, >>> >>> I'm using Presence Snapshot 4.1. >>> >>> If I want to REGISTER my client, I get the error: Unresolvable >>> Destination. >>> >>> I have following lines in my log message: >>> >>> /usr/sbin/ser[8941]: Unknown domain to: sip:PDA_User@fh-joanneum.at >>> from: sip:PDA_User@fh-joanneum.at >>> /usr/sbin/ser[8941]: ERROR: mk_proxy: could not resolve hostname: >>> "fhjoanneum.at" >>> /usr/sbin/ser[8941]: ERROR: uri2proxy: bad host name in URI >>> <sip:PDA_User@fhjoanneum.at> >>> /usr/sbin/ser[8941]: ERROR: t_forward_nonack: failure to add branches >>> /usr/sbin/ser[8941]: sl_reply error() >>> /usr/sbin/ser[8941]: ERROR: sl_reply_error used: I'm terribly sorry, >>> server error occurred (1/SL) >>> >>> >>> >>> U 10.0.0.3:5060 -> 10.0.0.11:5060 >>> REGISTER sip:PDA_User@fh-joanneum.at SIP/2.0..Via: SIP/2.0/UDP >>> 10.0.0.3:5060;branch=z9hG4bK479720758..Max-Forwards: 70..From: >>> <sip:PDA_User@fhjoanneu >>> m.at>;tag=1505826169..To: <sip:PDA_User@fh-joanneum.at>..Call-ID: >>> 927318080- >>> 406265317-1110482780..CSeq: 1 REGISTER..Contact: >>> <sip:PDA_User@10.0.0.3>.. >>> Content-Length: 0..User-Agent: SIP .NET 1.0 evaluation version, >>> www.independentsoft.com.... >>> # >>> U 10.0.0.11:5060 -> 10.0.0.3:5060 >>> SIP/2.0 478 Unresolvable destination (478/TM)..Via: SIP/2.0/UDP >>> 10.0.0.3:5060;branch=z9hG4bK479720758..From: <sip:PDA_User@fhjoanneum. >>> at>;tag=1505826 >>> 169..To: >>> <sip:PDA_User@fh-joanneum.at>;tag=589230a54cd08b3768529724501fae28- >>> 2449..Call-ID: 927318080-406265317-1110482780..CSeq: 1 >>> REGISTER..Server: S >>> ip EXpress router (0.10.99-dev35-pa-4.1 (i386/linux))..Content-Length: >>> 0..Warning: 392 10.0.0.11:5060 "Noisy feedback tells: pid=8941 >>> req_src_ip=10.0 >>> .0.3 req_src_port=5060 in_uri=sip:PDA_User@fh-joanneum.at >>> out_uri=sip:PDA_User@fh-joanneum.at via_cnt==1".... >>> # >>> U 10.0.0.11:5060 -> 10.0.0.3:5060 >>> SIP/2.0 500 I'm terribly sorry, server error occurred (1/SL)..Via: >>> SIP/2.0/UDP >>> 10.0.0.3:5060;branch=z9hG4bK479720758..From: <sip:PDA_User@fh-joanneum. >>> at>;tag=1505826169..To: <sip:PDA_User@fhjoanneum. >>> at>;tag=56a704c9068c5b1b9228b761fe5fb2cc.2449..Call-ID: 927318080- >>> 406265317-1110482780..CSeq: 1 REGI >>> STER..Server: Sip EXpress router (0.10.99-dev35-pa-4.1 >>> (i386/linux))..Content- >>> Length: 0..Warning: 392 10.0.0.11:5060 "Noisy feedback tells: pid=8941 >>> req_src_ip=10.0.0.3 req_src_port=5060 >>> in_uri=sip:PDA_User@fh-joanneum.at >>> out_uri=sip:PDA_User@fh-joanneum.at via_cnt==1" >>> >>> I hope you can help me. >>> >>> Regards, >>> Alois >>> >>> >>> _______________________________________________ >>> Serusers mailing list >>> Serusers(a)lists.iptel.org >>> http://lists.iptel.org/mailman/listinfo/serusers >>> >>> > > >

1 0

[Serusers] fr_inv_timer
by olivier.taylor 19 Jun '06

19 Jun '06

hi all, I have modparam("tm", "fr_inv_timer", 60) when a callee doesn't anwer, he often send a 487 (cancelled) before 60 seconds... It means timeout in fact or no answer... If the caller stop the call, I also get a 487... How to make the difference on a 487 generated by the caller and by the callee? It makes difference, if it's generated by the callee, I will forward the call to voicemail or another number, if it's generated by the caller, I will do nothing. When I set fr_inv_timer to 15, I always get a timeout and it's ok, but my customers dislikes that as well as the callees who needs to be better than Ben Jonhson for the 100meters :( Does exists a parameter to be send to the callee to tell him to wait 60 seconds + 1 before sending me a Cancel? Regards, Olivier

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