< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index Next in Thread >

[SFtrack] Updated: (XECS-1947) Calls through gateways fail with a 404 Not Found.


     [ 
http://track.sipfoundry.org/browse/XECS-1947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chaitra Sharma updated XECS-1947:
---------------------------------

    Description: 
Case1:
Precondition:
1. Install the test machine with build
2. Users 440, 441 are registered to SCS.
3. User 440 and 441 have International dialing permission.
3. Navigate to Devices-->Gateways and add an 'Unmanaged gateway' as follows:
    Name = Test_gateway
    Address = 176.25.2.114
    Location = -- all --
    Shared = unchecked
    Port = 0
    Transport protocol = Auto
4. Navigate to System-->Dial Plans and click on the default International dial 
rule.
5. Add the gateway as 'Test_gateway and enable the dial rule.
6. Activate the dial plans.

Steps to reproduce:
>From user 440 dial the international number 011-12345678.

Expected response:
The call should go through the gateway.

Actual Response:
1. The call gets disconnected on 440
2. The logs show sipregistrar sending a '404 Not found' response.
Call id: 94bdf5b0-b01902dc-13c4-542-6bb4fddd-542
Snapshot: snapshot_404_Not_Found.tar.gz

Case2:
Precondition:
1. Navigate to Users-->User groups and create a user group 'OutboundGroup'
2. Add users 440 and 441 to this group.
3. Navigate to Devices-->Gateways -->Test_gateway and select the Location = 
OutboundGroup
4. Activate the Dial Plans.

Steps to reproduce:
>From user 440 dial the international number 011-123456789

Actual Response:
1. The call gets disconnected on 440.
2. The logs show sipregistrar responding with a '404 Not found' response
3. The Fallbackrules.xml correctly display the 
<callerLocation>OutboundGroup</callerLocation>
4. the userlocation.xml correctly displays the users in the user group assigned 
to Location.
Call id: 94bdf408-b01902dc-13c4-685-27359875-685
Snapshot: snapshot_after_Location_is_set.tar.gz

  was:
Case1:
Precondition:
1. Install the test machine with build
2. Users 440, 441 are registered to SCS.
3. User 440 and 441 have International dialing permission.
3. Navigate to Devices-->Gateways and add an 'Unmanaged gateway' as follows:
    Name = Test_gateway
    Address = 176.25.2.114
    Location = -- all --
    Shared = unchecked
    Port = 0
    Transport protocol = Auto
4. Navigate to System-->Dial Plans and click on the default International dial 
rule.
5. Add the gateway as 'Test_gateway and enable the dial rule.
6. Activate the dial plans.

Steps to reproduce:
>From user 440 dial the international number 011-12345678.

Expected response:
The call should go through the gateway.

Actual Response:
1. The call gets disconnected on 440
2. The logs show sipregistrar sending a '404 Not found' response.
Call id: 94bdf5b0-b01902dc-13c4-542-6bb4fddd-542
Snapshot: snapshot_404_Not_Found.tar.gz

Case2:
Precondition:
1. Navigate to Users-->User groups and create a user group 'OutboundGroup'
2. Add users 440 and 441 to this group.
3. Navigate to Devices-->Gateways -->Test_gateway and select the Location = 
OutboundGroup
4. Activate the Dial Plans.

Steps to reproduce:
>From user 440 dial the international number 011-123456789

Actual Response:
1. The call gets disconnected on 440.
2. The logs show sipregistrar responding with a '404 Not found' response
3. The Fallbackrules.xml correctly display the 
<callerLocation>OutboundGroup</callerLocation>
4. the userlocation.xml correctly displays the users in the user group assigned 
to Location.
Call id: 94bdf0b8-b01902dc-13c4-277-29759a46-277
Snapshot: snapshot_after_setting_location.tar.gz


> Calls through gateways fail with a 404 Not Found.
> -------------------------------------------------
>
>                 Key: XECS-1947
>                 URL: http://track.sipfoundry.org/browse/XECS-1947
>             Project: sipXecs
>          Issue Type: Bug
>    Affects Versions: 3.11.8
>         Environment: sipxproxy 3.11.8-014120 2008-11-27T21:54:01 oem-centos5
> sipxconfig 3.11.8-014120 2008-11-27T22:06:35 oem-centos5
>            Reporter: Chaitra Sharma
>            Priority: Critical
>         Attachments: snapshot_404_Not_Found.tar.gz, 
> snapshot_after_Location_is_set.tar.gz
>
>
> Case1:
> Precondition:
> 1. Install the test machine with build
> 2. Users 440, 441 are registered to SCS.
> 3. User 440 and 441 have International dialing permission.
> 3. Navigate to Devices-->Gateways and add an 'Unmanaged gateway' as follows:
>     Name = Test_gateway
>     Address = 176.25.2.114
>     Location = -- all --
>     Shared = unchecked
>     Port = 0
>     Transport protocol = Auto
> 4. Navigate to System-->Dial Plans and click on the default International 
> dial rule.
> 5. Add the gateway as 'Test_gateway and enable the dial rule.
> 6. Activate the dial plans.
> Steps to reproduce:
> From user 440 dial the international number 011-12345678.
> Expected response:
> The call should go through the gateway.
> Actual Response:
> 1. The call gets disconnected on 440
> 2. The logs show sipregistrar sending a '404 Not found' response.
> Call id: 94bdf5b0-b01902dc-13c4-542-6bb4fddd-542
> Snapshot: snapshot_404_Not_Found.tar.gz
> Case2:
> Precondition:
> 1. Navigate to Users-->User groups and create a user group 'OutboundGroup'
> 2. Add users 440 and 441 to this group.
> 3. Navigate to Devices-->Gateways -->Test_gateway and select the Location = 
> OutboundGroup
> 4. Activate the Dial Plans.
> Steps to reproduce:
> From user 440 dial the international number 011-123456789
> Actual Response:
> 1. The call gets disconnected on 440.
> 2. The logs show sipregistrar responding with a '404 Not found' response
> 3. The Fallbackrules.xml correctly display the 
> <callerLocation>OutboundGroup</callerLocation>
> 4. the userlocation.xml correctly displays the users in the user group 
> assigned to Location.
> Call id: 94bdf408-b01902dc-13c4-685-27359875-685
> Snapshot: snapshot_after_Location_is_set.tar.gz

-- 
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