sr-users February 2017

sr-users@lists.kamailio.org

74 participants
100 discussions

Fosdem 2017 dinner
by Daniel-Constantin Mierla 04 Feb '17

04 Feb '17

Hello, the dinner at Fosdem 2017 is planned to start at 20:00, on Saturday, Feb 4, 2017. The address is: Le Pickwick Avenue Adolphe Buyl 79 1050 Ixelles, Belgium * https://en.yelp.be/biz/le-pickwick-ixelles The place is nearby Fosdem location. If you announced the intention to participate at the dinner before Feb 1, 2017, your seat is reserved. If you did it afterwards, please contact me during RTC Devroom to confirm the availability of the seats. Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - Mar 6-8 (Europe) and Mar 20-22 (USA) - www.asipto.com Kamailio World Conference - May 8-10, 2017 - www.kamailioworld.com

1 0

Spurious dialog timeouts
by Pranathi Venkatayogi 03 Feb '17

03 Feb '17

Hi, I have two kamailio proxies between the customer and agent. Cust -> proxy1 -> proxy2 -> agent. The dialogs are successfully established and remain undeleted within the customer / agent client. However in Proxy2 I am seeing spurious dialog timeout. I am attaching kamailio log trace below. Also attached is the siptrace on the agent/customer side. Question: How is this dlg_ontimeout() generated despite dialog being successfully established and undelete? How to avoid it. Kamailio (proxy2) log: 7719 Feb 3 21:41:20 labsip00 /usr/sbin/kamailio[11323]: exec: *** cfgtrace:local_route=[dialog:end] c=[//etc/kamailio//routing.cfg] l=490 a=16 n=if 7720 Feb 3 21:41:20 labsip00 /usr/sbin/kamailio[11323]: exec: *** cfgtrace:local_route=[dialog:end] c=[//etc/kamailio//routing.cfg] l=481 a=24 n=is_known_dlg 7721 Feb 3 21:41:20 labsip00 /usr/sbin/kamailio[11323]: exec: *** cfgtrace:local_route=[dialog:end] c=[//etc/kamailio//routing.cfg] l=482 a=63 n=assign 7722 Feb 3 21:41:20 labsip00 /usr/sbin/kamailio[11323]: exec: *** cfgtrace:local_route=[dialog:end] c=[//etc/kamailio//routing.cfg] l=489 a=16 n=if 7723 Feb 3 21:41:20 labsip00 /usr/sbin/kamailio[11323]: exec: *** cfgtrace:local_route=[dialog:end] c=[//etc/kamailio//routing.cfg] l=485 a=26 n=xlog 7724 Feb 3 21:41:20 labsip00 /usr/sbin/kamailio[11323]: INFO: <script>: Translation: Dialog ended for sip:agent2@translation.sms-test.cyracom.com. Marking free 7725 Feb 3 21:41:20 labsip00 /usr/sbin/kamailio[11323]: exec: *** cfgtrace:local_route=[dialog:end] c=[//etc/kamailio//routing.cfg] l=486 a=63 n=assign 7726 Feb 3 21:41:20 labsip00 /usr/sbin/kamailio[11323]: exec: *** cfgtrace:local_route=[dialog:end] c=[//etc/kamailio//routing.cfg] l=487 a=63 n=assign 7727 Feb 3 21:41:20 labsip00 /usr/sbin/kamailio[11323]: WARNING: dialog [dlg_handlers.c:1515]: dlg_ontimeout(): timeout for dlg with CallID '1478097bad2847cfaa60a768d76044b0' and tags '57315e78d6514251876bd5a9e32347d2' '00a1eac150f04e2592527372412f059e' 7728 Feb 3 21:41:20 labsip00 /usr/sbin/kamailio[11323]: exec: *** cfgtrace:local_route=[dialog:end] c=[//etc/kamailio//routing.cfg] l=490 a=16 n=if 7729 Feb 3 21:41:20 labsip00 /usr/sbin/kamailio[11323]: exec: *** cfgtrace:local_route=[dialog:end] c=[//etc/kamailio//routing.cfg] l=481 a=24 n=is_known_dlg 7730 Feb 3 21:41:20 labsip00 /usr/sbin/kamailio[11323]: exec: *** cfgtrace:local_route=[dialog:end] c=[//etc/kamailio//routing.cfg] l=482 a=63 n=assign 7731 Feb 3 21:41:20 labsip00 /usr/sbin/kamailio[11323]: exec: *** cfgtrace:local_route=[dialog:end] c=[//etc/kamailio//routing.cfg] l=489 a=16 n=if 7732 Feb 3 21:41:20 labsip00 /usr/sbin/kamailio[11323]: exec: *** cfgtrace:local_route=[dialog:end] c=[//etc/kamailio//routing.cfg] l=485 a=26 n=xlog 7733 Feb 3 21:41:20 labsip00 /usr/sbin/kamailio[11323]: INFO: <script>: Translation: Dialog ended for sip:agent5@translation.sms-test.cyracom.com. Marking free 7734 Feb 3 21:41:20 labsip00 /usr/sbin/kamailio[11323]: exec: *** cfgtrace:local_route=[dialog:end] c=[//etc/kamailio//routing.cfg] l=486 a=63 n=assign 7735 Feb 3 21:41:20 labsip00 /usr/sbin/kamailio[11323]: exec: *** cfgtrace:local_route=[dialog:end] c=[//etc/kamailio//routing.cfg] l=487 a=63 n=assign 7736 Feb 3 21:41:20 labsip00 /usr/sbin/kamailio[11323]: WARNING: dialog [dlg_handlers.c:1515]: dlg_ontimeout(): timeout for dlg with CallID '04d924dc160d4e0c9366d4699f579793' and tags '9b107772c82148c0a09182dc86804c51' '44b0a200438a42f8a6ac931ed72f795a' Thanks for your input, Pranathi

1 0

FreeSWITCH at FOSDEM, SIP and WebRTC Load Balancing and High Availability
by Giovanni Maruzzelli 03 Feb '17

03 Feb '17

See you all, in person or in the intertube, at: https://fosdem.org/2017/schedule/event/freeswitch/ sent from mobile cell: +39 347 266 56 18 Giovanni Maruzzelli OpenTelecom.IT

1 0

Websocket TLS Issue
by Jade SZ 03 Feb '17

03 Feb '17

Hi Guys, I am trying to setup the following flow: Browser >> WSS >> HA Proxy >>> WSS >> Kamailio But getting TLS errors in Kamailio logs: *[29634]: ERROR: <core> [tcp_read.c:1321]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f68ebe872b0 r: 0x7f68ebe87330* *[29631]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number* Browser <-----wss---->Kamailio works fine with same certs. Both HA Proxy and Kamilio are installed on separate servers, hosting on same port with different domain. Kamailio tls.conf has method = TLSv1 *@HA Proxy:* openssl s_client -connect HA-PROXY-DOMAIN:*10443* SSL-Session: Protocol : TLSv1.2 *@Kamailio :* openssl s_client -connect KAMAILIO-DOMAIN:*10443* SSL-Session: Protocol : TLSv1 So I made HA Proxy to be on TLSv1 "ssl-default-bind-options force-tlsv10" But still I get the same TLS error in Kamailio. *HA Proxy config looks like:* *frontend public* * bind *:10443 ssl crt /etc/haproxy/certs/cert.pem* * acl is_websocket hdr_end(host) -i m1.some-domain.com <http://m1.some-domain.com>* * use_backend wss if is_websocket* * default_backend wss* *backend wss* * timeout server 600s* * server ws1 k1.some-domain.com:10443 <http://k1.some-domain.com:10443>* * server ws1 k2.some-domain.com:10443 <http://k2.some-domain.com:10443>* Need some direction, thanks in advance. Regards, Jade

4 4

id column i tables
by Kristian F. Høgh 02 Feb '17

02 Feb '17

Hi list, We provision our kamailio database from an external system. In the future we would like to provision from two different systems. To prevent the two systems from touching each others data, we would like to create views from the two tables. provision system 1 would write to table1 provision system 2 would write to table2 kamailio will read a view over the two tables. The tables we will create views over are: - address - aliases - dispatcher - uri - usr_preferences Now to my question :-) Does kamailio use the id field in any of the tables above? The id's are auto-incremented, and we might get conflicts between table1 and table2 *Kristian Høgh* Telefon: 4422 8822 support(a)uni-tel.dk[1] Gydevang 19 | 3450 Allerød www.uni-tel.dk [2] -------- [1] mailto:support@uni-tel.dk [2] http://www.uni-tel.dk

