sr-users April 2017

sr-users@lists.kamailio.org

79 participants
114 discussions

Rtpengine module. rtcp-mux-demux option does not work.
by Denys Pozniak 13 Apr '17

13 Apr '17

Hello, All! We are using Kamailio as Webrtc to SIP proxy. Clinet's Chrome browser needs to have rtcp-mux option to work correct, so we are adding it in RTPENGINE->WS direction as: rtpengine_manage("trust-address replace-origin replace-session-connection *rtcp-mux-offer rtcp-mux-accept* ICE=force RTP/SAVPF"); Also we need to remove it in RTPENGINE->PSTN direction, we are trying to do it like this: rtpengine_manage("trust-address replace-origin replace-session-connection * rtcp-mux-… [View More]

2 1

RAW_SOCKS with Kamaili 4.4.5
by Yasin CANER 13 Apr '17

13 Apr '17

3 6

Kamailio 5.0 can't get version of the RTP proxy
by Yebe diomande Keffa 13 Apr '17

13 Apr '17

Hello Getting this issu on Kamaiio 5.0 ( install from GIT): Apr 10 10:47:42 ns3033789 /usr/local/sbin/kamailio[11496]: WARNING: rtpproxy [rtpproxy.c:1366]: rtpp_test(): can't get version of the RTP proxy Apr 10 10:47:42 ns3033789 /usr/local/sbin/kamailio[11488]: WARNING: rtpproxy [rtpproxy.c:1403]: rtpp_test(): support for RTP proxy <udp:127.0.0.1:7722> has been disabled temporarily I done install of RTPproxy with: $ git clone -b master https://github.com/sippy/rtpproxy.git $ git -C … [View More]

3 5

New developer: Mikko Lehto
by Daniel-Constantin Mierla 12 Apr '17

12 Apr '17

Hello, just to let everyone know that I invited Mikko Lehto into the developer group on Kamailio gihub project. He has made a lot of good pull requests over the time, specially to documentation and unit tests that could have been just committed directly without delay on waiting for a review, saving also time from the other developers. Taking time to express my thanks for all his contributions so far and reviving those unit tests, and I am looking forward to future collaboration! Cheers, … [View More]

3 2

Use mysql view to load data into htable
by Jan Hazenberg 12 Apr '17

12 Apr '17

Hello, I'm trying to load data from a mysql table into a htable using a mysql view. But when i start kamailio i get the following error: ERROR: htable [ht_db.c:345]: ht_db_load_table(): Wrong db type [3] for key_type column Here a example of a view i'm trying to use: CREATE OR REPLACE VIEW `view_blacklist_prefix` AS SELECT prefix AS key_name, '0' AS key_type, '0' AS value_type, '1' AS key_value, '0' AS expires FROM openser.blacklist_prefix GO Should it be possible to use a mysql view … [View More]

2 2

snmpstats issue
by Igor Potjevlesch 12 Apr '17

12 Apr '17

