Open mgruendlerZH opened 5 years ago
Weiß ich gerade nicht. Aber das eine wird über Perl gemacht und das andere über PHP. Da scheint was schief zu gehen. Hast du es mal im Debug Modus versucht? Was steht dann im Log?
Hallo Christian
Hier das Log, danke für deine Hilfe
Gruss Mirko
Den Call habe ich über die Testfunktion im Plugin gestartet ->> Funktioniert
2019-02-10 20:37:14 [LOG] Logfile content deleted
Lese Daten von Miniserver:
Text: Tür
/opt/loxberry/webfrontend/htmlauth/plugins/text2sip/bin/sipcmd -m "G.711" -o /opt/loxberry/log/plugins/text2sip/Text2SIP_sipcmd.log -T 1 -P sip -u "99999" -c "1" -a "192.168.2.55" -w "192.168.2.59" -x "c123;w100;v/opt/loxberry/data/plugins/text2sip/wav/Text2SIP_bd0T_wav;w5000;h" 2>&1 |tee -a /opt/loxberry/log/plugins/text2sip/Text2SIP.log|while read DTMF_LINE; do echo $DTMF_LINE|grep -q "Exiting."; if [ $? -eq 0 ]; then wget -q -t 1 -T 10 -O /dev/null "http://Adminuser:Password@Miniserver:80/dev/sps/io/Text2SIP_1/0"; fi; DTMF_CODE=echo $DTMF_LINE |grep "receive DTMF:"|cut -c16
; echo "DTMF: $DTMF_CODE"; wget -q -t 1 -T 10 -O /dev/null "http://Adminuser:Password@Miniserver:80/dev/sps/io/Text2SIP_1/$DTMF_CODE"; echo $DTMF_LINE|grep -q "receive DTMF:"; if [ "$DTMF_CODE" == "0" ]; then echo "Confirmation code 0 detected. Exit!!" >> /opt/loxberry/log/plugins/text2sip/Text2SIP.log; sleep .5; killall -15 /opt/loxberry/webfrontend/htmlauth/plugins/text2sip/bin/sipcmd; else if [ ${#DTMF_CODE} -eq 1 ]; then echo "Confirmation code [$DTMF_CODE] detected but [0] expected. Continue..." >> /opt/loxberry/log/plugins/text2sip/Text2SIP.log; fi; fi; done
Add job for guide 1 to queue as #39
################################ Start job from /opt/loxberry/data/plugins/text2sip/wav/Text2SIP_YNpF.job.tsp @ Sun Feb 10 20:37:28 2019
Sun Feb 10 20:37:28 2019 ## Generating voice
Sun Feb 10 20:37:28 2019 ## Converting voice
Sun Feb 10 20:37:28 2019 ## Calling 123
Starting sipcmd LoxBerry Text2SIP Plugin Edition v0.7a adapted by C.Woerstenfeld (sipcmd developed by Tuomo Makkonen)
Manager
Init
initialising SIP endpoint...
Listening for SIP signalling on 0.0.0.0:TestChanAudio
TestChanAudio
5060
SIP listener up
registered as sip:99999@192.168.2.59
Created LocalEndPoint
Main
DIAL_TIMEOUT is 1
Codec-Filter: G.711
TestPhone::Main: calling "123" using gateway "192.168.2.59" at Sun Feb 10 20:37:28 2019
Setting up a call to: sip:123@192.168.2.59
LocalEndpoint::MakeConnection
LocalEndpointCreateConnection
LocalConnection
OnIncomingConnection: token=L76bf70cc2
connection set up to sip:123@192.168.2.59
TestPhone::Main: calling "sip:123@192.168.2.59" for 1/1 seconds
Problem running command sequence ("c123;w100;v/opt/loxberry/data/plugins/text2sip/wav/Text2SIP_bd0T_wav;w5000;h"):
Call: Dial timed out, check -T / --dialtimeout command line option
TestPhone::Main: shutting down
OnReleased: reason: EndedByLocalUser
OnReleased: reason: EndedByLocalUser
OnClearedCall
~LocalConnection
TestPhone::Main: exiting...
Exiting.
~Manager
2019-02-10 20:37:38 [LOG] Show logfile
Sun Feb 10 20:37:28 2019 ## Deleting files
0:00.011 text2sip Version 1.0.1 by LoxBerry Text2SIP on Unix Linux (4.14.30-v7+-armv7l) with PTLib (v2.10.11 (svn:30295)) at 2019/2/10 20:37:28.875
0:00.011 text2sip OpalMan Attached endpoint with prefix sip
0:00.011 text2sip OpalEP Created endpoint: sip
0:00.012 text2sip PTLib Created read/write mutex 0x11b8970
0:00.012 text2sip PWLib File handle high water mark set: 9 PUDPSocket
0:00.012 text2sip IfaceMon Initial interface list:
127.0.0.1 <00-00-00-00-00-00> (lo)
192.168.2.55
0:00.012 text2sip PTLIB Opened NetLink socket
0:00.012 text2sip PWLib File handle high water mark set: 13 Thread unblock pipe
0:00.013 text2sip PTLib Created thread 0x11b9eb0
0:00.013 text2sip PTLib Thread high water mark set: 3
0:00.013 text2sip PTLib Created read/write mutex 0x11b8b18
0:00.013 Network In...0x746c5330 PTLib Started thread 0x11b9eb0 (9180) Network Interface Monitor:0x746c5330
0:00.013 Network In...0x746c5330 IfaceMon Started interface monitor thread.
0:00.013 text2sip PWLib File handle high water mark set: 15 Thread unblock pipe
0:00.013 text2sip PTLib Created thread 0x11ba078 Housekeeper
0:00.013 text2sip PTLib No permission to set priority level 4
0:00.014 text2sip PTLib Thread high water mark set: 4
0:00.014 Housekeeper:0x74685330 PTLib Started thread 0x11ba078 (9183) Housekeeper:0x74685330
0:00.015 text2sip OpalMan Attached endpoint with prefix sips
0:00.015 text2sip SIP Created endpoint.
0:00.015 text2sip OpalMan Added route "local:.=sip:
0:00.028 text2sip OpalUDP Setting interface to 192.168.2.55%eth0
0:00.028 text2sip SIP Transaction timers set: retry=10.000, completion=16.000
0:00.028 text2sip OpalMan Attached endpoint with prefix local
0:00.029 text2sip OpalEP Created endpoint: local
0:00.029 text2sip LocalEP Created endpoint.
0:00.029 text2sip OpalMan Set up call from local: to sip:123@192.168.2.59
0:00.029 text2sip PTLib Created read/write mutex 0x11c3918
0:00.029 text2sip Call Created Call[C7971d8e11]
0:00.029 text2sip OpalMan Set up connection to "local:"
0:00.029 text2sip PTLib Created read/write mutex 0x11c3bc0
0:00.029 text2sip OpalCon Created connection Call[C7971d8e11]-EP
v=0 o=- 1549827448 1 IN IP4 192.168.2.55 s=text2sip/1.0.1 c=IN IP4 192.168.2.55 t=0 0 m=audio 5000 RTP/AVP 8 0 a=sendrecv a=rtpmap:8 PCMA/8000/1 a=rtpmap:0 PCMU/8000/1 a=maxptime:240
0:00.054 text2sip OpalUDP Setting interface to 192.168.2.55%eth0
0:00.054 text2sip SIP Transaction timers set: retry=9.999, completion=31.999
0:00.055 text2sip OpalCon SetPhase from UninitialisedPhase to SetUpPhase for Call[C7971d8e11]-EP
0:01.164 OnRelease:0x742ff330 OpalCon SetPhase from ReleasingPhase to ReleasedPhase for Call[C7971d8e11]-EP
0:01.165 OnRelease:0x742ff330 OpalCon OnRelease thread completed for Call[C7971d8e11]-EP
Den Call habe ich über die URL ausgelöst: http://192.168.2.55/plugins/text2sip/?mode=make_call&vg=1 -> Fehler
2019-02-10 20:37:51 Anfrage zum Abspielen von Ansage #1 2019-02-10 20:37:51 ERROR0005: Kann mich auf Port 5060 nicht zum SIP-Proxy verbinden. (192.168.2.59) 2019-02-10 20:37:59 [LOG] Show logfile
Von: Wörsty notifications@github.com Gesendet: Samstag, 9. Februar 2019 15:43 An: Woersty/LoxBerry-Plugin-Text2SIP LoxBerry-Plugin-Text2SIP@noreply.github.com Cc: Mirko Gründler mirko@gruendlers.net; Manual manual@noreply.github.com Betreff: Re: [Woersty/LoxBerry-Plugin-Text2SIP] Problem mit Grandstream HT 802 (#25)
Weiß ich gerade nicht. Aber das eine wird über Perl gemacht und das andere über PHP. Da scheint was schief zu gehen. Hast du es mal im Debug Modus versucht? Was steht dann im Log?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/Woersty/LoxBerry-Plugin-Text2SIP/issues/25#issuecomment-462050062, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AtQ5QTfLdCk3mvYw3b04iQXu7LKEB5SQks5vLt6RgaJpZM4axqk1.
Es kommt keine Antwort.
Das INVITE geht an 192.168.2.59 raus aber es kommt nix zurück.
INVITE sip:123@192.168.2.59 SIP/2.0 CSeq: 1 INVITE Via: SIP/2.0/UDP 192.168.2.55:5060;branch=z9hG4bK544c3bf8-d82b-e911-9982-b827eb5f3167;rport User-Agent: text2sip/1.0.1 From: "192.168.2.55" <sip:99999@192.168.2.59>;tag=066a39f8-d82b-e911-9982-b827eb5f3167 Call-ID: 8a8639f8-d82b-e911-9982-b827eb5f3167@loxberry Supported: 100rel,replaces Organization: LoxBerry Text2SIP To: <sip:123@192.168.2.59> Contact: "192.168.2.55" <sip:99999@192.168.2.55> Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING,PRACK Content-Length: 193 Content-Type: application/sdp Max-Forwards: 70 v=0 o=- 1549827448 1 IN IP4 192.168.2.55 s=text2sip/1.0.1 c=IN IP4 192.168.2.55 t=0 0 m=audio 5000 RTP/AVP 8 0 a=sendrecv a=rtpmap:8 PCMA/8000/1 a=rtpmap:0 PCMU/8000/1 a=maxptime:240
Wie sieht das Log vom "Test" aus (da wo es geht)?
Hallo Christian
Ich habe hier ein Problem das ich mir nicht erklären kann.
Konstellation: Ich habe ein Analoges Retro Telefon das an einem Grandstream HT802 Analogconverter hängt Der HT802 unterstütze Direct Calls also von IP zu IP ohne SIP Proxy
Wenn ich das ganze aus der Plugin Konfiguration aus teste klingelt das Telefon wie erwartet. Wenn ich allerdings die Ansage über den Browser oder den Miniserver aufrufen will, habe ich im Browsertest "http://192.168.2.55/plugins/text2sip/?mode=make_call&vg=1" die Fehlermeldung "ERROR0005: Kann mich auf Port 5060 nicht zum SIP-Proxy verbinden. (192.168.2.59)" Warum ist das so?
Danke Gruss Mirko