2 2

Disabling DNS SRV records checks
by Ahmed Fouad 01 Feb '17

01 Feb '17

Hi, I'm running kamailio version 4.1 and having the following DNS related configuration use_dns_failover = off dns_try_naptr = no dns_udp_pref = -1 dns_try_ipv6 = off dns_retr_time=1 dns_retr_no=1 dns_servers_no=1 dns_use_search_list=no But still am seeing SRV record checks for my domains which I like to completely disable these checks and only use A records only. x.x.x.x.57828 > 8.8.8.8.53: 7417+ SRV? _sip._udp.subdomain.com 8.8.8.8.53 > x.x.x.x.57828: 7417 NXDomain 0/1/0 (129) I can't find a DNS option to disable SRV checks. Can you please advise ?

2 3

could not make ul_rm_contact work
by Aqs Younas 01 Feb '17

01 Feb '17

Greetings list, I am trying to remove a specific contact from memory but always resulted in vain. root@debian:/usr/local/kamailio/sbin# ./kamctl ul show Domain:: location table=1024 records=1 max_slot=1 AOR:: 1040(a)192.168.0.101 Contact:: sip:1040@192.168.0.102:36619;rinstance=1dfaed088d873a18;transport=tcp Q= Expires:: 2416 Callid:: _3595KDc1PinhUGFpSf4Dg.. Cseq:: 2 User-agent:: Z 3.9.32144 r32121 State:: CS_SYNC Flags:: 0 Cflag:: 0 Socket:: tcp:192.168.0.101:5060 Methods:: 5087 Ruid:: uloc-58911db0-f45-1 Reg-Id:: 0 Last-Keepalive:: 1485905402 Last-Modified:: 1485905402 . /kamctl fifo ul_rm_contact location 1040(a)191.168.0.101 sip:1040@192.168.0.102:36619;rinstance=1dfaed088d873a18;transport=tcp 404 AOR not found Tried another command root@debian:/usr/local/kamailio/sbin# ./kamctl fifo ul_rm location 1040(a)192.168.0.101 root@debian:/usr/local/kamailio/sbin# ./kamctl ul show Domain:: location table=1024 records=1 max_slot=1 AOR:: 1040(a)192.168.0.101 Contact:: sip:1040@192.168.0.102:36619;rinstance=1dfaed088d873a18;transport=tcp Q= Expires:: deleted Callid:: _3595KDc1PinhUGFpSf4Dg.. Cseq:: 2 User-agent:: Z 3.9.32144 r32121 State:: CS_SYNC Flags:: 0 Cflag:: 0 Socket:: tcp:192.168.0.101:5060 Methods:: 5087 Ruid:: uloc-58911db0-f45-1 Reg-Id:: 0 Last-Keepalive:: 1485905402 Last-Modified:: 1485905402 And this. . /kamctl ul rm 1040(a)192.168.0.1 sip:1040@192.168.0.102:36619 ;rinstance=1dfaed088d873a18;transport=tcp 404 AOR not found Can someone help me know to remove a contact from memory? Any pointer is much appreciated. Best Regards.

