SIPfoundry Issue Tracker

  • Log In Access more options
    • Online Help
    • GreenHopper Help
    • Agile Answers
    • Use Agile By Default
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What’s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
  • Agile Access more options
    • Planning Board
    • Task Board
    • Chart Board
    • Released Board
    • Rapid Board
    • Manage Rapid Boards
    • Getting Started
  • sipXecs
  • XX-4444

Unable to transfer calls to hunt group, conference extensions through Auto Attendant.

  • Rapid Board
  • More Actions
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: 3.11, 4.0.0
  • Component/s: None
  • Labels:
    None
  • Environment:
    sipxproxy 3.11.9-014238 2008-12-11T01:13:12 oem-centos5
    sipxconfig 3.11.9-014238 2008-12-11T01:25:54 oem-centos5

Description

Precondition:
1. Users 330, 331 and 144 are registered to SCS
2. Add a hunt group with extension 555 having users 331 and 144 with following call sequence:
    Initially call 331 for 30 sec
    If no response 114 for 30 sec

Steps to reproduce:
1. From 330, dial 100
2. When the auto attendant prompt, prompts for party's extension , enter the hunt group extension 555

Expected Result:
The prompt 'Please hold while I transfer your call" should be heard and the call should be transfered to users in the hunt group.

Actual Result:
The call is not transfered and the prompt "That extension is not valid" is played followed by the auto attendant prompt.
Call-Id: 94be0498-b01902d8-13c4-3a5-79ecfea0-3a5

Observation:
1. Transferring the call through auto attendant to any other SCS extension works as expected.
2. This issue occurs for virtual lines like hunt group extension, conference extension, possibly even for ACD line(not tested due to XCF-3106)
3. This scenario works as expected in 3.10.3-014059
  • Options
    • Sort By Name
    • Sort By Date
    • Ascending
    • Descending
    • Download All

Attachments

  1. GZip Archive
    snapshot_Autoattendant_transfer_to_huntgroup_fails.tar.gz
    2008-12-12 04:16
    574 kB
    Chaitra Sharma

Activity

Ascending order - Click to sort in descending order
  • All
  • Comments
  • Work Log
  • History
  • Activity
Hide
Permalink
Scott Lawrence added a comment - 2008-12-12 11:33
I don't know that we want it to work for conferences, but hunt groups and acd queues seem reasonable since they are the sort of numbers one would want to give to outside parties.
Show
Scott Lawrence added a comment - 2008-12-12 11:33 I don't know that we want it to work for conferences, but hunt groups and acd queues seem reasonable since they are the sort of numbers one would want to give to outside parties.
Hide
Permalink
Andy Spitzer added a comment - 2008-12-16 09:45
When I spec'ed the new AA, I was convinced that the original version of the AA code did NOT allow dialing of these "non-user" extensions.

Further review shows it does appear to have been able to dial anything in the IMDB Aliases table, and so those need to get added to validusers.xml

This is mostly sipXconfig work to add the desired entries into validusers.xml, and AA will then allow them to be dialed (the numeric ones, at any rate, as that is all the user can enter with DTMF digits).

Any extra differentientation (i.e. can dial hunt groups, but not ACD queues) would require a different approach.

--Woof!
Show
Andy Spitzer added a comment - 2008-12-16 09:45 When I spec'ed the new AA, I was convinced that the original version of the AA code did NOT allow dialing of these "non-user" extensions. Further review shows it does appear to have been able to dial anything in the IMDB Aliases table, and so those need to get added to validusers.xml This is mostly sipXconfig work to add the desired entries into validusers.xml, and AA will then allow them to be dialed (the numeric ones, at any rate, as that is all the user can enter with DTMF digits). Any extra differentientation (i.e. can dial hunt groups, but not ACD queues) would require a different approach. --Woof!
Hide
Permalink
Andy Spitzer added a comment - 2008-12-17 12:34
Added entries in validusers.xml for the following aliases:
   Hunt Groups
   ACD Queues
   Conference Bridges
   external aliases

--Woof!
Show
Andy Spitzer added a comment - 2008-12-17 12:34 Added entries in validusers.xml for the following aliases:    Hunt Groups    ACD Queues    Conference Bridges    external aliases --Woof!
Hide
Permalink
Chaitra Sharma added a comment - 2008-12-18 05:41
This issue is resolved. Verified using the build:

sipxproxy 3.11.9-014294 2008-12-18T02:33:49 oem-centos5
sipxconfig 3.11.9-014294 2008-12-18T02:48:42 oem-centos5

Hence closing this issue.

Thanks,
Chaitra
Show
Chaitra Sharma added a comment - 2008-12-18 05:41 This issue is resolved. Verified using the build: sipxproxy 3.11.9-014294 2008-12-18T02:33:49 oem-centos5 sipxconfig 3.11.9-014294 2008-12-18T02:48:42 oem-centos5 Hence closing this issue. Thanks, Chaitra

People

  • Assignee:
    Unassigned
    Reporter:
    Chaitra Sharma
Vote (0)
Watch (0)

Dates

  • Created:
    2008-12-12 04:16
    Updated:
    2009-04-24 21:25
    Resolved:
    2008-12-17 12:34

Time Tracking

Estimated:
Not Specified
Original Estimate - Not Specified
Remaining:
Not Specified
Remaining Estimate - Not Specified
Logged:
2d
Time Spent - 2 days

Agile

  • View on Rapid Board
  • Atlassian JIRA (v5.0.6#733-sha1:f48fab7)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for OpenSCS/sipXecs. Try JIRA - bug tracking software for your team.