I've been trying to configure FreeSWITCH with telcentris but not working.
FreeSWITCH Currently it works perfectly with other providers.
I tried using the XML configuration that is in the official website (here the link: http://wiki.freeswitch.org/wiki/Provider_Configuration:_Telcentris) but nothing. The only thing that changes in my xml is the user and the ip access and that's what I do. Too put the public context.
I created a lua script that is with the puebas I'm doing, and this is the error that throws me for FreeSWITCH console:
12.19.2012 13:14:58.619723 [NOTICE] switch_cpp.cpp: 1227 TELCENTRIS
12.19.2012 13:14:58.619723 [NOTICE] switch_channel.c: 930 New Channel sofia/external/2590573122223333 [80d4568f-2451-4f72-8de2-65b471a80e20]
12.19.2012 13:14:58.779729 [NOTICE] sofia.c: 6258 Hangup sofia/external/2590573122222222 [CS_CONSUME_MEDIA] [NORMAL_TEMPORARY_FAILURE]
12.19.2012 13:14:58.779729 [NOTICE] switch_cpp.cpp: 1227 *********** Caller: NORMAL_TEMPORARY_FAILURE - Try: 1 ***********
12.19.2012 13:14:58.779729 [NOTICE] switch_cpp.cpp: 1227 REQUESTED
If someone used FreeSWITCH with telcentris, or can tell me what could be the possible failure or error, I would greatly appreciate it.
I think the best would be to run tcpdump or wireshark and collect the whole SIP and RTP traffic for that destination. Then it will be more clear what's going on.
Related
When using Xdebug directly from VSCode using one of two PHP extension (xdebug.php-debug, devsense.phptools-vscode) for debugging everything works as expected. But I have a shared environment where an Apache/PHP/Xdebug setup/instance is to be used by multiple developers.
With both extension everything works well when being used directly receiving the Xdebug connection. I have a breakpoint at the last line of code and although the whole HTML content was completely sent by PHP the browser it is still waiting to do anything - although ob_end_flush() (output buffering) was already called. Stepping over the last line of code the HTML content arrives at the browser. The Xdebug log is finishing in the same way.
[Step Debug] -> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="https://xdebug.org/dbgp/xdebug" command="run" transaction_id="14" status="stopping" reason="ok"></response>
...
[Step Debug] -> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="https://xdebug.org/dbgp/xdebug" command="stop" transaction_id="22" status="stopped" reason="ok"></response>
When I now set this up using DBGp proxy the two PHP extension behave different. One is blocking the HTML output forever for all request been started and if I kill the apache processes I get a proxy log
21:01:28.652 [warn] [server] Handler response error: Error reading response: Error reading length: EOF
21:01:28.652 [info] [server] Closing server connection from 127.0.0.1:60104
21:01:28.653 [warn] [server] Handler response error: Error reading response: Error reading length: EOF
21:01:28.653 [info] [server] Closing server connection from 127.0.0.1:35422
21:01:28.653 [warn] [server] Handler response error: Error reading response: Error reading length: EOF
21:01:28.653 [info] [server] Closing server connection from 127.0.0.1:43594
21:01:28.653 [warn] [server] Handler response error: Error reading response: Error reading length: EOF
21:01:28.653 [info] [server] Closing server connection from 127.0.0.1:56398
21:01:28.659 [warn] [server] Handler response error: Error reading response: Error reading length: EOF
21:01:28.659 [info] [server] Closing server connection from 127.0.0.1:40030
while the other is delivering the HTML output and says in the proxy log the same moment
22:02:02.316 [warn] [server] Handler response error: Error reading response: Error reading length: EOF
22:02:02.317 [info] [server] Closing server connection from 127.0.0.1:33160
In both cases the Xdebug log says the same: status stopped, reason ok.
So I wonder whether the way the request seems to completely end in both cases reading an EOF and closing the server connection is really a warning because it's unexpected or whether this is the normal behaviour. And then of course it's an issue of the one PHP extension seeming not to tell the proxy and server they can end their connection (I assume this is the client's job which here is the proxy).
I checked all configuration options from Xdebug, the VSCode PHP extension and DBGp proxy to increase logging but I could not find out more than what I have described above. I tried setting the connection either via the VSCode extension or manually issuing echo -e "proxyinit -p 39001 -k jni-vscode -m 1\0" | nc 127.0.0.1 9001 with no success. The EOF warning stays and for the devsense.phptools-vscode plugin there is no php output to the browser. If anyone has a clue why I would appreciate a hint.
Thanks,
Jürgen
PS: Killing dbgpProxy makes apache deliver all the content with access_log entry showing it took 3064 seconds to fulfill the request.
The situation is, I wanna establish a QUIC connection based on quic-go from local to ECS server. The related tests using localhost are done both on local and remote device. That is:
#local: .$QUIC-GO-PATH/example/client/main -insecure -keylog ssl.log -qlog trial.log -v https://127.0.0.1:6121/demo/tile
#local: .$QUIC-GO-PATH/example/main -qlog -tcp -v
These tests are completed.
Now is the problem,when I start local-remote connection an error occurred:
#remote: .$QUIC-GO-PATH/example/main -qlog -tcp -v
#local: .$QUIC-GO-PATH/example/client/main -insecure -keylog ssl.log -qlog trial.log -v https://$REMOTE_IPADDR:6121/demo/tile
timeout: no recent network activity
When I go through a wireshark examination, it seems like the CRYPTO handshake never finishes:
Wireshark
Also client Qlog file atteched here:
Qlog file
Codes are all the same with https://github.com/lucas-clemente/quic-go
Help!
This problem has been solved.
Code $QUIC-GO-PATH/example/main.go has binded the port as a default onto 127.0.0.1:6121, which led to the problem that the server cannot get reached by client outside, just get this on server running:
-bind 0.0.0.0:6121
I'm on a workstation that doesn't have a FQDN. I'm developing in Ruby and using the mail gem. I host my own mail server on the LAN. I want to forward outgoing emails to this server, off to a gmail recipient (example).
Due to the fact I'm on my workstation (localhost), it not being recognized as part of one of my LAN domains (I have a static IP), it isn't being recognized by Postfix (from my mail server log):
Mar 25 08:44:30 machine.mydomain1.com postfix/smtpd[9653]: sacl_check: mbr_user_name_to_uuid(mygmail#gmail.com) failed: No such file or directory
Mar 25 08:44:30 machine.mydomain1.com postfix/cleanup[9657]: sacl_check: mbr_user_name_to_uuid(mygmail#gmail.com) failed: No such file or directory
Mar 25 08:44:30 machine.mydomain1.com postfix/smtp[9658]: 92946D63CD4: to=<mygmail#gmail.com>, relay=127.0.0.1[127.0.0.1]:10024, delay=0.14, delays=0.01/0.01/0/0.11, dsn=2.0.0, status=sent (250 2.0.0 from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as AE8ECD63CDA)
Mar 25 08:44:31 machine.mydomain1.com postfix/smtp[9661]: AE8ECD63CDA: to=<mygmail#gmail.com>, relay=gmail-smtp-in.l.google.com[173.194.195.26]:25, delay=0.52, delays=0/0.01/0.34/0.16, dsn=5.7.1, status=bounced (host gmail-smtp-in.l.google.com[173.194.195.26] said: 550-5.7.1 [206.248.184.17 11] Our system has detected that this message is 550-5.7.1 not RFC 5322 compliant: 550-5.7.1 'From' header is missing. 550-5.7.1 To reduce the amount of spam sent to Gmail, this message has been 550-5.7.1 blocked. Please visit 550-5.7.1 https://support.google.com/mail/?p=RfcMessageNonCompliant 550 5.7.1 and review RFC 5322 specifications for more information. a2si7453997iog.10 - gsmtp (in reply to end of DATA command))
Mar 25 08:56:42 machine.mydomain1.com postfix/smtpd[9764]: NOQUEUE: reject: RCPT from unknown[192.168.1.4]: 554 5.7.1 <mygmail#gmail.com>: Relay access denied; from=<alpha#mydomain3.ca> to=<mygmail#gmail.com> proto=ESMTP helo=<mydomain3.ca>
I can use the mail gem properly on another box that has a FQDN just fine. I just can't seem to get it to work on my workstation. As it states in the mail server log:
'From' header is missing. 550-5.7.1 To reduce the amount of spam sent to Gmail, this message has been 550-5.7.1 blocked.
I'm assuming this is the machine name from, and not the email sender from. How can I tell the mail server that I'm not localhost? I've messed with the relay and other directives in postfix to no avail. So I'm trying to modify the Ruby syntax to make the server recognize me.
Any insight appreciated as to how I can get this to work. It's my development box and it's working on my production server, but I'd like to have it working on my dev box.
Adding the following fixed it, a config item for the gem:
mail.header['From'] = 'machine.mydomain.com'
Also making sure the relay information in postfix is set properly.
I am trying to play caller a file before dialing callee with opensips and rtpproxy. I used the makeann from rtpproxy to pre encode a wav file didyou8r1c.wav(mono, 16bit, 8k), which gave didyou8r1c.wav.0 and didyou8r1c.wav.8.
Both files are located in /opt/test/ directory. My invite block is given below.
if (has_body("application/sdp")) {
if (rtpproxy_offer())
t_on_reply("1");
xlog("Trying to Play Caller file");
rtpproxy_stream2uac("/opt/test/didyou8r1c", "-1");
}
But i see this error in rtpproxy logs.
Jan 4 04:07:08 66-226-76-150 rtpproxy[3977]: INFO:GLOBAL:handle_command: play request failed: session ZjU2NDU4Y2M1ODJlYjVmZjNmODY4MGI2MmU5ZTNkZjI., tags 253e361d;1/NONE not found
I hope someone can help me in figuring out what i am doing wrong.
Best Regards.
Frontend developer desperately trying to get a WAMP running on Windows 7 (Home Premium, 64 bit, SP1). I've tried WAMPSERVER and XAMPP. Starting the Apache service failed on both, returning the exact same critical error in their error.log-files:
[Thu Dec 13 14:38:56.905257 2012] [mpm_winnt:crit] [pid 4868:tid 280]
(OS 109)The pipe has been ended. : AH00404: Child: Unable to read
socket data from parent
[Thu Dec 13 14:38:57.028264 2012] [mpm_winnt:crit] [pid 5100:tid 408]
AH00427: Parent: child process exited with status 3 -- Aborting.
I've googled for over 2 hours for this problem and have tried several things. Checking/freeing up Port 80, using a different port, turning off MSSE's real-time protection, disabling LMHOSTS Lookup, dozens of reinstalls... All to no avail.
Please help :(
Go to Control Panel -> Administrative Tools -> Services. Find "Web Deployment Agent Service" right click and stop. Start up Apache and see if it sticks. If so, right click on Web Deployment Agent again and go to properties and set the startup type to Manual.
In my case, the error log was this:
[crit] (OS 109)The pipe has been ended. : setup_inherited_listeners: Unable to read socket data from parent
The solution was that Apache was set to listen on IPv6 interface, but there was no IPv6 interface enabled.