Hello, On one of my Kamailio server, I don't have data returned by KAMAILIO-MIB::. KAMAILIO-SIP-COMMON-MIB and KAMAILIO-SIP-SERVER-MIB look to work good. Everything is configured as the other Kamailio instances, but there is nothing about current dialog even if the module is loaded into Kamailio and called into kamailio.cfg. Any idea? Here is an output of snmpwalk: snmpwalk -c legosnoc -v 1 <HOST> 1.3.6.1.4.1.34352 KAMAILIO-SIP-COMMON-MIB::kamailioSIPProtocolVersion.0 … [View More]= STRING: SIP/2.0 KAMAILIO-SIP-COMMON-MIB::kamailioSIPServiceStartTime.0 = Timeticks: (0) 0:00:00.00 KAMAILIO-SIP-COMMON-MIB::kamailioSIPEntityType.0 = BITS: 20 proxyServer(2) KAMAILIO-SIP-COMMON-MIB::kamailioSIPTransportRcv.ipv4."IP_HOST".5060 = BITS: 40 udp(1) KAMAILIO-SIP-COMMON-MIB::kamailioSIPTransportRcv.ipv4."IP_HOST".5060 = BITS: 40 udp(1) KAMAILIO-SIP-COMMON-MIB::kamailioSIPMethodName.1 = STRING: METHOD_INVITE KAMAILIO-SIP-COMMON-MIB::kamailioSIPMethodName.2 = STRING: METHOD_CANCEL KAMAILIO-SIP-COMMON-MIB::kamailioSIPMethodName.3 = STRING: METHOD_ACK KAMAILIO-SIP-COMMON-MIB::kamailioSIPMethodName.4 = STRING: METHOD_BYE KAMAILIO-SIP-COMMON-MIB::kamailioSIPMethodName.5 = STRING: METHOD_INFO KAMAILIO-SIP-COMMON-MIB::kamailioSIPMethodName.6 = STRING: METHOD_OPTIONS KAMAILIO-SIP-COMMON-MIB::kamailioSIPMethodName.7 = STRING: METHOD_UPDATE KAMAILIO-SIP-COMMON-MIB::kamailioSIPMethodName.8 = STRING: METHOD_REGISTER KAMAILIO-SIP-COMMON-MIB::kamailioSIPMethodName.9 = STRING: METHOD_MESSAGE KAMAILIO-SIP-COMMON-MIB::kamailioSIPMethodName.10 = STRING: METHOD_SUBSCRIBE KAMAILIO-SIP-COMMON-MIB::kamailioSIPMethodName.11 = STRING: METHOD_NOTIFY KAMAILIO-SIP-COMMON-MIB::kamailioSIPMethodName.12 = STRING: METHOD_PRACK KAMAILIO-SIP-COMMON-MIB::kamailioSIPMethodName.13 = STRING: METHOD_REFER KAMAILIO-SIP-COMMON-MIB::kamailioSIPMethodName.14 = STRING: METHOD_PUBLISH KAMAILIO-SIP-COMMON-MIB::kamailioSIPSummaryInRequests.0 = Counter32: 2680 KAMAILIO-SIP-COMMON-MIB::kamailioSIPSummaryOutRequests.0 = Counter32: 1050 KAMAILIO-SIP-COMMON-MIB::kamailioSIPSummaryInResponses.0 = Counter32: 3102 KAMAILIO-SIP-COMMON-MIB::kamailioSIPSummaryOutResponses.0 = Counter32: 1630 KAMAILIO-SIP-COMMON-MIB::kamailioSIPSummaryTotalTransactions.0 = Counter32: 1518 KAMAILIO-SIP-COMMON-MIB::kamailioSIPCurrentTransactions.0 = Gauge32: 7 KAMAILIO-SIP-COMMON-MIB::kamailioSIPNumUnsupportedUris.0 = Counter32: 16 KAMAILIO-SIP-COMMON-MIB::kamailioSIPNumUnsupportedMethods.0 = Counter32: 0 KAMAILIO-SIP-COMMON-MIB::kamailioSIPOtherwiseDiscardedMsgs.0 = Counter32: 0 KAMAILIO-SIP-SERVER-MIB::kamailioSIPProxyStatefulness.0 = INTEGER: callStateful(3) KAMAILIO-SIP-SERVER-MIB::kamailioSIPProxyRecordRoute.0 = INTEGER: true(1) KAMAILIO-SIP-SERVER-MIB::kamailioSIPProxyAuthMethod.0 = BITS: 20 digest(2) KAMAILIO-SIP-SERVER-MIB::kamailioSIPNumProxyRequireFailures.0 = Counter32: 0 KAMAILIO-SIP-SERVER-MIB::kamailioSIPRegMaxContactExpiryDuration.0 = Gauge32: 3600 seconds KAMAILIO-SIP-SERVER-MIB::kamailioSIPRegMaxUsers.0 = Gauge32: 4294967295 KAMAILIO-SIP-SERVER-MIB::kamailioSIPRegCurrentUsers.0 = Gauge32: 325416 KAMAILIO-SIP-SERVER-MIB::kamailioSIPRegDfltRegActiveInterval.0 = Gauge32: 3600 seconds KAMAILIO-SIP-SERVER-MIB::kamailioSIPUserUri.1 = STRING: DefaultUser KAMAILIO-SIP-SERVER-MIB::kamailioSIPUserAuthenticationFailures.1 = Counter32: 0 KAMAILIO-SIP-SERVER-MIB::kamailioSIPContactDisplayName.1.1 = STRING: DefaultUser KAMAILIO-SIP-SERVER-MIB::kamailioSIPContactURI.1.1 = STRING: DefaultUser KAMAILIO-SIP-SERVER-MIB::kamailioSIPContactLastUpdated.1.1 = STRING: 0-0-0,0:0:0.0 KAMAILIO-SIP-SERVER-MIB::kamailioSIPContactExpiry.1.1 = STRING: 0-0-0,0:0:0.0 KAMAILIO-SIP-SERVER-MIB::kamailioSIPContactPreference.1.1 = STRING: -0.01 KAMAILIO-SIP-SERVER-MIB::kamailioSIPRegUserLookupCounter.0 = Counter32: 4 KAMAILIO-SIP-SERVER-MIB::kamailioSIPRegAcceptedRegistrations.0 = Counter32: 21 KAMAILIO-SIP-SERVER-MIB::kamailioSIPRegRejectedRegistrations.0 = Counter32: 0 KAMAILIO-MIB::kamailioSrvMaxMemory.0 = Gauge32: 738197504 KAMAILIO-MIB::kamailioSrvFreeMemory.0 = Gauge32: 358262600 KAMAILIO-MIB::kamailioSrvMaxUsed.0 = Gauge32: 380013984 KAMAILIO-MIB::kamailioSrvRealUsed.0 = Gauge32: 379934904 KAMAILIO-MIB::kamailioSrvMemFragments.0 = Gauge32: 70 KAMAILIO-MIB::kamailioSrvCnfFullVersion.0 = STRING: kamailio 4.2.8 (x86_64/linux) 4507b8 KAMAILIO-MIB::kamailioSrvCnfVerName.0 = STRING: kamailio KAMAILIO-MIB::kamailioSrvCnfVerVersion.0 = STRING: 4.2.8 KAMAILIO-MIB::kamailioSrvCnfVerArch.0 = STRING: x86_64 KAMAILIO-MIB::kamailioSrvCnfVerOs.0 = STRING: linux KAMAILIO-MIB::kamailioSrvCnfVerId.0 = STRING: 4507b8 KAMAILIO-MIB::kamailioSrvCnfVerCompTime.0 = STRING: 12:34:45 Feb 17 2017 KAMAILIO-MIB::kamailioSrvCnfVerCompiler.0 = STRING: gcc 4.4.6 KAMAILIO-MIB::kamailioSrvCnfVerFlags.0 = STRING: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, DBG_QM_MALLOC, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES KAMAILIO-MIB::kamailioMsgQueueDepth.0 = Gauge32: 0 KAMAILIO-MIB::kamailioMsgQueueMinorThreshold.0 = INTEGER: -1 KAMAILIO-MIB::kamailioMsgQueueMajorThreshold.0 = INTEGER: -1 KAMAILIO-MIB::kamailioMsgQueueDepthAlarmStatus.0 = BITS: 00 KAMAILIO-MIB::kamailioMsgQueueDepthMinorAlarm.0 = INTEGER: clear(0) KAMAILIO-MIB::kamailioMsgQueueDepthMajorAlarm.0 = INTEGER: clear(0) KAMAILIO-MIB::kamailioCurNumDialogs.0 = Gauge32: 0 KAMAILIO-MIB::kamailioCurNumDialogsInProgress.0 = Gauge32: 0 KAMAILIO-MIB::kamailioCurNumDialogsInSetup.0 = Gauge32: 0 KAMAILIO-MIB::kamailioTotalNumFailedDialogSetups.0 = Counter32: 0 KAMAILIO-MIB::kamailioDialogLimitMinorThreshold.0 = INTEGER: -1 KAMAILIO-MIB::kamailioDialogLimitMajorThreshold.0 = INTEGER: -1 KAMAILIO-MIB::kamailioTotalNumDialogSetups.0 = Counter32: 0 KAMAILIO-MIB::kamailioDialogUsageState.0 = INTEGER: idle(0) KAMAILIO-MIB::kamailioDialogLimitAlarmStatus.0 = BITS: 00 KAMAILIO-MIB::kamailioDialogLimitMinorAlarm.0 = INTEGER: clear(0) KAMAILIO-MIB::kamailioDialogLimitMajorAlarm.0 = INTEGER: clear(0) KAMAILIO-MIB::kamailioNetTcpConnEstablished.0 = Counter32: 0 KAMAILIO-MIB::kamailioNetTcpConnFailed.0 = Counter32: 0 KAMAILIO-MIB::kamailioNetTcpConnReset.0 = Counter32: 0 KAMAILIO-MIB::kamailioNetTcpConnSuccess.0 = Counter32: 0 KAMAILIO-MIB::kamailioNetTcpConnOpen.0 = Gauge32: 0 KAMAILIO-MIB::kamailioNetTcpConnPassiveOpen.0 = Counter32: 0 KAMAILIO-MIB::kamailioNetTcpConnReject.0 = Counter32: 0 KAMAILIO-MIB::kamailioNetTcpEnabled.0 = INTEGER: 0 KAMAILIO-MIB::kamailioNetTcpMaxConns.0 = INTEGER: 2048 KAMAILIO-MIB::kamailioNetTcpConnTimeout.0 = INTEGER: 10 KAMAILIO-MIB::kamailioNetTcpSendTimeout.0 = INTEGER: 160 KAMAILIO-MIB::kamailioNetTcpConnLifetime.0 = INTEGER: 1920 KAMAILIO-MIB::kamailioNetTcpNoConnect.0 = INTEGER: 0 KAMAILIO-MIB::kamailioNetTcpFdCache.0 = INTEGER: 1920 KAMAILIO-MIB::kamailioNetTcpAsync.0 = INTEGER: true(1) KAMAILIO-MIB::kamailioNetTcpAsyncConnWait.0 = INTEGER: true(1) KAMAILIO-MIB::kamailioNetTcpAsyncConnWqMax.0 = INTEGER: 32768 KAMAILIO-MIB::kamailioNetTcpAsyncWqBlkSize.0 = INTEGER: 10485760 KAMAILIO-MIB::kamailioNetTcpRdBufSize.0 = INTEGER: 16384 KAMAILIO-MIB::kamailioNetTcpDeferAccept.0 = INTEGER: 0 KAMAILIO-MIB::kamailioNetTcpDelayedAck.0 = INTEGER: true(1) KAMAILIO-MIB::kamailioNetTcpSynCnt.0 = INTEGER: 0 KAMAILIO-MIB::kamailioNetTcpLinger.0 = INTEGER: 0 KAMAILIO-MIB::kamailioNetTcpKeepAlive.0 = INTEGER: true(1) KAMAILIO-MIB::kamailioNetTcpKeepIdle.0 = INTEGER: 0 KAMAILIO-MIB::kamailioNetTcpKeepIntvl.0 = INTEGER: 0 KAMAILIO-MIB::kamailioNetTcpKeepCnt.0 = INTEGER: 0 KAMAILIO-MIB::kamailioNetTcpCrlfPing.0 = INTEGER: true(1) KAMAILIO-MIB::kamailioNetTcpAcceptAliases.0 = INTEGER: 0 KAMAILIO-MIB::kamailioNetTcpAcceptNoCl.0 = INTEGER: 0 KAMAILIO-MIB::kamailioNetWsConnsActive.0 = Gauge32: 0 KAMAILIO-MIB::kamailioNetWsConnsActiveMax.0 = Gauge32: 0 KAMAILIO-MIB::kamailioNetWsConnsFailed.0 = Counter32: 0 KAMAILIO-MIB::kamailioNetWsConnsClosedLocal.0 = Counter32: 0 KAMAILIO-MIB::kamailioNetWsConnsClosedRemote.0 = Counter32: 0 KAMAILIO-MIB::kamailioNetWsFramesRx.0 = Counter32: 0 KAMAILIO-MIB::kamailioNetWsFramesTx.0 = Counter32: 0 KAMAILIO-MIB::kamailioNetWsHandshakeSuccess.0 = Counter32: 0 KAMAILIO-MIB::kamailioNetWsHandshakeFailed.0 = Counter32: 0 KAMAILIO-MIB::kamailioNetConfUdpTransport.0 = INTEGER: true(1) KAMAILIO-MIB::kamailioNetConfUdpDtlsTransport.0 = INTEGER: -1 KAMAILIO-MIB::kamailioNetConfTcpTransport.0 = INTEGER: 0 KAMAILIO-MIB::kamailioNetConfTcpTlsTransport.0 = INTEGER: 0 KAMAILIO-MIB::kamailioNetConfSctpTransport.0 = INTEGER: true(1) KAMAILIO-MIB::kamailioNetConfSctpTlsTransport.0 = INTEGER: -1 KAMAILIO-MIB::kamailioNetConfWsTransport.0 = INTEGER: -1 KAMAILIO-MIB::kamailioNetConfWsTlsTransport.0 = INTEGER: 0 KAMAILIO-MIB::kamailioNetConfHttpServer.0 = INTEGER: 0 KAMAILIO-MIB::kamailioNetConfMsrpRelay.0 = INTEGER: 0 KAMAILIO-MIB::kamailioNetConfStunServer.0 = INTEGER: 0 KAMAILIO-MIB::kamailioNetConfOutbound.0 = INTEGER: 0 Regards, Igor. --- L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast. https://www.avast.com/antivirus [View Less]

