AudioCodes with 14.10

402 views
Skip to first unread message

Michael Picher

unread,
Feb 19, 2015, 6:48:38 PM2/19/15
to sipxco...@googlegroups.com
fyi, if anybody is looking to go to 14.10, have AudioCodes firmware 6.60 on hand...

--

Michael Picher, VP of Product Management
eZuce, Inc.

300 Brickstone Square

Suite 104

Andover, MA. 01810


tlwy...@gmail.com

unread,
Feb 20, 2015, 1:52:30 PM2/20/15
to sipxco...@googlegroups.com
Thank for posting - sometimes import information like this gets lost in the process and we find out the hard way................

Tony Wyland
Messiah College

Melcon Moraes

unread,
Mar 5, 2015, 9:16:11 AM3/5/15
to Michael Picher, sipxco...@googlegroups.com
Mike, 

For MP-124 as well?

-
MM


--
You received this message because you are subscribed to the Google Groups "sipxcom-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-user...@googlegroups.com.
Visit this group at http://groups.google.com/group/sipxcom-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/CAAHujP7RwuS%3DffG%3DsTZY1Zx%3DhQ8dmgqzWHZjYG5C6Z8g5XwW8g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Michael Picher

unread,
Mar 6, 2015, 11:03:19 AM3/6/15
to sipxco...@googlegroups.com, mpi...@ezuce.com
This issue was referring to inbound calling.  I have no data on station gateways...  sorry, i should have been more clear.

Mike

Melcon Moraes

unread,
Mar 12, 2015, 2:03:12 PM3/12/15
to Michael Picher, sipxco...@googlegroups.com
Ok.

For incoming then, let's say a M1K, would you please elaborate a bit on that? What was the issue found with firmware below 6.6? I'm starting to test with firmware 6.4.

-
MM

To post to this group, send email to sipxco...@googlegroups.com.

arturojg...@gmail.com

unread,
Mar 12, 2015, 2:25:19 PM3/12/15
to sipxco...@googlegroups.com
How I can get a copy of that firmware ? ( art...@siei.mx)

Michael Picher

unread,
Mar 12, 2015, 3:01:27 PM3/12/15
to arturojg...@gmail.com, sipxco...@googlegroups.com
It's available from AudioCodes if you have a service contract, or where you purchased the gateways from.

Mike


Michael Picher, VP of Product Innovation

eZuce, Inc.

300 Brickstone Square

Suite 104

Andover, MA. 01810


Notice: This transmittal and/or attachments may be privileged or confidential. It is intended solely for the addressee(s) named above. Any dissemination, or copying is strictly prohibited. If you received this transmittal in error, please notify us immediately by reply and immediately delete this message and all its attachments. Thank you. FMS

--
You received this message because you are subscribed to the Google Groups "sipxcom-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-user...@googlegroups.com.
To post to this group, send email to sipxco...@googlegroups.com.
Visit this group at http://groups.google.com/group/sipxcom-users.

Michael Picher

unread,
Mar 12, 2015, 3:22:34 PM3/12/15
to Melcon Moraes, sipxco...@googlegroups.com
Not sure exactly what was going on as we were remote...  I don't have any captures or anything.  The config all looked fine to me.  We even dropped in a new config from the server generated .ini file to no avail.  

I suspect some sort of signaling issue that got sorted out in their newer builds...  because that was our last resort.

Mike


Michael Picher, VP of Product Innovation

eZuce, Inc.

300 Brickstone Square

Suite 104

Andover, MA. 01810


Notice: This transmittal and/or attachments may be privileged or confidential. It is intended solely for the addressee(s) named above. Any dissemination, or copying is strictly prohibited. If you received this transmittal in error, please notify us immediately by reply and immediately delete this message and all its attachments. Thank you. FMS

Mihai Costache

unread,
Mar 13, 2015, 2:15:01 AM3/13/15
to Michael Picher, Melcon Moraes, sipxco...@googlegroups.com
Hi Melcon,
The problem with Audiocodes and sipxcom 14.10 was that on below version Audiocodes didn't parsed messages correctly: A REFER sip:40583 ... message sent from sipxcom seen corectly formatted on packet capture will be seen in Audiocodes logs like:

R sip:40583...

19d:15h:26m:4s R sip:40...@172.16.14.103:5060;x-sipX-nonat SIP/2.0 Via: SIP/2.0/TCP 172.27.14.43;branch=z9hG4bK-XX-4c80_KZKstptIr9XNyVsqJp6iQ Via: SIP/2.0/UDP 172.27.14.43:15060;rport=15060;branch=z9hG4bKce328XH151yND Max-Forwards: 20 From: <sip:77...@fictivedomain.com;user=phone>;

Best Regards,
Mihai Costache

"No problem can withstand the assault of sustained thinking. "

                                -  Voltaire



Michael Picher

unread,
Mar 13, 2015, 2:49:49 AM3/13/15
to Mihai Costache, Melcon Moraes, sipxco...@googlegroups.com
Thanks Mihai.  Sounds like you ran into this with another customer...  :-)

Mike


Michael Picher, VP of Product Innovation
eZuce, Inc.

300 Brickstone Square

Suite 104

Andover, MA. 01810


Notice: This transmittal and/or attachments may be privileged or confidential. It is intended solely for the addressee(s) named above. Any dissemination, or copying is strictly prohibited. If you received this transmittal in error, please notify us immediately by reply and immediately delete this message and all its attachments. Thank you. FMS

Mihai Costache

