Might try running 5.6 or 5.8 code to see if that helps.   No reason for it,
but I haven't been running the 6.x code.   Mainly because I haven't seen
anyone state they are working with no issues on it, and I've seen that on
the 5.6 and 5.8 code.

 

From: [email protected]
[mailto:[email protected]] On Behalf Of Tony Graziano
Sent: Tuesday, March 20, 2012 12:32 PM
To: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] Audiocodes MP118 487 Request Terminated

 

Do you have an internal dns table setup on the gateway?

I would turn up the logging level on the gateway and review that to see
where it leads you.

On Mar 20, 2012 3:27 PM, "Jorge E. Fernandez"
<[email protected]> wrote:

Im experiencing an issue with apparently random calls where they go straight
busy tone... It only happens on about 50% of calls that go out through the
gateway. When I trace the calls the gateway returns a "487 Request
Terminated" after the INVITE and when I go through the syslog from the
gateway I find this error while its handling the invite

 

(   lgr_stk_ses)(10026     ) !! [ERROR] SIPStackSession::HandleStackSetupEV
failed because no remote IP

 

The audiocodes is running firmware 6.0 and im running SipXecs 4.4... The
weird thing is that nothing changes from call to call its just that some go
through and some don't. Internal calling is working properly.

 

Help is greatly appreciated.

 

Regards,

 

--

Jorge E. Fernandez
IT Specialist
J9 IT Consultants

[email protected]
http://j9consultants.com - @jef2904






 


_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/

 

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/

Reply via email to