2 7

issue with sip path support between asterisk and kamailio
by gerry kernan 12 Apr '17

12 Apr '17

Hi Thanks in advanced if anyone can help me on this. I have kamailio -4.2.3-1.1 running in front of asterisk 13.13.1. I'm using Path support with asterisk so that I can forward Sip requests via kamailio to the asterisk server running on a LAN IP. Kamailio is configured with a WAN and LAN IP. All works well I can register a sip endpoint to the asterisk server via kamailio and make an receive calls, SIP OPTIONs from the asterisk server are received and relayed by kamailio to endpoints. … [View More]But I'm having issues when a call is hung up asterisk appears to be trying to send the BYE via its own IP address rather that the IP of the LAN interface on the kamailio server. Should I be looking at the issue being on asterisk as it is not sending the BYE via correct IP? Y.Y.Y.Y = WAN IP of client endpoint 192.10.10.216 = LAN IP of asterisk Example of BYE from sip debug on asterisk --- (10 headers 0 lines) --- Really destroying SIP dialog '5d3ae6944a08b42c2078e237141e0e40@192.10.10.216:5060' Method: OPTIONS -- <SIP/1001-00000011> Playing 'digits/17.ulaw' (language 'en') -- Executing [*250@cos-all:8] Wait("SIP/1001-00000011", "1") in new stack -- Executing [*250@cos-all:9] SayUnixTime("SIP/1001-00000011", ",,IMp") in new stack -- <SIP/1001-00000011> Playing 'digits/4.ulaw' (language 'en') -- <SIP/1001-00000011> Playing 'digits/oh.ulaw' (language 'en') -- <SIP/1001-00000011> Playing 'digits/4.ulaw' (language 'en') -- <SIP/1001-00000011> Playing 'digits/p-m.ulaw' (language 'en') -- Executing [*250@cos-all:10] Hangup("SIP/1001-00000011", "") in new stack == Spawn extension (cos-all, *250, 10) exited non-zero on 'SIP/1001-00000011' Scheduling destruction of SIP dialog 'OGRjYzJlYmE5MDhjYTdkMTM1ZTAxNTk2YWYwNDg5MTA.' in 6400 ms (Method: ACK) set_destination: Parsing <sip:1001@Y.Y.Y.Y:16078;transport=UDP> for address/port to send to set_destination: set destination to Y.Y.Y.Y:16078 Reliably Transmitting (no NAT) to Y.Y.Y.Y:16078: BYE sip:1001@Y.Y.Y.Y:16078;transport=UDP SIP/2.0 Via: SIP/2.0/UDP 192.10.10.216:5060;branch=z9hG4bK46ed8549 Max-Forwards: 70 From: <sip:*250@sip.domain.ie;transport=UDP>;tag=as60c5965b To: <sip:1001@sip.domain.ie;transport=UDP>;tag=471c3a31 Call-ID: OGRjYzJlYmE5MDhjYTdkMTM1ZTAxNTk2YWYwNDg5MTA. CSeq: 102 BYE User-Agent: OMBUTEL PBX Proxy-Authorization: Digest username="1001", realm="asterisk", algorithm=MD5, uri="sip:sip.domain.ie", nonce="4aaa41f3", response="136fac72a799f9507a7466b578786110" X-Asterisk-HangupCause: Normal Clearing X-Asterisk-HangupCauseCode: 16 Content-Length: 0 KAMAILIO LAN IP = 192.10.10.202 SIP status of peer on asterisk * Name : 1001 Description : Infinity-Test Secret : <Set> MD5Secret : <Not set> Remote Secret: <Not set> Context : cos-all Record On feature : automon Record Off feature : automon Subscr.Cont. : <Not set> Language : en Tonezone : uk AMA flags : Unknown Transfer mode: open CallingPres : Presentation Allowed, Not Screened Callgroup : Pickupgroup : Named Callgr : Nam. Pickupgr: MOH Suggest : ringback Mailbox : 1001@ombutel-voicemail VM Extension : asterisk LastMsgsSent : 0/0 Call limit : 2147483647 Max forwards : 0 Dynamic : Yes Callerid : "Infinity-Test" <1001> MaxCallBR : 384 kbps Expire : 3228 Insecure : no Force rport : No Symmetric RTP: No ACL : Yes DirectMedACL : No T.38 support : No T.38 EC mode : Unknown T.38 MaxDtgrm: 4294967295 DirectMedia : Yes PromiscRedir : No User=Phone : No Video Support: No Text Support : No Ign SDP ver : No Trust RPID : Yes Send RPID : Yes Path support : Yes Path : <sip:192.10.10.202;lr;received=sip:Y.Y.Y.Y:16078> TrustIDOutbnd: Legacy Subscriptions: Yes Overlap dial : Yes DTMFmode : rfc2833 Timer T1 : 500 Timer B : 32000 ToHost : Addr->IP : 192.168.200.122:5060 Defaddr->IP : (null) Prim.Transp. : UDP Allowed.Trsp : UDP Def. Username: 1001 SIP Options : norefersub replaces replace timer Codecs : (ulaw|alaw|g729) Auto-Framing : No Status : OK (19 ms) Useragent : Zoiper for Windows 2.43 r24984 Reg. Contact : sip:1001@192.168.200.122:5060;rinstance=3798b50d10d60d84;transport=UDP Qualify Freq : 60000 ms Keepalive : 0 ms Sess-Timers : Accept Sess-Refresh : uas Sess-Expires : 1800 secs Min-Sess : 90 secs RTP Engine : asterisk Parkinglot : Use Reason : No Gerry Kernan Infinity IT | 17 The Mall | Beacon Court | Sandyford | Dublin D18 E3C8 | Ireland Tel: +353 - (0)1 - 293 0090 | E-Mail: <mailto:gerry.kernan@infinityit.ie> gerry.kernan(a)infinityit.ie Managed IT Services Infinity IT - <http://www.infinityit.ie/> www.infinityit.ie IP Telephony Asterisk Consulting - <http://www.asteriskconsulting.com> www.asteriskconsulting.com Contact Centre Total Interact - <http://www.totalinteract.com> www.totalinteract.com [View Less]

