well, looks like you are using sipXbridge to talk to the Edgemark... i don't think you want to do this.
try to setup the edgemark as an unmanaged gateway, i assume the trunk terminates on it. mike On Fri, Apr 6, 2012 at 11:53 AM, Mike Moulton <[email protected]> wrote: > Thank you both for details of your experience with Edgemarc devices. > Unfortunately this is my only options with this provided. So I will either > need to get it working, switch providers or switch away from sipx. > > I was able to get some logs from the edgemarc for a failed call we had > yesterday. Ultimately it looks like the sipx bridge replied to the edgemarc > with an SIP 500, where the bridge error was 213. I think that is a timeout > error if I'm correct. Now the question is why it would have timed out on > our end. > > Any thoughts would be very helpful on this issue. > > Below is the output sent to me by my provider. > > 17:24:50.996347 172.22.2.29.5060 > 172.22.2.10.5060:**** > > >>>>>>>>>>>>>>>sip header start>>>>>>>>>>>>>>>>>>>**** > > INVITE sip:[email protected]:5060;transport=udp SIP/2.0**** > > **** > > Via: SIP/2.0/UDP 172.22.2.29:5060 > ;branch=z9hG4bK-BroadWorks.as1-66.226.228.163V5060-0-29672815-417224082-1333646691036- > **** > > **** > > Record-Route: <sip:[email protected];lr>**** > > **** > > From: "LEWIS,CHRIS" <sip:[email protected]:5060 > ;user=phone>;tag=417224082-1333646691036-**** > > **** > > To: "6026486802 6026486802" <sip:[email protected]:5060>**** > > **** > > Call-ID: [email protected]**** > > **** > > CSeq: 29672815 INVITE**** > > **** > > Contact: <sip:172.22.2.29:5060>**** > > **** > > **Support**ed:**** > > **** > > Max-forwards: 50**** > > **** > > Content-disposition: session;handling=required**** > > **** > > Allow: ACK, BYE, CANCEL, INFO, INVITE, OPTIONS, PRACK, REFER, NOTIFY, > UPDATE**** > > **** > > Content-Type: application/sdp**** > > **** > > Accept: multipart/mixed, application/media_control+xml, application/sdp*** > * > > **** > > Content-Length: 284**** > > **** > > ** ** > > ** ** > > v=0**** > > **** > > o=BroadWorks 35399080 1 IN IP4 172.22.2.29**** > > **** > > s=-**** > > **** > > c=IN IP4 172.22.2.29**** > > **** > > t=0 0**** > > **** > > m=audio 16616 RTP/AVP 0 8 18 101**** > > **** > > a=rtpmap:0 PCMU/8000**** > > **** > > a=rtpmap:8 PCMA/8000**** > > **** > > a=rtpmap:18 G729/8000**** > > **** > > a=fmtp:18 annexb=no**** > > **** > > a=rtpmap:101 telephone-event/8000**** > > **** > > a=fmtp:101 0-15**** > > **** > > a=sendrecv**** > > **** > > a=maxptime:20**** > > **** > > ** ** > > <<<<<<<<<<<<<<<sip header stop<<<<<<<<<<<<<<<<<<<<**** > > [tos 0xb8]**** > > 17:24:50.999378 172.22.2.10.5060 > 172.22.2.29.5060:**** > > >>>>>>>>>>>>>>>sip header start>>>>>>>>>>>>>>>>>>>**** > > SIP/2.0 100 Trying**** > > **** > > Record-Route: <sip:[email protected];lr>**** > > **** > > From: "LEWIS,CHRIS" <sip:[email protected]:5060 > ;user=phone>;tag=417224082-1333646691036-**** > > **** > > To: "6026486802 6026486802" <sip:[email protected]:5060>**** > > **** > > Call-Id: [email protected]**** > > **** > > Cseq: 29672815 INVITE**** > > **** > > Via: SIP/2.0/UDP 172.22.2.29:5060 > ;branch=z9hG4bK-BroadWorks.as1-66.226.228.163V5060-0-29672815-417224082-1333646691036- > **** > > **** > > Content-Length: 0**** > > **** > > ** ** > > ** ** > > <<<<<<<<<<<<<<<sip header stop<<<<<<<<<<<<<<<<<<<<**** > > [tos 0xb8]**** > > 17:24:51.779598 172.22.2.10.5060 > 172.22.2.29.5060:**** > > >>>>>>>>>>>>>>>sip header start>>>>>>>>>>>>>>>>>>>**** > > SIP/2.0 500 Server Internal Error**** > > **** > > Via: SIP/2.0/UDP 172.22.2.29:5060 > ;branch=z9hG4bK-BroadWorks.as1-66.226.228.163V5060-0-29672815-417224082-1333646691036- > **** > > **** > > From: "LEWIS,CHRIS" <sip:[email protected]:5060 > ;user=phone>;tag=417224082-1333646691036-**** > > **** > > To: "6026486802 6026486802" <sip:[email protected]:5060>**** > > **** > > Call-Id: [email protected]**** > > **** > > Cseq: 29672815 INVITE**** > > **** > > Server: sipXecs/4.4.0 sipXecs/sipxbridge (Linux)**** > > **** > > **Support**ed: replaces**** > > **** > > Contact: <sip:[email protected]:5080>**** > > **** > > Reason: ~~id~bridge;cause=213;text="Relayed Error Response"**** > > **** > > Content-Length: 0**** > > **** > > Date: Thu, 05 Apr 2012 17:24:51 GMT > > > > > On Wed, Apr 4, 2012 at 10:41 AM, Tony Graziano < > [email protected]> wrote: > >> Edgewater has a horribly written interface for iptables. >> >> Funny you say that. I just did a brief interop with airespring which went >> well, but the final deployment will be using an edgewater. I am going to >> ask them to provide an interface on the edgewater to be on the same IP >> network as sipx and simply use it as an unmanaged gateway because they will >> be using an MPLS connection from airespring. >> >> Beyond that upcoming test the only use I've had for them was a door stop >> or paperweight (great during tax season). >> >> Can you get a siptrace from sipx with proxy set to debug levels? >> >> If the EDGMEARC thingy is setup as an unmanaged gateway (preferred) then >> the only thing we can glean from a siptrace at sipx is what it sent and >> what it was sent back to make it fail. The links above provide >> ZERO meaningful insight into any call (both say request denied, from what, >> noone knows). >> >> Beyond that, a pcap from your edgmarc might prove to give other >> information. >> >> >> >> >> On Wed, Apr 4, 2012 at 1:12 PM, Michael Picher <[email protected]> wrote: >> >>> Edgewater... run away! >>> >>> I'd start with those guys. I've not been able to make them work but >>> have not spent 'quality' time with their tech support. >>> >>> Mike >>> >>> >>> >>> On Wed, Apr 4, 2012 at 12:56 PM, Mike Moulton <[email protected]>wrote: >>> >>>> I'm experiencing some intermittent call failures and I'm having trouble >>>> diagnosing the problem. About 50% of the time when a user dials out, they >>>> will receive a fast busy, the other times the call goes through as >>>> expected. Once a call is established there are times when the call will be >>>> disconnected in the middle of a conversation. I'm not sure of the frequency >>>> of the dropped called, but it seems to be less often than the fast busy on >>>> dial out. >>>> >>>> Our setup consists of Polycom phones [650,331,335] connected to sipx >>>> v4.4.0. Our service provided has installed a Edgewater 4550 SBC that is >>>> setup as a SIP Trunk gateway. >>>> >>>> I have captures traces of two calls, the first is a failure, the second >>>> is the same call successful. >>>> >>>> Failed Trace: >>>> http://mmoulton-sipx.s3.amazonaws.com/trace-mmoulton-failed. xml >>>> Success Trace: >>>> http://mmoulton-sipx.s3.amazonaws.com/trace-mmoulton-success .xml >>>> >>>> Any help would be greatly appreciated. >>>> >>>> On a side note, where would you recommend I look for paid support to >>>> resolve this issue if the list is unable to easily help? >>>> >>>> Thanks! >>>> >>>> _______________________________________________ >>>> sipx-users mailing list >>>> [email protected] >>>> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >>>> >>> >>> >>> >>> -- >>> Michael Picher, Director of Technical Services >>> eZuce, Inc. >>> >>> 300 Brickstone Square**** >>> >>> Suite 201**** >>> >>> Andover, MA. 01810 >>> O.978-296-1005 X2015 >>> M.207-956-0262 >>> @mpicher <http://twitter.com/mpicher> >>> www.ezuce.com >>> >>> >>> ------------------------------------------------------------------------------------------------------------ >>> There are 10 kinds of people in the world, those who understand binary >>> and those who don't. >>> >>> >>> _______________________________________________ >>> 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 >> ~~~~~~~~~~~~~~~~~~ >> 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].**net<[email protected]> >> >> Helpdesk Customers: >> http://myhelp.myitdepartment.**net<http://myhelp.myitdepartment.net> >> Blog: http://blog.myitdepartment.net >> >> _______________________________________________ >> sipx-users mailing list >> [email protected] >> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >> > > > > -- > Mike Moulton > [email protected] > 602.432.2568 | iphone > 602.648.6810 | office > mmoulton | twitter > > > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > -- Michael Picher, Director of Technical Services eZuce, Inc. 300 Brickstone Square**** Suite 201**** Andover, MA. 01810 O.978-296-1005 X2015 M.207-956-0262 @mpicher <http://twitter.com/mpicher> www.ezuce.com ------------------------------------------------------------------------------------------------------------ There are 10 kinds of people in the world, those who understand binary and those who don't.
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