unread,
Mar 13, 2015, 2:52:54 AM3/13/15
to Michael Picher, Melcon Moraes, sipxco...@googlegroups.com
Unfortunately yes, but once learned ...

Best Regards,
Mihai Costache

"No problem can withstand the assault of sustained thinking. "

                                -  Voltaire



Melcon Moraes

unread,
Mar 14, 2015, 9:14:30 PM3/14/15
to Mihai Costache, Michael Picher, sipxco...@googlegroups.com
Thanks for the info Mihai.

-
MM

Melcon Moraes

unread,
Mar 17, 2015, 6:42:41 PM3/17/15
to Mihai Costache, Michael Picher, sipxco...@googlegroups.com
Hello, Mihai.

I think I ran into the same issue you described.

I see this on the logs:

Mar 17 17:13:53 TE sip: 10...@10.108.10.14:5060;x-sipX-nonat SIP/2.0#015#012Record-Route: <sip:10.108.10.21:5060;lr;sipXecs-CallDest=AL%2CINT;sipXecs-rs=%2Aauth%7E.%2Afrom%7EMWMxMzIyNTU0NzQ5%21d0c1a718eebfa4cd572e1ea031a2cc58>#015#012Via: SIP/2.0/TCP 10.108.10.21;branch=z9hG4bK-XX-c708QuXksX_IKs7Ec`485HMIGg#015#012Via: SIP/2.0/TCP 10.108.10.21;branch=z9hG4bK-XX-c705j3T5kwpPlmUAg5zqmkRedQ~gspsR4itoIUH5Ihy3otbsg#015#012Via: SIP/2.0/UDP 10.108.10.21;branch=z9hG4bK-XX-c6ffRs36T6btrk2o4kqrszZKlQ~JCqOkN28ITX7o3EWaSYXsQ#015#012Via: SIP/2.0/UDP 10.108.10.13;branch=z9hG4bKac1322790832#015#012Max-Forwards: 16#015#012From: <sip:11518...@uc.corp.local>;tag=1c1322554749#015#012To: <sip:00...@uc.corp.local;user=phone>#015#012Call-Id: 13225119441...@10.108.10.13#015#012Cseq: 1 INVITE#015#012Contact: <sip:11518...@10.108.10.13:5060;x-sipX-nonat>#015#012Supported: em,100rel,timer,replaces,path,resource-priority,sdp-anat#015#012Allow: REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,INFO,SUBSCRIBE,UPDATE#015#012User-Agent: Audiocodes-Sip-Gateway-Mediant 1000 - MSBG/v.6.40A.045.006#015#012Content-Type: application/sdp#015#012Content-Length: 233#015#012Date: Tue, 17 Mar 2015 20:13:52 GMT#015#012X-Sipx-Authidentity: <sip:00...@uc.corp.local;signature=55088B00%3A8b4429176366be75b8f54e571da91279>#015#012Exp [Time: 17:13:52]



It seems to happen only when the transport is TCP. Instead of an INVITE, it got only TE. Also, there is this logs as well:

Mar 17 17:13:53 10.108.10.14 (     sip_stack)(13982     )  AcSIPParser: Problem in SIP Message Headers [Time: 17:13:52]
Mar 17 17:13:53 10.108.10.14 (     sip_stack)(13983     ) !! [ERROR] AcSIPParser: Parse Error. Unexpected symbol '#015'. Expected token [Time: 17:13:52]
Mar 17 17:13:53 10.108.10.14 (     sip_stack)(13984     ) !! [ERROR] Message type:  [Time: 17:13:52]
Mar 17 17:13:53 10.108.10.14 (     sip_stack)(13985     ) !! [ERROR] Source header:  [Time: 17:13:52]
Mar 17 17:13:53 10.108.10.14 (     sip_stack)(13986     ) !! [ERROR] Line: 1. Column: 1 [Time: 17:13:52]
Mar 17 17:13:53 10.108.10.14 (     sip_stack)(13987     )  One of the basic headers (To, From, CSeq, Call-Id, Via) is missing in the message [Time: 17:13:52]
Mar 17 17:13:53 10.108.10.14 (     sip_stack)(13988     ) !! [ERROR] SIPTransportMngr::HandleReceivedMessage - Basic error in Message [Time: 17:13:52]


Which indicates a parsing error: Unexpected symbol '#015'


From the logs, I would assume that #015 and #012 are \r and \n respectively, but the decimals does not match the actual value of \r and \n.
Any ideas no how or why would that start to happen on 14.10? I don't see it occour with 14.04. Just trying to understand what changed and where.

Thanks in advance.

-
MM

Michael Picher

unread,
Mar 17, 2015, 7:29:26 PM3/17/15
to Melcon Moraes, Mihai Costache, sipxco...@googlegroups.com
We have a fix coming in 15.04:

XX-11552XX-11585 UC-2921 Prevents Audiocodes gateways from working correctly when using TCPFixed an issue caused by UC-2921 where after upgrade to 14.10 Audiocodes FXS gateways would lose their registration status and sip calls over TCP connections would work once but fail after the first call.Bug


Michael Picher, VP of Product Innovation
eZuce, Inc.

300 Brickstone Square

Suite 104

Andover, MA. 01810


Notice: This transmittal and/or attachments may be privileged or confidential. It is intended solely for the addressee(s) named above. Any dissemination, or copying is strictly prohibited. If you received this transmittal in error, please notify us immediately by reply and immediately delete this message and all its attachments. Thank you. FMS

Reply all
Reply to author
Forward
0 new messages