2 2

WAN ITSP + NAT can someone help me ?
by Martin Lapointe 12 Apr '17

12 Apr '17

hi all, did someone can help me for with some configuration im a litle lost with inbount trafic with kamailio i need to redirect inbound conection from itsp (over wan) to an internal PBX but it seem nat is not working (I do the test with jitsi on my desktop and sip connection seem initiate (200 ok) but no sound ) like contact information is not update on sip header can someone help me a bit MARTIN LAPOINTE Spécialiste en infrastructure technologique T (418) 543-2600 x2119 F (418) 543-0363 … [View More]

2 1

Kamailio 5.0 doesn't forward Authorization (Digest username) to Asterisk
by Marko Tirs 11 Apr '17

11 Apr '17

Hello all, I am trying to use Kamailio 5.0 with Asterisk (separate IP addresses, both port 5060), but Asterisk doesn't register the SIP clients which comes through Kamailio.If I register the same user directly to the Asterisk then it works! 1st REGISTER is also without Authorization (Digest name) but in the 2nd REGISTER it exists and registration goes OK. How to use Kamailio with Asterisk in the way the SIP client is registered on both of them?Thank youMarko SIP-CLIENT DIRECTLY TO ASTERISK:---… [View More]-------------------------------------------------------- 1 2017-04-01 15:20:48.331806 192.168.0.12 192.168.0.2 SIP 544 Request: REGISTER sip:192.168.0.2 (1 binding) | 2 2017-04-01 15:20:48.332998 192.168.0.2 192.168.0.12 SIP 626 Status: 401 Unauthorized | 3 2017-04-01 15:20:48.333814 192.168.0.12 192.168.0.2 SIP 700 Request: REGISTER sip:192.168.0.2 (1 binding) | 4 2017-04-01 15:20:48.335975 192.168.0.2 192.168.0.12 SIP 647 Status: 200 OK (1 binding) | Frame 3: 700 bytes on wire (5600 bits), 700 bytes captured (5600 bits) on interface 0 Ethernet II, Src: AsrockIn_0a:0b:46 (70:85:c2:0a:0b:46), Dst: Raspberr_a1:fd:f7 (b8:27:eb:a1:fd:f7) Internet Protocol Version 4, Src: 192.168.0.12, Dst: 192.168.0.2 User Datagram Protocol, Src Port: 64369, Dst Port: 5060 Session Initiation Protocol (REGISTER) Request-Line: REGISTER sip:192.168.0.2 SIP/2.0 Message Header Via: SIP/2.0/UDP 192.168.0.12:64369;rport;branch=z9hG4bKPj9f8759c0537b4834bb411358d0b0a2ff Max-Forwards: 70 From: "33" <sip:33@192.168.0.2>;tag=4c586be1fcf842359e7d429abcb0b213 To: "33" <sip:33@192.168.0.2> Contact: <sip:74081936@192.168.0.12:64369>;+sip.instance="<urn:uuid:b408367e-d06b-4780-a9a0-291eb99ec83c>" Call-ID: d3c240808c934b77a9bbcb8bd4c1bd8c CSeq: 2 REGISTER Expires: 600 Supported: gruu User-Agent: Blink 3.0.0 (Windows) Authorization: Digest username="33", realm="asterisk", nonce="76ca37d8", uri="sip:192.168.0.2", response="19fc1a634abc72c41dcb516470c34fc2", algorithm=MD5 Authentication Scheme: Digest Username: "33" Realm: "asterisk" Nonce Value: "76ca37d8" Authentication URI: "sip:192.168.0.2" Digest Authentication Response: "19fc1a634abc72c41dcb516470c34fc2" Algorithm: MD5 Content-Length: 0 SIP-CLIENT TO KAMAILIO WITH FORWARD TO ASTERISK:---------------------------------------------------------------------------------------------- 11 2017-04-01 15:21:06.806347 192.168.0.13 192.168.0.2 SIP 459 Request: REGISTER sip:192.168.0.2:5060 (1 binding) | 12 2017-04-01 15:21:06.807514 192.168.0.2 192.168.0.13 SIP 608 Status: 401 Unauthorized | 13 2017-04-01 15:21:06.814819 192.168.0.13 192.168.0.2 SIP 456 Request: REGISTER sip:192.168.0.2:5060 (remove 1 binding) | 14 2017-04-01 15:21:06.815712 192.168.0.2 192.168.0.13 SIP 608 Status: 401 Unauthorized | 15 2017-04-01 15:21:06.821125 192.168.0.13 192.168.0.2 SIP 459 Request: REGISTER sip:192.168.0.2:5060 (1 binding) | 16 2017-04-01 15:21:06.821910 192.168.0.2 192.168.0.13 SIP 608 Status: 401 Unauthorized | Frame 15: 459 bytes on wire (3672 bits), 459 bytes captured (3672 bits) on interface 0 Ethernet II, Src: Micro-St_de:b2:3a (00:24:21:de:b2:3a), Dst: Raspberr_a1:fd:f7 (b8:27:eb:a1:fd:f7) Internet Protocol Version 4, Src: 192.168.0.13, Dst: 192.168.0.2 User Datagram Protocol, Src Port: 5060, Dst Port: 5060 Session Initiation Protocol (REGISTER) Request-Line: REGISTER sip:192.168.0.2:5060 SIP/2.0 Message Header Via: SIP/2.0/UDP 192.168.0.13;branch=z9hG4bKd101.0ad599b6000000000000000000000000.0 To: <sip:32@192.168.0.2> SIP to address: sip:32@192.168.0.2 From: <sip:32@192.168.0.2>;tag=533cb9e91f4b999cf76861cbb9ed54ed-85c4 SIP from address: sip:32@192.168.0.2 SIP from tag: 533cb9e91f4b999cf76861cbb9ed54ed-85c4 CSeq: 10 REGISTER Call-ID: 41df282f10fdc7b6-2773(a)127.0.0.1 Max-Forwards: 70 Content-Length: 0 User-Agent: kamailio (5.0.0 (x86_64/linux)) Contact: <sip:32@192.168.0.13:5060> Contact URI: sip:32@192.168.0.13:5060 Expires: 3600 kamailio.cfg:-------------------- #!define WITH_DEBUG #!define WITH_MYSQL #!define WITH_AUTH #!define WITH_USRLOCDB #!define WITH_ASTERISK ... #!ifdef WITH_ASTERISK asterisk.bindip = "192.168.0.2" desc "Asterisk IP Address" asterisk.bindport = "5060" desc "Asterisk Port" kamailio.bindip = "192.168.0.13" desc "Kamailio IP Address" kamailio.bindport = "5060" desc "Kamailio Port" #!endif ... # Forward REGISTER to Asterisk route[REGFWD] { if(!is_method("REGISTER")) { return; } $var(rip) = $sel(cfg_get.asterisk.bindip); $uac_req(method)="REGISTER"; $uac_req(ruri)="sip:" + $var(rip) + ":" + $sel(cfg_get.asterisk.bindport); #$uac_req(ruri)="sip:" + $au + "@" + $var(rip) + ":" + $sel(cfg_get.asterisk.bindport); $uac_req(furi)="sip:" + $au + "@" + $var(rip); $uac_req(turi)="sip:" + $au + "@" + $var(rip); $uac_req(hdrs)="Contact: <sip:" + $au + "@" + $sel(cfg_get.kamailio.bindip) + ":" + $sel(cfg_get.kamailio.bindport) + ">\r\n"; if($sel(contact.expires) != $null) $uac_req(hdrs)= $uac_req(hdrs) + "Expires: " + $sel(contact.expires) + "\r\n"; else $uac_req(hdrs)= $uac_req(hdrs) + "Expires: " + $hdr(Expires) + "\r\n"; uac_req_send(); } [View Less]

2 2

Info: mailing lists use lists.kamailio.org
by Daniel-Constantin Mierla 11 Apr '17

11 Apr '17

Hello, all the mailing lists related to the Kamailio project are using now lists.kamailio.org as primary domain, including sr-dev and sr-users. >From now on, the emails should be addressed to: - sr-dev(a)lists.kamailio.org - sr-users(a)lists.kamailio.org The previous domain (lists.sip-router.org) should still work, so existing discussions can go on as usual. If anyone is encountering any problems or notices some information on kamailio.org that needs to be updated, do not hesitate to … [View More]

2 3

← Newer
1
...
5
6
7
8
9
10
11
12
Older →

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