sr-users May 2008

sr-users@lists.kamailio.org

121 participants
203 discussions

[OpenSER-Users] Question about proxy_authenticate
by mark morreny 30 May '08

30 May '08

Hi, I am wondering if someone could help me to understand a bit more about the internal mechanism of proxy_challenge? If the UA is connecting to the server using the external ip, proxy_challenge fails, but if the UA is connecting to the server using the lan ip, proxy_challenge succeeds. What is the reason why this is happening? How does proxy_challenge work exactly? Thanks in advance for your help. Regards, Mark

2 1

[OpenSER-Users] Unable to t_relay (ERROR:tm:update_uac_dst)
by Pete Kay 30 May '08

30 May '08

Hi, After next_gw(), openser appends "64.231.23.234:5060;transport=tcp" as the domain of th ruri. When doing a t_relay with that ruri, I am getting ERROR:tm:update_uac_dst. before relay ruri = sip:86143455048@64.231.23.234:5060;transport=tcp starting to relay May 29 21:18:04 [12107] ERROR:tm:update_uac_dst: failed to fwd to af 2, proto 2 (no corresponding listening socket) May 29 21:18:04 [12107] ERROR:tm:t_forward_nonack: failure to add branches However, if I do a t_relay with ruri= "sip:86143455048@64.231.23.234<sip%3A86143455048(a)64.231.23.234>", then the call can go through. Could anyone tell me why? A workaround that I can think of is to reconstruct the ruri to get rid of the port and the "transport=tcp" with something like: rewriteuri("sip:$rU@$rd"); But, the above line gives "sip:$rU@$rd" instead of the desired " sip:86143455048@64.231.23.234 <sip%3A86143455048(a)64.231.23.234>". Is there anyway of using psuedo variable in rewriteuri? Thanks alot in advance for your help. Regards, Pete

5 4

[OpenSER-Users] Managing MSILO responses
by Saúl Ibarra 30 May '08

30 May '08

Hi all, I'm having a little trouble setting up msilo: When I send a MESSAGE to an offline user, MSILO does it's job and stores it, and when the other user gets registered, he sees the MESSAGES. But if I enable onification, by putting: modparam("msilo", "registrar", "sip:softswitch@OPENSER_IP") MSILO repplies me sayng the user is offline, but hten I can't continue sending MESSAGEs, because they will be directed to the URI indicated by the registyrar parameter instead of the original user I wanted to send the MESSAGE. I'm using Twinkle 1.2. Thanks in advance!! -- Saúl -- "Nunca subestimes el ancho de banda de un camión lleno de disketes." ---------------------------------------------------------------- http://www.saghul.net/

2 2

[OpenSER-Users] BYE not relaying properly
by Ruchir Brahmbhatt 30 May '08

30 May '08

Hi All, I have OpenSER 1.2.3(previously it was 1.2.1 but installed latest version to make sure that it is not an OpenSER bug) configured and running for following features: * Registrar * Proxy * Media proxy for NAT traversal * LCR module for PSTN termination * SEMS for voicemail * Multi-leg accounting with Radiator radius * Call forwarding using user_preferences I'm having one really strange issue. My OpenSER is configured to listen on particular IP address say 1.2.3.4. I've added alias for the domain name say voip.domain.com. User agent register to OpenSER using voip.domain.com as a proxy. They can call each other & pstn. I'm using Media Proxy for handling media in case of clients behind NAT. Audio & signaling seems to be working fine in case of internal and pstn calling. I have configured call forwarding unconditional, no answer & busy. In case of unconditional call forwarding, audio and signaling works fine. But when I test call forwarding on no answer or busy, audio is proper but signaling doesn't work properly. Specially BYE. Here is my setup: * 3 users configured; 1000, 2000 & 3000. * 2000 has no answer forwarding to pstn number. * 3000 has busy forwarding to 2000 If 1000 calls 2000 and 2000 doesn't pickup the phone in 30 seconds(configured using fr_inv_timer param of tm module), the pstn number is pushed in request uri and request is sent to gateway for pstn termination. Audio works fine. If caller(1000) hangs up, the callee is hung up properly. However if callee (pstn number) hangs up the call, the caller doesn't receive the BYE message and hence stays connected. Media Proxy session is closed properly but in OpenSER, BYE request is not sent to caller but keeps looping in OpenSER instead. I have several doubts about this issue. One thing is that the pstn gateway is sending BYE to OpenSER IP address instead of domain name. I know this kind of problem can occur if we haven't configured alias parameter properly. Reference: http://www.openser.org/mos/view/-OpenSER-Installation-Notes/ (Section 4. Troubleshooting) I have added ip and domain in domain table as well but still no change. I've been facing this issue since several days and still not able to solve. I've done many OpenSER setups but having such issue for the first time. I've compared the OpenSER config file to my older setups but it seems proper. Can anyone please guide me in correct direction? Thanks, Ruchir Brahmbhatt

1 2

[OpenSER-Users] Can openser auto-retry if a call fails?
by Pete Kay 29 May '08

