[SFtrack] Resolved: (XECS-1951) Cannot make any Outgoing Gateway Calls 404 & 407 seen in merged logs
[
http://track.sipfoundry.org/browse/XECS-1951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Parfitt resolved XECS-1951.
---------------------------------
Resolution: Duplicate
Duplicate of XECS-1947
> Cannot make any Outgoing Gateway Calls 404 & 407 seen in merged logs
> --------------------------------------------------------------------
>
> Key: XECS-1951
> URL: http://track.sipfoundry.org/browse/XECS-1951
> Project: sipXecs
> Issue Type: Bug
> Affects Versions: 3.11.8
> Environment: Software Communication System (3.11.8-014124
> 2008-11-30T07:23:18)
> Reporter: Chris Parfitt
> Assignee: Chris Parfitt
> Priority: Blocker
> Attachments: merged.xml,
> no_outgoing_gateway_calls_sipx-configuration.tar.gz
>
>
> This issue is being seen since the new Gateway Feature "Restrict the gateway
> by selecting a specific location in which it can be used" has been added to
> the build.
> I have tried adding 2 types of known good Gateways one Audiocodes Mediant
> 1000 and an ITSP a BT BBV SIP Trunk
> This is preventing/b;ocking PV from testing many Gateway scenarios
> Both outgoing Gateway calls are failing with "407 Proxy Authentication" and
> "404 Not found" seen in the traces
> Scenario1:
> Call from User 2005 using BT BBV ITSP trunk
> Dials 901778393331
> Call Fails
> Merge logs Call-Id:
> 94bd9aa0-c07a18b8-13c4-205c-414f9173-205c@xxxxxxxxxxxxxxxxxxxxxxxxxx
> Scenario2:
> Call from User 2005 using Audiocodes Gateway
> Dials 65602602
> Call Fails
> Merge logs Call-Id:
> 94bd9aa0-c07a18b8-13c4-205c-414f9173-205c@xxxxxxxxxxxxxxxxxxxxxxxxxx
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://track.sipfoundry.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
