After comparing a pidgin login (debug log)--- 2012.01.27 14:25:08 execute: -> 2012.01.27 14:25:08 execute: Request performed successfully 2012.01.27 14:25:08 execute: <- 2012.01.27 14:25:13 NIOConnection: startTLS: using c2s 2012.01.27 14:25:14 SASLAuthentication: SaslException javax.security.sasl.SaslException: DIGEST-MD5: digest response format violation. Nonexistent realm: voice.myitdepartment.net at com.sun.security.sasl.digest.DigestMD5Server.validateClientResponse(DigestMD5Server.java:430) at com.sun.security.sasl.digest.DigestMD5Server.evaluateResponse(DigestMD5Server.java:244) at org.jivesoftware.openfire.net.SASLAuthentication.handle(SASLAuthentication.java:296) at org.jivesoftware.openfire.net.StanzaHandler.process(StanzaHandler.java:165) at org.jivesoftware.openfire.nio.ConnectionHandler.messageReceived(ConnectionHandler.java:133) at org.apache.mina.common.support.AbstractIoFilterChain$TailFilter.messageReceived(AbstractIoFilterChain.java:570) at org.apache.mina.common.support.AbstractIoFilterChain.callNextMessageReceived(AbstractIoFilterChain.java:299) at org.apache.mina.common.support.AbstractIoFilterChain.access$1100(AbstractIoFilterChain.java:53) at org.apache.mina.common.support.AbstractIoFilterChain$EntryImpl$1.messageReceived(AbstractIoFilterChain.java:648) at org.apache.mina.common.IoFilterAdapter.messageReceived(IoFilterAdapter.java:80) at org.apache.mina.common.support.AbstractIoFilterChain.callNextMessageReceived(AbstractIoFilterChain.java:299) at org.apache.mina.common.support.AbstractIoFilterChain.access$1100(AbstractIoFilterChain.java:53) at org.apache.mina.common.support.AbstractIoFilterChain$EntryImpl$1.messageReceived(AbstractIoFilterChain.java:648) at org.apache.mina.filter.codec.support.SimpleProtocolDecoderOutput.flush(SimpleProtocolDecoderOutput.java:58) at org.apache.mina.filter.codec.ProtocolCodecFilter.messageReceived(ProtocolCodecFilter.java:185) at org.apache.mina.common.support.AbstractIoFilterChain.callNextMessageReceived(AbstractIoFilterChain.java:299) at org.apache.mina.common.support.AbstractIoFilterChain.access$1100(AbstractIoFilterChain.java:53) at org.apache.mina.common.support.AbstractIoFilterChain$EntryImpl$1.messageReceived(AbstractIoFilterChain.java:648) at org.apache.mina.filter.executor.ExecutorFilter.processEvent(ExecutorFilter.java:239) at org.apache.mina.filter.executor.ExecutorFilter$ProcessEventsRunnable.run(ExecutorFilter.java:283) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at org.apache.mina.util.NamePreservingRunnable.run(NamePreservingRunnable.java:51) at java.lang.Thread.run(Thread.java:636)
When I use pidgin, it says no realm used, and it logs in fine. 2012.01.27 14:38:08 execute: -> 2012.01.27 14:38:08 execute: Request performed successfully 2012.01.27 14:38:08 execute: <- 2012.01.27 14:38:09 NIOConnection: startTLS: using c2s 2012.01.27 14:38:10 000137 (01/03/00) - Connection #1 tested: OK 2012.01.27 14:38:10 000138 (01/03/00) - Connection #1 tested: OK 2012.01.27 14:38:10 AuthorizationManager: Trying Default Mapping.map(xxreplaced_was sip users idxx) 2012.01.27 14:38:10 DefaultAuthorizationMapping: No realm found 2012.01.27 14:38:10 AuthorizationManager: Trying Default Policy.authorize(xxreplaced_was sip users idxx , xxwas passwordxx) 2012.01.27 14:38:10 DefaultAuthorizationPolicy: Checking authenID realm 2012.01.27 14:38:10 000138 (01/03/00) - Connection #3 tested: OK 2012.01.27 14:38:10 000139 (01/03/00) - Connection #3 tested: OK 2012.01.27 14:38:10 000139 (01/03/00) - Connection #2 tested: OK 2012.01.27 14:38:10 000140 (01/03/00) - Connection #2 tested: OK 2012.01.27 14:38:10 000140 (01/03/00) - Connection #1 tested: OK 2012.01.27 14:38:10 000141 (02/03/00) - Connection #3 tested: OK 2012.01.27 14:38:10 000142 (02/03/00) - #1 registered a statement as closed which wasn't known to be open. This could happen if you close a statement twice. 2012.01.27 14:38:10 000142 (02/03/00) - Connection #1 tested: OK 2012.01.27 14:38:10 000142 (01/03/00) - Connection #3 tested: OK Sorry for the noise, taking to dev list. On Fri, Jan 27, 2012 at 2:07 PM, Tony Graziano <[email protected]> wrote: > I don't know how fruitful it is to keep beating on this, but: > > /opnefire log... > > > 2012.01.27 13:56:31 Closing session due to exception: (SOCKET, R: > /10.255.251.112:63862, L: /10.255.252.64:5222, S: > 0.0.0.0/0.0.0.0:5222) > org.apache.mina.filter.codec.ProtocolDecoderException: > java.lang.Exception: Disallowed character (Hexdump: 80 62 01 03 01 00 > 39 00 00 00 20 00 00 04 01 00 80 00 00 05 00 00 2F 00 00 33 00 00 32 > 00 00 0A 07 00 C0 00 00 16 00 00 13 00 00 09 06 00 40 00 00 15 00 00 > 12 00 00 03 02 00 80 00 00 08 00 00 14 00 00 11 4F 22 F3 57 83 DD 2E > BF EB F3 97 55 5F C6 B0 82 16 7D E8 8C 77 84 42 3F 4E 33 8D A6 7F FC > 57 33) > at > org.apache.mina.filter.codec.ProtocolCodecFilter.messageReceived(ProtocolCodecFilter.java:170) > at > org.apache.mina.common.support.AbstractIoFilterChain.callNextMessageReceived(AbstractIoFilterChain.java:299) > at > org.apache.mina.common.support.AbstractIoFilterChain.access$1100(AbstractIoFilterChain.java:53) > at > org.apache.mina.common.support.AbstractIoFilterChain$EntryImpl$1.messageReceived(AbstractIoFilterChain.java:648) > at > org.apache.mina.filter.executor.ExecutorFilter.processEvent(ExecutorFilter.java:239) > at > org.apache.mina.filter.executor.ExecutorFilter$ProcessEventsRunnable.run(ExecutorFilter.java:283) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at > org.apache.mina.util.NamePreservingRunnable.run(NamePreservingRunnable.java:51) > at java.lang.Thread.run(Thread.java:636) > Caused by: java.lang.Exception: Disallowed character > at > org.jivesoftware.openfire.nio.XMLLightweightParser.read(XMLLightweightParser.java:211) > at org.jivesoftware.openfire.nio.XMPPDecoder.doDecode(XMPPDecoder.java:32) > at > org.apache.mina.filter.codec.CumulativeProtocolDecoder.decode(CumulativeProtocolDecoder.java:133) > at > org.apache.mina.filter.codec.ProtocolCodecFilter.messageReceived(ProtocolCodecFilter.java:163) > ... 9 more > > This leads me to believe there is a trailing "0" or character being > generated in the openfire configuration file. It happens on a new ISO > install too, so it's a problem that could be investigated. There is an > identical error in the sparkweb forum that indicates simplification of > the config file is needed. While I still think Spark is the problem, I > am starting to wonder if it can be fixed in the configuration. > > > On Fri, Jan 27, 2012 at 1:50 PM, Tony Graziano > <[email protected]> wrote: >> OK. running a pcap with 2.6.3 for a remote user on their firewall (lab here). >> >> 2.5.8 logs in fine, just no extended call info in status (phone >> numbers/names), pidgin displays this fine. >> install 2.6.3, run pcap of the server ip, cant login via IP, hostname >> or servername. Pcap shows NO packet getting to server at far end. Same >> thing with 2.7.x beta. >> >> I think the Smack library you might be using is different somehow, >> because I should see "SOMETHING". Is your server hostname/sipdomain >> name the same? >> >> What's the secret? >> >> >> On Fri, Jan 27, 2012 at 12:51 PM, Tony Graziano >> <[email protected]> wrote: >>> Are you using an Internal SSO or something? Numberous folks can't get >>> past long if using 2.6.3 (not web client, regular app). Does it show >>> "call info" as it is supposed too? >>> >>> I think this is a problem with SPARK/SMACK not knowing how to lookup >>> DNS SRV (again). Did you have to create different records or lter the >>> config in a way to not state sipdomain or hostname in order to use it? >>> >>> >>> On Fri, Jan 27, 2012 at 11:06 AM, Aaron Pursell <[email protected]> wrote: >>>> We're running 2.6.3 Spark with no issues and call detail works fine. On 4.4 >>>> SIPX systems and it works flawlessly between different 4.4 servers as far >>>> as >>>> communication between servers and clients. >>>> >>>> >>>> Aaron Pursell >>>> Network Systems Administration >>>> Easter Seals-Goodwill Northern Rocky Mountain, Inc. >>>> 4400 Central Ave >>>> Great Falls, Montana 59405 >>>> >>>> (406) 771-3721 >>>> [email protected] >>>>>>> Tony Graziano <[email protected]> 1/26/2012 7:35 AM >>> >>>> >>>> No replies needed. I found the 2.7 beta is still labeled as 2.6.3 in >>>> the download link. Unfortunately it still suffers fron not being able >>>> to connect (login) unless you backrev to 2.5.8, which does not show >>>> the callerid in the status. Seems Pidgin works better with Openfire >>>> than Spark (still) does. >>>> >>>> On Thu, Jan 26, 2012 at 9:11 AM, Tony Graziano >>>> <[email protected]> wrote: >>>>> Sorry, it display on the correct status message, it is not providing >>>>> call details in Spark, only Pidgin. At the same time, Spark 2.7 beta >>>>> is listed but there is no download to see if that fixes anything. >>>>> >>>>> On Thu, Jan 26, 2012 at 9:05 AM, Mircea Carasel <[email protected]> wrote: >>>>>> >>>>>> >>>>>> On Thu, Jan 26, 2012 at 3:24 PM, Tony Graziano >>>>>> <[email protected]> wrote: >>>>>>> >>>>>>> Is it normal to assume I cannot see the call info when using Spark but >>>>>>> can when using Pidgin? >>>>>> >>>>>> If I understand correctly, is it about "On the phone" status message? >>>>>> Displaying this info, should not be dependent on what IM client are you >>>>>> using. sipxecs puts a status message in a xmpp presence packet, and >>>>>> basically, any IM XMPP client should be able to display it. AFAIK, both >>>>>> Spark and Pidgin display this info >>>>>> >>>>>> Mircea >>>>>> ---------- >>>>>> Come and see us at CoLab @ CSU in March (5th & 6th) >>>>>> http://www.sipfoundry.org/sipx-colab >>>>>> http://wiki.sipfoundry.org/display/sipXecs/2012+sipX-CoLab+Hackfest >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> ====================== >>>>>>> Tony Graziano, Manager >>>>>>> Telephone: 434.984.8430 >>>>>>> sip: [email protected] >>>>>>> Fax: 434.465.6833 >>>>>>> >>>>>>> Email: [email protected] >>>>>>> >>>>>>> LAN/Telephony/Security and Control Systems Helpdesk: >>>>>>> Telephone: 434.984.8426 >>>>>>> sip: [email protected] >>>>>>> >>>>>>> Helpdesk Customers: http://myhelp.myitdepartment.net >>>>>>> Blog: http://blog.myitdepartment.net >>>>>>> >>>>>>> Linked-In Profile: >>>>>>> http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 >>>>>>> Ask about our Internet Fax services! >>>>>>> _______________________________________________ >>>>>>> sipx-users mailing list >>>>>>> [email protected] >>>>>>> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> sipx-users mailing list >>>>>> [email protected] >>>>>> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >>>>> >>>>> >>>>> >>>>> -- >>>>> ====================== >>>>> Tony Graziano, Manager >>>>> Telephone: 434.984.8430 >>>>> sip: [email protected] >>>>> Fax: 434.465.6833 >>>>> >>>>> Email: [email protected] >>>>> >>>>> LAN/Telephony/Security and Control Systems Helpdesk: >>>>> Telephone: 434.984.8426 >>>>> sip: [email protected] >>>>> >>>>> Helpdesk Customers: http://myhelp.myitdepartment.net >>>>> Blog: http://blog.myitdepartment.net >>>>> >>>>> Linked-In Profile: >>>>> http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 >>>>> Ask about our Internet Fax services! >>>> >>>> >>>> >>>> -- >>>> ====================== >>>> Tony Graziano, Manager >>>> Telephone: 434.984.8430 >>>> sip: [email protected] >>>> Fax: 434.465.6833 >>>> >>>> Email: [email protected] >>>> >>>> LAN/Telephony/Security and Control Systems Helpdesk: >>>> Telephone: 434.984.8426 >>>> sip: [email protected] >>>> >>>> Helpdesk Customers: http://myhelp.myitdepartment.net >>>> Blog: http://blog.myitdepartment.net >>>> >>>> Linked-In Profile: >>>> http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 >>>> Ask about our Internet Fax services! >>>> _______________________________________________ >>>> sipx-users mailing list >>>> [email protected] >>>> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >>>> >>>> _______________________________________________ >>>> sipx-users mailing list >>>> [email protected] >>>> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >>> >>> >>> >>> -- >>> ~~~~~~~~~~~~~~~~~~ >>> Tony Graziano, Manager >>> Telephone: 434.984.8430 >>> sip: [email protected] >>> Fax: 434.465.6833 >>> ~~~~~~~~~~~~~~~~~~ >>> LAN/Telephony/Security and Control Systems Helpdesk: >>> Telephone: 434.984.8426 >>> sip: [email protected] >>> >>> Helpdesk Customers: http://myhelp.myitdepartment.net >>> Blog: http://blog.myitdepartment.net >>> >>> Linked-In Profile: >>> http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 >>> Ask about our Internet Fax services! >> >> >> >> -- >> ~~~~~~~~~~~~~~~~~~ >> Tony Graziano, Manager >> Telephone: 434.984.8430 >> sip: [email protected] >> Fax: 434.465.6833 >> ~~~~~~~~~~~~~~~~~~ >> LAN/Telephony/Security and Control Systems Helpdesk: >> Telephone: 434.984.8426 >> sip: [email protected] >> >> Helpdesk Customers: http://myhelp.myitdepartment.net >> Blog: http://blog.myitdepartment.net >> >> Linked-In Profile: >> http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 >> Ask about our Internet Fax services! > > > > -- > ~~~~~~~~~~~~~~~~~~ > Tony Graziano, Manager > Telephone: 434.984.8430 > sip: [email protected] > Fax: 434.465.6833 > ~~~~~~~~~~~~~~~~~~ > LAN/Telephony/Security and Control Systems Helpdesk: > Telephone: 434.984.8426 > sip: [email protected] > > Helpdesk Customers: http://myhelp.myitdepartment.net > Blog: http://blog.myitdepartment.net > > Linked-In Profile: > http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 > Ask about our Internet Fax services! -- ~~~~~~~~~~~~~~~~~~ Tony Graziano, Manager Telephone: 434.984.8430 sip: [email protected] Fax: 434.465.6833 ~~~~~~~~~~~~~~~~~~ LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected] Helpdesk Customers: http://myhelp.myitdepartment.net Blog: http://blog.myitdepartment.net Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 Ask about our Internet Fax services! -- LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected] Helpdesk Customers: http://myhelp.myitdepartment.net Blog: http://blog.myitdepartment.net _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