2 3

sdp_with_transport
by M. Salman 01 Feb '17

01 Feb '17

Hi Guys, Just wanted to clarify the following case: what should be result of sdp_with_transport("RTP/SAVPF") on line: m=audio 10231 UDP/TLS/RTP/SAVPF 111 103 104 9 0 8 106 105 13 126 I am having a weird behavior for two different versions of Kamailio. I hope I am doing something wrong. kamailio 4.3.2 => sdp_with_transport("RTP/SAVPF") = true kamailio 4.4.5 => sdp_with_transport("RTP/SAVPF") = false -- Regards M. Salman VoIP Professional

3 2

Re: [SR-Users] sr-users Digest, Vol 140, Issue 30
by Andrew Miller 01 Feb '17

01 Feb '17

Is it too late to request a place for the meal at FOSDEM? I would love to come. Andy Miller On 30 Jan 2017 11:00, <sr-users-request(a)lists.sip-router.org> wrote: > Send sr-users mailing list submissions to > sr-users(a)lists.sip-router.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users > or, via email, send a message with subject or body 'help' to > sr-users-request(a)lists.sip-router.org > > You can reach the person managing the list at > sr-users-owner(a)lists.sip-router.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of sr-users digest..." > > > Today's Topics: > > 1. Diversion Header - relay messed up (Roman Dissauer) > 2. Re: dlg_set_timeout bye to websockets client (Switch168) > 3. Presence Module do not load db_url (Vu. Minh Cao) > 4. Re: FOSDEM 2017 (Giacomo Vacca) > 5. Re: Replace old registration record with new one while > keeping single AOR per contact (Federico Cabiddu) > 6. Re: Replace old registration record with new one while > keeping single AOR per contact (Aqs Younas) > 7. Re: mhomed opened sockets (Diego Nadares) > 8. Re: [sr-dev] FOSDEM 2017 (Daniel-Constantin Mierla) > 9. Re: FOSDEM 2017 (Ivan Todorov) > 10. Re: [Kamailio-Business] [sr-dev] FOSDEM 2017 (Alexandr Dubovikov) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 29 Jan 2017 18:42:23 +0100 > From: Roman Dissauer <roman(a)dissauer.net> > To: sr-users(a)lists.sip-router.org > Subject: [SR-Users] Diversion Header - relay messed up > Message-ID: <DB3FC45E-ACCE-426E-B662-031909F6BA40(a)dissauer.net> > Content-Type: text/plain; charset=utf-8 > > When I get an INVITE with Diversion Header the Request is forwarded > without Diversion Header and the Request User is taken from Diversion User. > Problem is that on the Destination Host I cannot get original Request User > what is the intended destination! > Is this intended behaviour? How can I change this behaviour? > > I already tried to delete the Diversion Header on request_route but this > didn’t change the behaviour. > > Thanks in andvance for your help! > Roman > > Here The INVITEs with x.x.x.x as Kamailio external IP and y.y.y.y as > Carrier IP > > Incoming INVITE: > > INVITE sip:+43123456789@x.x.x.x:5060 SIP/2.0. > Via: SIP/2.0/UDP y.y.y.y:5060;branch=z9hG4bK02B7871714d9345f843. > From: <sip:+43987654321@y.y.y.y>;tag=gK022ac5cb. > To: <sip:436761234567@x.x.x.x>. > Call-ID: 906143813_44460603(a)y.y.y.y. > CSeq: 28100 INVITE. > Max-Forwards: 19. > Allow: INVITE,ACK,CANCEL,BYE,REGISTER,REFER,INFO,SUBSCRIBE, > NOTIFY,PRACK,UPDATE,OPTIONS. > Accept: application/sdp, application/isup, application/dtmf, > application/dtmf-relay, multipart/mixed. > Contact: <sip:+43987654321@y.y.y.y:5060>. > P-Asserted-Identity: <sip:+43987654321@y.y.y.y:5060>. > Diversion: <sip:+436761234567@y.y.y.y:5060>;privacy=full;screen=no; > reason=unconditional; counter=1. > Supported: timer,100rel. > Session-Expires: 1800. > Min-SE: 90. > Content-Length: 260. > Content-Disposition: session; handling=required. > Content-Type: application/sdp. > ... > > > Relayed INVITE: > > INVITE sip:436761234567@x.x.x.x:5060 SIP/2.0. > Record-Route: <sip:10.23.101.1;r2=on;lr=on;ftag=gK022ac5cb>. > Record-Route: <sip:x.x.x.x;r2=on;lr=on;ftag=gK022ac5cb>. > Via: SIP/2.0/UDP 10.23.101.1;branch=z9hG4bK8582. > 4fc0216dbecafde29127db502993222c.0. > Via: SIP/2.0/UDP y.y.y.y:5060;rport=5060;branch= > z9hG4bK02B7871714d9345f843. > From: <sip:+43987654321@y.y.y.y>;tag=gK022ac5cb. > To: <sip:436761234567@x.x.x.x>. > Call-ID: 906143813_44460603(a)y.y.y.y. > CSeq: 28100 INVITE. > Max-Forwards: 18. > Allow: INVITE,ACK,CANCEL,BYE,REGISTER,REFER,INFO,SUBSCRIBE, > NOTIFY,PRACK,UPDATE,OPTIONS. > Accept: application/sdp, application/isup, application/dtmf, > application/dtmf-relay, multipart/mixed. > Contact: <sip:+43987654321@y.y.y.y:5060>. > P-Asserted-Identity: <sip:+43987654321@y.y.y.y:5060>. > Supported: timer,100rel. > Session-Expires: 1800. > Min-SE: 90. > Content-Length: 274. > Content-Disposition: session; handling=required. > ... > > > > > > > > ------------------------------ > > Message: 2 > Date: Sun, 29 Jan 2017 18:21:37 +0000 > From: Switch168 <team(a)switch168.com> > To: "Kamailio (SER) - Users Mailing List" > <sr-users(a)lists.sip-router.org>, miconda(a)gmail.com > Subject: Re: [SR-Users] dlg_set_timeout bye to websockets client > Message-ID: > <CAJ4KJRjeZT++vYWkfnY10WnkWztpVtpSV700TW0ebh > 7z+jRAEg(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hi Daniel, > > > For anyone else who might run into this issue I found > https://github.com/kamailio/kamailio/issues/85 to be related to mine. And > its a good a starting point. > > Cheers > Andrew > > > > > On Fri, Jan 27, 2017 at 10:47 AM Switch168 <team(a)switch168.com> wrote: > > > HI Daniel, > > > > modparam("dialog", "dlg_flag", 4) modparam("dialog", "send_bye", 1) > > modparam("dialog", "timeout_noreset", 1) > > > > So regular bye's by useragent i can succesfully relay to this > > <sip:6gjlmali@ec2c66jsa0ei.invalid;transport=ws> > > style of uri by using this snippet below > > > > # Handle requests within SIP dialogs > > route[WITHINDLG] { > > if(is_method("BYE")) { > > xlog("DEBUG: Received BYE"); > > route(NATDETECT); > > loose_route(); > > dlg_manage(); > > t_check_trans(); > > handle_ruri_alias(); > > rtpengine_delete(); > > route(RELAY); > > exit; > > } > > ... > > > > But the byes that are sent out by dlg_set_timeout("$var(timer)") gives > out > > error cannot resolve > > the random.uri and I don't know how to fix the bye before it get sent > out. > > > > Thanks > > Andrew > > > > > > > > > > > > > > > > > > On Fri, Jan 27, 2017 at 12:15 AM, Daniel-Constantin Mierla < > > miconda(a)gmail.com> wrote: > > > > Hello, > > > > isn't the dialog module setting the right value there? What function are > > you using to update the contact? > > > > Cheers, > > Daniel > > > > On 27/01/2017 06:01, Andrew Tan wrote: > > > > Hello, > > > > Just wondering if it's possible to intercept the bye message that > > dlg_set_timeout sends out to do some nat_helper function to fix it so the > > bye can be sent to random.invalid uris. > > > > I know there is the edge proxy outbound module but wondering if I can do > > it without. > > > > Regular bye between 2 clients i was able intercept and fix with nat > helper > > but I dont know how to fix the byes that is sent out from dlg_set_timeout > > function. > > > > Thanks in advance! > > Andrew > > > > > > > > _______________________________________________ > > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing > listsr-users@lists.sip-router.orghttp://lists.sip-router. > org/cgi-bin/mailman/listinfo/sr-users > > > > > > -- > > Daniel-Constantin Mierlawww.twitter.com/miconda -- > www.linkedin.com/in/miconda > > Kamailio Advanced Training - Mar 6-8 (Europe) and Mar 20-22 (USA) - > www.asipto.com > > Kamailio World Conference - May 8-10, 2017 - www.kamailioworld.com > > > > > > _______________________________________________ > > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list > > sr-users(a)lists.sip-router.org > > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users > > > > > > >

