Question : Audiocodes VOIP gateway being refused by Vertical Televantage system

My gateway device is being refused by the SIP phone server (see attached log snipped). Any ideas as to why? I have another gateway (same model) that works fine. I even loaded the operational config file onto the problem device, and no go. Something isnt right, but I dont know what it is.

"'SDP_ERROR_MALFORMED_NUMBER')" doesn't help me any.

Code Snippet:

1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
28:
29:

1d:7h:30m:57s (     sip_stack)(1137      )  UdpRtxMngr::Remove 1 INVITE
 
1d:7h:30m:57s (      lgr_flow)(1138      )  |       |(SIPTU#10)100 State:Inviting([email protected])
 
1d:7h:30m:57s (     sip_stack)(1139      )  SIPCall(#10) changes state from Inviting to Proceeding
 
1d:7h:30m:57s (      lgr_flow)(1140      )  |       |       |       #4:SIP_TRYING_EV([email protected])
 
1d:7h:30m:57s (   lgr_stk_ses)(1141      )   SendToCall - event: PROCEEDING  m_Call = 31718960
 
1d:7h:30m:57s (      lgr_flow)(1142      )  |       |       #4:PROCEEDING:([email protected])
 
1d:7h:30m:57s (      lgr_flow)(1143      )  |       #1:PROCEEDING   : ([email protected])
 
1d:7h:30m:57s (      lgr_flow)(1144      )  ---- Incoming SIP Message from 192.168.50.5:5060 ----
 
1d:7h:30m:57s SIP/2.0 400 Bad Request
Call-ID: [email protected]
CSeq: 1 INVITE
From: "InSite Services" ;tag=1c1143429621
To:

Open in New Window

Select All

Answer : Audiocodes VOIP gateway being refused by Vertical Televantage system

Can you do a screen Wireshark capture of the known good gateway with Televantage system. Then a test with the known bad system. Then maybe attach the files.

Also have you reversed the procedure? Take the known bad configuration and place it on the known good system and vice versa. The goal is to isolate is it a bad piece of hardware or bad configuration. Also making sure we are usign the same login credentials when testing. Also even make sure that we are testing the physical layer making sure that is not even the culprit.

Also are you using the same firmware on each system?

Joel