sr-users November 2008

sr-users@lists.kamailio.org

97 participants
171 discussions

[Serusers] Problem with SIP Identity
by jerome.herve＠orange-ftgroup.com 07 Nov '08

07 Nov '08

Hello everyone, I'm currently working on the implementation of RFC4474 in SER. I didn't manage to set up the auth_identity module in SER. Is there someone able to tell me what do I have to write in ser.cfg to make this possible? An example of an entire ser.cfg will be great. I hope you will help me. Thanks & regards, Jérôme HERVE tél. 02 96 05 27 41 mob. 06 76 15 18 49

2 1

[Kamailio-Users] $du has no effect in failure route
by jh＠tutpro.com 07 Nov '08

07 Nov '08

i have in failure route: t_on_branch("0"); $du = "sip:127.0.0.1:5070"; xlog("L_INFO", "Pseudo variable du has value <$du>\n"); t_relay("0x01"); and i get to syslog: Nov 6 16:33:15 test /usr/sbin/kamailio[22539]: Pseudo variable du has value <sip:127.0.0.1:5070> but wireshark shows that the invite is sent according to uri host of the branch added in failure route and not to 127.0.0.1:5070. is this a bug or is it so that $du is not supposed to have any effect in … [View More]

3 3

[Kamailio-Users] Kamailio + eyebeam + TLS
by paulo leonardo 07 Nov '08

07 Nov '08