1 0

Re: [SR-Users] FOSDEM 2017
by Hugh Waite 01 Feb '17

01 Feb '17

Hi all, Please count me and one other in for the meal on Saturday. See you in Brussels! Hugh Waite On 30 Jan 2017 11:00 a.m., <sr-users-request(a)lists.sip-router.org> wrote: Send sr-users mailing list submissions to sr-users(a)lists.sip-router.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users or, via email, send a message with subject or body 'help' to sr-users-request(a)lists.sip-router.org You can reach the person managing the list at sr-users-owner(a)lists.sip-router.org When replying, please edit your Subject line so it is more specific than "Re: Contents of sr-users digest..." Today's Topics: 1. Diversion Header - relay messed up (Roman Dissauer) 2. Re: dlg_set_timeout bye to websockets client (Switch168) 3. Presence Module do not load db_url (Vu. Minh Cao) 4. Re: FOSDEM 2017 (Giacomo Vacca) 5. Re: Replace old registration record with new one while keeping single AOR per contact (Federico Cabiddu) 6. Re: Replace old registration record with new one while keeping single AOR per contact (Aqs Younas) 7. Re: mhomed opened sockets (Diego Nadares) 8. Re: [sr-dev] FOSDEM 2017 (Daniel-Constantin Mierla) 9. Re: FOSDEM 2017 (Ivan Todorov) 10. Re: [Kamailio-Business] [sr-dev] FOSDEM 2017 (Alexandr Dubovikov) ---------------------------------------------------------------------- Message: 1 Date: Sun, 29 Jan 2017 18:42:23 +0100 From: Roman Dissauer <roman(a)dissauer.net> To: sr-users(a)lists.sip-router.org Subject: [SR-Users] Diversion Header - relay messed up Message-ID: <DB3FC45E-ACCE-426E-B662-031909F6BA40(a)dissauer.net> Content-Type: text/plain; charset=utf-8 When I get an INVITE with Diversion Header the Request is forwarded without Diversion Header and the Request User is taken from Diversion User. Problem is that on the Destination Host I cannot get original Request User what is the intended destination! Is this intended behaviour? How can I change this behaviour? I already tried to delete the Diversion Header on request_route but this didn’t change the behaviour. Thanks in andvance for your help! Roman Here The INVITEs with x.x.x.x as Kamailio external IP and y.y.y.y as Carrier IP Incoming INVITE: INVITE sip:+43123456789@x.x.x.x:5060 SIP/2.0. Via: SIP/2.0/UDP y.y.y.y:5060;branch=z9hG4bK02B7871714d9345f843. From: <sip:+43987654321@y.y.y.y>;tag=gK022ac5cb. To: <sip:436761234567@x.x.x.x>. Call-ID: 906143813_44460603(a)y.y.y.y. CSeq: 28100 INVITE. Max-Forwards: 19. Allow: INVITE,ACK,CANCEL,BYE,REGISTER,REFER,INFO,SUBSCRIBE, NOTIFY,PRACK,UPDATE,OPTIONS. Accept: application/sdp, application/isup, application/dtmf, application/dtmf-relay, multipart/mixed. Contact: <sip:+43987654321@y.y.y.y:5060>. P-Asserted-Identity: <sip:+43987654321@y.y.y.y:5060>. Diversion: <sip:+436761234567@y.y.y.y:5060>;privacy=full;screen=no; reason=unconditional; counter=1. Supported: timer,100rel. Session-Expires: 1800. Min-SE: 90. Content-Length: 260. Content-Disposition: session; handling=required. Content-Type: application/sdp. ... Relayed INVITE: INVITE sip:436761234567@x.x.x.x:5060 SIP/2.0. Record-Route: <sip:10.23.101.1;r2=on;lr=on;ftag=gK022ac5cb>. Record-Route: <sip:x.x.x.x;r2=on;lr=on;ftag=gK022ac5cb>. Via: SIP/2.0/UDP 10.23.101.1;branch=z9hG4bK8582. 4fc0216dbecafde29127db502993222c.0. Via: SIP/2.0/UDP y.y.y.y:5060;rport=5060;branch=z9hG4bK02B7871714d9345f843. From: <sip:+43987654321@y.y.y.y>;tag=gK022ac5cb. To: <sip:436761234567@x.x.x.x>. Call-ID: 906143813_44460603(a)y.y.y.y. CSeq: 28100 INVITE. Max-Forwards: 18. Allow: INVITE,ACK,CANCEL,BYE,REGISTER,REFER,INFO,SUBSCRIBE, NOTIFY,PRACK,UPDATE,OPTIONS. Accept: application/sdp, application/isup, application/dtmf, application/dtmf-relay, multipart/mixed. Contact: <sip:+43987654321@y.y.y.y:5060>. P-Asserted-Identity: <sip:+43987654321@y.y.y.y:5060>. Supported: timer,100rel. Session-Expires: 1800. Min-SE: 90. Content-Length: 274. Content-Disposition: session; handling=required. ... ------------------------------ Message: 2 Date: Sun, 29 Jan 2017 18:21:37 +0000 From: Switch168 <team(a)switch168.com> To: "Kamailio (SER) - Users Mailing List" <sr-users(a)lists.sip-router.org>, miconda(a)gmail.com Subject: Re: [SR-Users] dlg_set_timeout bye to websockets client Message-ID: <CAJ4KJRjeZT++vYWkfnY10WnkWztpVtpSV700TW0ebh7z+jRAEg(a)mail.gmail.com> Content-Type: text/plain; charset="utf-8" Hi Daniel, For anyone else who might run into this issue I found https://github.com/kamailio/kamailio/issues/85 to be related to mine. And its a good a starting point. Cheers Andrew On Fri, Jan 27, 2017 at 10:47 AM Switch168 <team(a)switch168.com> wrote: > HI Daniel, > > modparam("dialog", "dlg_flag", 4) modparam("dialog", "send_bye", 1) > modparam("dialog", "timeout_noreset", 1) > > So regular bye's by useragent i can succesfully relay to this > <sip:6gjlmali@ec2c66jsa0ei.invalid;transport=ws> > style of uri by using this snippet below > > # Handle requests within SIP dialogs > route[WITHINDLG] { > if(is_method("BYE")) { > xlog("DEBUG: Received BYE"); > route(NATDETECT); > loose_route(); > dlg_manage(); > t_check_trans(); > handle_ruri_alias(); > rtpengine_delete(); > route(RELAY); > exit; > } > ... > > But the byes that are sent out by dlg_set_timeout("$var(timer)") gives out > error cannot resolve > the random.uri and I don't know how to fix the bye before it get sent out. > > Thanks > Andrew > > > > > > > > > On Fri, Jan 27, 2017 at 12:15 AM, Daniel-Constantin Mierla < > miconda(a)gmail.com> wrote: > > Hello, > > isn't the dialog module setting the right value there? What function are > you using to update the contact? > > Cheers, > Daniel > > On 27/01/2017 06:01, Andrew Tan wrote: > > Hello, > > Just wondering if it's possible to intercept the bye message that > dlg_set_timeout sends out to do some nat_helper function to fix it so the > bye can be sent to random.invalid uris. > > I know there is the edge proxy outbound module but wondering if I can do > it without. > > Regular bye between 2 clients i was able intercept and fix with nat helper > but I dont know how to fix the byes that is sent out from dlg_set_timeout > function. > > Thanks in advance! > Andrew > > > > _______________________________________________ > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing listsr-users@lists.sip-router.orghttp://lists.sip-router. org/cgi-bin/mailman/listinfo/sr-users > > > -- > Daniel-Constantin Mierlawww.twitter.com/miconda -- www.linkedin.com/in/miconda > Kamailio Advanced Training - Mar 6-8 (Europe) and Mar 20-22 (USA) - www.asipto.com > Kamailio World Conference - May 8-10, 2017 - www.kamailioworld.com > > > _______________________________________________ > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list > sr-users(a)lists.sip-router.org > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users > > >

1 0

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 February 2017