Federico Beffa <beffa@...> writes:
Hi Anthony,
thanks for the clarification and the suggestion. As an immediate workaround I would like to try the "cron" approach you suggested. I have therefore experimented a little bit with the chat api command.
My jingle_profiles/client.xml looks essentially as the one provided with the example configuration:
<profile type="client"> <param name="name" value="$${xmpp_client_profile}"/> <param name="login" value="user1@.../talk"/> <param name="password" value="XXXX"/> <param name="dialplan" value="XML"/> <param name="context" value="public"/> <param name="message" value="Jingle all the way"/> <param name="rtp-ip" value="$${bind_server_ip}"/> <param name="ext-rtp-ip" value="auto-nat"/> <param name="auto-login" value="true"/> <!-- SASL "plain" or "md5" --> <param name="sasl" value="plain"/> <!-- if the server where the jabber is hosted is not the same as the one in the jid --> <param name="server" value="talk.google.com"/> <!-- Enable TLS or not --> <param name="tls" value="true"/> <!-- disable to trade async for more calls --> <param name="use-rtp-timer" value="true"/> <!-- default extension (if one cannot be determined) --> <param name="exten" value="888"/> <!-- VAD choose one --> <!-- <param name="vad" value="in"/> --> <!-- <param name="vad" value="out"/> --> <!--<param name="vad" value="both"/>--> <!--<param name="avatar" value="/path/to/tiny.jpg"/>--> <!--<param name="candidate-acl" value="wan.auto"/>--> <param name="local-network-acl" value="localnet.auto"/> </profile>
When I try to use the chat command at the fs_cli prompt I'm unable to form a full jid and always get an error message from the remote server. Here an example:
chat jingle|888 <at> xmppc|user2@...|test
Sent freeswitch <at> ubuntu-vbox-t5500> 2011-10-08 14:22:09.804596 [NOTICE] libdingaling.c:1373 SecSEND: ------------------------------------------------------------------------------
<message to="user2@..." type="chat" from="user1@..."> <body>test</body> </message>
2011-10-08 14:22:09.844698 [INFO] libdingaling.c:1371 SecRECV: ------------------------------------------------------------------------------
- -
<message to="user1@..." type="error" from="user2@..."> <body>test</body> <error code="400" type="modify"> <bad-request xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"></bad-request> <text xmlns="urn:ietf:params:xml:ns:xmpp-stanzas">If set, the 'from' attribute must be set to the user's full JID.</text> </error> </message>
"xmppc" is the value of the variable "xmpp_client_profile" as in the default config. I get the same error independently from what I set before "@xmppc" in the from_jid. Differently from this, if as the from_jid I set my explicit jid "user1@.../talk" as in the client.xml file I get the error:
2011-10-08 14:20:50.446696 [ERR] mod_dingaling.c:544 Invalid Profile gmail.com
Despite the fact that even a wrong message reaching the remote server could work as a "keep alive" signal, I still would like to understand the proper syntax. I would be grateful if somebody could explain me what is the correct syntax to use with chat and jingle?
Thank you! Fede
P.S.: By the way, I'm now working on HEAD.
Hi Federico and Anthony, Were you guys able to come up with a solution for this? I had mine working for about a month without any problems. I'm running the git version from October 1, 2011. I just ran into the same problem after changing my router since I changed my Internet connection from DSL to fiber optic. Reading the comments from this post: http://www.personal.psu.edu/wcs131/blogs/psuvoip/2010/10/using_freeswitch_to... _google.html I guess this is an issue with Freeswitch having problems when there are Internet disconnections. I guess one way to solve this would be to change my router, but I don't really want to buy another ONT router, besides I don't even know if my ISP would let me use a different ONT since the ones that they provide are all "customized". It is really hard to tell when it has disconnected. Even when typing "dingaling status" from the fs_cli, it will show AUTHORIZED when it is disconnected. The only way to tell if it's been disconnected is checking whether I can make calls or not. To solve this ,without having to restart freeswitch I would "disconnect" (according to FS) from my gtalk profile typing "dl_logout gtalk" and reconnect with "dl_login profile=gtalk". I also had the idea to use the "cron" approach and thought this was going to be the solution to all my problems. Of course, I had to test what would happen if the cron job would happen to run in the middle of a call. I manually typed the commands on the fs_cli while I was on a call and my call did not die!! Great!! I had the solution to the problem!! I then finished the call and ooohh surprise!! I was suddenly disconnected from the fs_cli, FS would die, close unexpectedly and create a core dump. I would really like to help to solve this so let me know if there's any way I can help out. I would like to try the chat approach to see if that works. Did you figure out what is the right syntax to chat? Greetings, Ricardo