Hi list, I have a litle problem, i would like to setup eyebeam with kamailio using TLS, but i always get *Registration error: 503 - certificate validation failure* =( !! I read the README of TLS. How certificate (.crt) i need to install in eyebeam? # kamailio -V ------------------------------------------------------------------------------------------- version: kamailio 1.4.1-tls (i386/linux) flags: STATS: Off, USE_IPV6, USE_TCP,* USE_TLS*, DISABLE_NAGLE, USE_MCAST, SHM_MEM, SHM_MMAP, … [View More]

2 1

Re: [Kamailio-Users] Remote-Party-ID header
by ingdavidcespedes＠cable.net.co 07 Nov '08

07 Nov '08

2 1

Re: [Kamailio-Users] CANCEL and 487 Request Terminated
by ingdavidcespedes＠cable.net.co 06 Nov '08

06 Nov '08

I think that's the way it should be. First it receive 487 from SBC and immediately it responds it to SBC with the ACK. Then it passes the 487 to the UAC and receive the ACK, that's all. It doesn't have to forward that last ACK to the SBC. ----- Mensaje original ----- De: Krom <kyle.romulas(a)gmail.com> Fecha: Jueves, Noviembre 6, 2008 4:06 pm Asunto: Re: [Kamailio-Users] CANCEL and 487 Request Terminated > My apologies for the drawing. Openser is receiving the 487 from the > SBC, … [View More]ACKing back to the SBC and then passing the 487 to the UAC and > the the UAC ACK's back to Openser. At which time the error occurs > because the ACK will not be forwarded since it already ACK'd for the > 487 to the SBC. > > -Kyle > > On Thu, Nov 6, 2008 at 2:42 PM, <ingdavidcespedes(a)cable.net.co> > wrote:> The final 487 should go from openser to UAC, not from SBC > to UAC. That's why the final ACK is getting lost, because it was > allready ACK'd by openser. > > > > ----- Mensaje original ----- > > De: Krom <kyle.romulas(a)gmail.com> > > Fecha: Jueves, Noviembre 6, 2008 1:18 pm > > Asunto: Re: [Kamailio-Users] CANCEL and 487 Request Terminated > > > >> Klaus, > >> > >> Some additional information. After viewing a trace I can see > that the > >> error is being generated from the last ACK received from the UAC. > >> OpenSER/Kamailio is ACK'ing to the 487 from the PSTN provider > and then > >> relaying the 487 to the UAC which in turn ACK's back. It is the > last>> ACK from the UAC that is getting the error on t_relay. I > can assume > >> because the ACK to the 487 was already sent by OpenSER/Kamailio > to the > >> PSTN upon receiving the initial 487. Something in the script I can > >> change to prevent this or just ignore the error and move on. :-) > >> > >> UAC OSER SBC > >> > >> CANCEL ---> | > >> > >> CANCEL ---> | > >> > >> <--- 200 canceling > >> > >> | <--- 200 OK > >> > >> | <--- 487 Request Terminated > >> > >> ACK ---> > >> > >> <--- 487 Reqest Terminated > >> > >> ACK ---> | > >> > >> > >> Regards, > >> -Kyle > >> > >> > >> On Thu, Nov 6, 2008 at 9:05 AM, Krom <kyle.romulas(a)gmail.com> > wrote:>> > Klaus, > >> > > >> > Thank you for the reply and the link. The link help in > checking my > >> > work. My script is very simple and even checking against the > >> compiled> scripted from sipwise.com the error persists. > >> > > >> > Here is my CANCEL and ACK handling. > >> > if(is_method("CANCEL") || is_method("ACK")) { > >> > if(t_check_trans()) { > >> > if(!t_relay()) sl_reply_error(); > >> > } > >> > exit; > >> > } > >> > > >> > Here is my route block for PSTN calls. > >> > route[4] > >> > { > >> > if (!load_gws()) { > >> > sl_send_reply("500", "Server Internal Error"); > >> > exit; > >> > } > >> > if (!next_gw()) { > >> > sl_send_reply("503", "Service Unavailable"); > >> > exit; > >> > } > >> > t_on_failure("2"); > >> > t_relay("udp:<IPADDR>:5060"); # Relay to the Session Boarder > >> Controller> > >> > exit; > >> > > >> > } > >> > > >> > Here is my failure route. > >> > failure_route[2] > >> > { > >> > > >> > if(t_check_status("408|500|503")) { > >> > if (!next_gw()) { > >> > t_reply("503", "Service Unavailable"); > >> > exit; > >> > } > >> > t_on_failure("2"); > >> > t_relay("udp:<IPADDR>:5060"); # Relay to the Session Boarder > >> Controller> } > >> > > >> > exit; > >> > > >> > } > >> > > >> > Any thoughts or errors you see? > >> > > >> > Regards. > >> > > >> > > >> > On Thu, Nov 6, 2008 at 3:56 AM, Klaus Darilion > >> > <klaus.mailinglists(a)pernau.at> wrote: > >> >> looks like the ACK is miss-routed. > >> >> > >> >> Usually calling t_relay() for ACK is sufficient (take a look at > >> the config > >> >> file generated with sipwise.com wizard for correct CANCEL/ACK > >> handling.>> > >> >> regards > >> >> klaus > >> >> > >> >> Krom schrieb: > >> >>> > >> >>> Et al, > >> >>> > >> >>> Version: openser-1.1.1-notls > >> >>> > >> >>> I am receiving the following after calling t_relay within the > >> default>>> route block. > >> >>> ERROR: t_newtran: transaction already in process 0xb0139638 > >> >>> WARNING:sl:sl_send_reply: I won't send a reply for ACK!! > >> >>> WARNING: script writer didn't release transaction > >> >>> > >> >>> This is happening when a downstream UAC dials outbound to the > >> PSTN and > >> >>> then terminates the call prior to the far ending answering. > >> >>> > >> >>> UAC send a CANCEL to the proxy, the proxy responds to the UAC > >> with a > >> >>> '200 canceling' and forwards the CANCEL to the PSTN provider. > >> >>> The PSTN provider sends 487 Request Terminated to the proxy and > >> the>>> proxy sends it on to the UAC. UAC responds with an ACK to > >> the proxy. > >> >>> > >> >>> Is this an issue? How do I handle this dialog withou > getting the > >> >>> t_relay error message? > >> >>> > >> >>> > >> >> > >> > > >> > > >> > > >> > -- > >> > Thanks, > >> > -- Kyle > >> > > >> > >> > >> > >> -- > >> Thanks, > >> -- Kyle > >> > >> _______________________________________________ > >> Users mailing list > >> Users(a)lists.kamailio.org > >> http://lists.kamailio.org/cgi-bin/mailman/listinfo/users > >> > > > > > > > > -- > Thanks, > -- Kyle > [View Less]

2 1

Re: [Kamailio-Users] CANCEL and 487 Request Terminated
by Krom 06 Nov '08

06 Nov '08

My apologies for the drawing. Openser is receiving the 487 from the SBC, ACKing back to the SBC and then passing the 487 to the UAC and the the UAC ACK's back to Openser. At which time the error occurs because the ACK will not be forwarded since it already ACK'd for the 487 to the SBC. -Kyle On Thu, Nov 6, 2008 at 2:42 PM, <ingdavidcespedes(a)cable.net.co> wrote: > The final 487 should go from openser to UAC, not from SBC to UAC. That's why the final ACK is getting lost, because … [View More]it was allready ACK'd by openser. > > ----- Mensaje original ----- > De: Krom <kyle.romulas(a)gmail.com> > Fecha: Jueves, Noviembre 6, 2008 1:18 pm > Asunto: Re: [Kamailio-Users] CANCEL and 487 Request Terminated > >> Klaus, >> >> Some additional information. After viewing a trace I can see that the >> error is being generated from the last ACK received from the UAC. >> OpenSER/Kamailio is ACK'ing to the 487 from the PSTN provider and then >> relaying the 487 to the UAC which in turn ACK's back. It is the last >> ACK from the UAC that is getting the error on t_relay. I can assume >> because the ACK to the 487 was already sent by OpenSER/Kamailio to the >> PSTN upon receiving the initial 487. Something in the script I can >> change to prevent this or just ignore the error and move on. :-) >> >> UAC OSER SBC >> >> CANCEL ---> | >> >> CANCEL ---> | >> >> <--- 200 canceling >> >> | <--- 200 OK >> >> | <--- 487 Request Terminated >> >> ACK ---> >> >> <--- 487 Reqest Terminated >> >> ACK ---> | >> >> >> Regards, >> -Kyle >> >> >> On Thu, Nov 6, 2008 at 9:05 AM, Krom <kyle.romulas(a)gmail.com> wrote: >> > Klaus, >> > >> > Thank you for the reply and the link. The link help in checking my >> > work. My script is very simple and even checking against the >> compiled> scripted from sipwise.com the error persists. >> > >> > Here is my CANCEL and ACK handling. >> > if(is_method("CANCEL") || is_method("ACK")) { >> > if(t_check_trans()) { >> > if(!t_relay()) sl_reply_error(); >> > } >> > exit; >> > } >> > >> > Here is my route block for PSTN calls. >> > route[4] >> > { >> > if (!load_gws()) { >> > sl_send_reply("500", "Server Internal Error"); >> > exit; >> > } >> > if (!next_gw()) { >> > sl_send_reply("503", "Service Unavailable"); >> > exit; >> > } >> > t_on_failure("2"); >> > t_relay("udp:<IPADDR>:5060"); # Relay to the Session Boarder >> Controller> >> > exit; >> > >> > } >> > >> > Here is my failure route. >> > failure_route[2] >> > { >> > >> > if(t_check_status("408|500|503")) { >> > if (!next_gw()) { >> > t_reply("503", "Service Unavailable"); >> > exit; >> > } >> > t_on_failure("2"); >> > t_relay("udp:<IPADDR>:5060"); # Relay to the Session Boarder >> Controller> } >> > >> > exit; >> > >> > } >> > >> > Any thoughts or errors you see? >> > >> > Regards. >> > >> > >> > On Thu, Nov 6, 2008 at 3:56 AM, Klaus Darilion >> > <klaus.mailinglists(a)pernau.at> wrote: >> >> looks like the ACK is miss-routed. >> >> >> >> Usually calling t_relay() for ACK is sufficient (take a look at >> the config >> >> file generated with sipwise.com wizard for correct CANCEL/ACK >> handling.>> >> >> regards >> >> klaus >> >> >> >> Krom schrieb: >> >>> >> >>> Et al, >> >>> >> >>> Version: openser-1.1.1-notls >> >>> >> >>> I am receiving the following after calling t_relay within the >> default>>> route block. >> >>> ERROR: t_newtran: transaction already in process 0xb0139638 >> >>> WARNING:sl:sl_send_reply: I won't send a reply for ACK!! >> >>> WARNING: script writer didn't release transaction >> >>> >> >>> This is happening when a downstream UAC dials outbound to the >> PSTN and >> >>> then terminates the call prior to the far ending answering. >> >>> >> >>> UAC send a CANCEL to the proxy, the proxy responds to the UAC >> with a >> >>> '200 canceling' and forwards the CANCEL to the PSTN provider. >> >>> The PSTN provider sends 487 Request Terminated to the proxy and >> the>>> proxy sends it on to the UAC. UAC responds with an ACK to >> the proxy. >> >>> >> >>> Is this an issue? How do I handle this dialog withou getting the >> >>> t_relay error message? >> >>> >> >>> >> >> >> > >> > >> > >> > -- >> > Thanks, >> > -- Kyle >> > >> >> >> >> -- >> Thanks, >> -- Kyle >> >> _______________________________________________ >> Users mailing list >> Users(a)lists.kamailio.org >> http://lists.kamailio.org/cgi-bin/mailman/listinfo/users >> > > -- Thanks, -- Kyle [View Less]

1 0

[Kamailio-Users] CANCEL and 487 Request Terminated
by Krom 06 Nov '08

06 Nov '08

Et al, Version: openser-1.1.1-notls I am receiving the following after calling t_relay within the default route block. ERROR: t_newtran: transaction already in process 0xb0139638 WARNING:sl:sl_send_reply: I won't send a reply for ACK!! WARNING: script writer didn't release transaction This is happening when a downstream UAC dials outbound to the PSTN and then terminates the call prior to the far ending answering. UAC send a CANCEL to the proxy, the proxy responds to the UAC with a '200 … [View More]

2 3

[Serusers] Assistance with SER setup
by Scott Seltzer 06 Nov '08

06 Nov '08

Hello, my name is Scott Seltzer, from ConnectMe (www.connectmevoice.com <http://www.connectmevoice.com/> ) Connectme is currently in the process of setting up SER for use as a Proxy and Registrar. We will ultimately need to be able to use an API to setup new SIP URIs for each new customer. We are not familiar at all with SER, and would like to find out what support options there may be out there. We would also be interested in using some consulting services to help get us started,… [View More]

1 0

[Serusers] FW: Support for SER setup
by Scott Seltzer 06 Nov '08

06 Nov '08

Hello, my name is Scott Seltzer, from ConnectMe (www.connectmevoice.com <http://www.connectmevoice.com> ) Connectme is currently in the process of setting up SER for use as a Proxy and Registrar. We will ultimately need to be able to use an API to setup new SIP URIs for each new customer. We are not familiar at all with SER, and would like to find out what support options there may be out there. We would also be interested in using some consulting services to help get us started, … [View More]

1 0

[Kamailio-Users] two endpoints
by Alex R.S.M 06 Nov '08

06 Nov '08

Hi, If ENUM lookup returns 2 destinations, does kamailio fork the message and send two INVITE? What function can be used to force kamailio to fork a message? Regards, Alex _________________________________________________________________ Windows Live Hotmail now works up to 70% faster. http://windowslive.com/Explore/Hotmail?ocid=TXT_TAGLM_WL_hotmail_acq_faster…

2 1

← Newer
1
...
11
12
13
14
15
16
17
18
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 November 2008