29 May '08

Hi, I know this kind of function exists in Asterisk, but I want to know if Openser can do it as well. Let's say there are two fail-over numbers(DID-b,DID-c) that associates with a DID(DID-a), if the original number(DID-a) that get dailed can't rearch the destination due to BUSY, NO RESPONSE, etc, is there anyway of having Openser to auto-retry with the next DID(DID-b)? If the next one fails, try the next next one(DID-c). One way I can think of is to do a lookup from DB for the alias in the fail_on_route section, but if I have multiple aliases, then I will have no way of *remembering* which alias has been tried unless I store it in the DB which is not a good solution. I am wondering if there any other way of doing it? Thanks in advance for all your kind suggestion. Regards, Pete

4 6

[OpenSER-Users] OPENSER Dinner Berlin, May 28
by Daniel-Constantin Mierla 29 May '08

29 May '08

Hello, bound to Asterisk Tag (http://www.asterisk-tag.org) and Linux Tag (http://www.linuxtag.org) events, Henning Westerholt and I will take care of an OPENSER group meeting in Berlin, Germany, May 28 at 20:00. The place is a small brewery next to Chartlottenburg Castle in Berlin, named Lusinen Brau, the website: http://www.luisenbraeu.com/ Organized in same idea of casual community meeting, everybody is welcome to join at any time. It is recommended to contact me or Henning to announce your participation so you got your seat reserved. Cheers, Daniel -- http://www.asipto.com

2 1

[OpenSER-Users] t_relay() issue when bad host name
by Iñaki Baz Castillo 29 May '08

29 May '08

Hi, perhaps I missing something but AFAIK if I do: rewritehostport("kk.kkkkkkkkkkaaa.bad"); append_branch(); xlog("L_INFO", "1111111111\n"); if (!t_relay()) { xlog("L_ERROR","222222222222\n"); } xlog("L_ERROR","3333333333\n"); Then, since "kk.kkkkkkkkkkaaa.bad" is a non existing domain I expect to see "222222222" because t_relay should reply a negative value: -4 bad destination (unresolvable address) But the fact is that I don't see that "2222222222", neither "3333333333" but this error: ---------- May 29 10:38:32 [16795] CRITICAL:core:mk_proxy: could not resolve hostname: "kk.kkkkkkkkkkaaa.bad" May 29 10:38:32 [16795] ERROR:tm:uri2proxy: bad host name in URI <sip:number_doesnt_exist@kk.kkkkkkkkkkaaa.new;transport=UDP;user=phone> May 29 10:38:32 [16795] ERROR:tm:t_forward_nonack: failure to add branches ----------- Why? Thanks a lot. -- Iñaki Baz Castillo ibc(a)in.ilimit.es

2 2

[OpenSER-Users] Variables in regular expression
by Yazid Hadj Said 29 May '08

29 May '08

Hi Can I use AVP variables in regular expression? regards Yazid.

2 1

[OpenSER-Users] presence module - force subscription termination
by Sigrid Thijs 29 May '08

29 May '08

Hi, is it possible to terminate all presence subscriptions for a certain presentity through the current config script (1.3.x branch)? Or is there another easy way to accomplish this, without modifying the authorization rules? kind regards, Sigrid

2 1

[Serusers] Presence-rule handling in SER2.0
by pravin.swami＠wipro.com 29 May '08

29 May '08

Dear All, We are having problems with presence-rules handling of SER 2.0 Presence Server. +------+ +----------+ +------+ | | | Presence | | | | UE1 |--------------| Server |--------------| UE2 | | | | (PS) | | | +------+ +----------+ +------+ 1. UE1 & UE2 subscribe to "watcher-info". 2. UE1 SUBSCRIBEs to UE2's "presence" information. 3. PS sends info winfo-NOTIFY to UE2 (with UE1 status as pending). 4. UE2 fetches its presence-rules.xml document(from path /var/simulated-xcap-root/pres-rules/users/UE2/presence-rules.xml) 5. UE2 updates presence-rules.xml by adding UE1 into ALLOWLIST section & PUTs the document back to PS. 6. User changes presence status at UE2. UE2 sends PUBLISH request to PS. At this stage, PS should trigger presence NOTIFY to UE1. This isn't happening. (Another thing we observe is: Everytime watcher subscription is refreshed, UE2 receives NOTIFY with UE1 status as pending) Are we missing something in the above callflow? Should UE2 send any SIP/HTTP request after HTTP PUT presence-rules.xml ? Are we missing something when building presence-rules.xml ? We have modified the ser.cfg for presence authorization as per ser presence Handbook. modparam("pa", "auth", "xcap") modparam("xcap", "xcap_root", "http://localhost/xcap-root") Should I make any more changes to ser.cfg We have attached the ser.cfg & presence-rules.xml file that we are using. Please help us in solving this problem. Regards, -Pravin Please do not print this email unless it is absolutely necessary. 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

1 0

← Newer
1
2
3
4
5
6
7
...
21
Older →

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 May 2008