sipXecs

Dial plan with Schedule does not work for voice mail dial rule

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 4.1.6
  • Fix Version/s: 4.1.7, 4.2
  • Component/s: DialPlan
  • Team:
    Management
  • Rank:
    1485   
  • Labels:
  • Description:
    Hide
    Type: Regression
    The dial plan with schedule was working fine when we did a full round of test against SCS 3.0

    Pre conditions :
    ----------------
    1.Login to the config UI as superadmin . Register one polycom phone with UID 300 ( all permissions are enabled for the user 300)
    2.Navigate to Devices--->Gateways and add an unmanaged gateway as follows :
      Enabled : checked
      Name : Gateway1
      Address :176.25.2.184
      Location :All
      Shared :Check
    Click on Apply and OK buttons.
    3.Restarted the services as per service restart prompt.
    4.Navigate to System--->Dial plans --->Schedules and add a schedule as follows :
      Name : Qantom
     Add a period as : Day :Every day ; From: 11:00AM To : 8:00 PM
     Click on Apply and OK buttons.
    5.Click on Dialing Rules and enable International dial plan as follows :
      Enabled :Checked
      Permission :International dialing
      PSTN prefix :<blank>
     Long distance prefix : 011
     Area Codes :<blank>
     External Number length : 5 digits
    Schedule :Qantom
    From more action drop down menu, select the unmanaged gateway "Gateway1"
    Click on Apply and OK buttons.
    6.Restart the services as per service restart prompt.
    7.Verify fallbackrules.xml under etc/sipxpbx directory and ensure that the generated 'sipx-ValidTime' is correct as per schedule.

    Steps to reproduce :
    ---------------------
    From the Polycom phone with user 300, dial an international number within the specified schedule time ( ie; in between 11:00AM and 8:00 PM)

    Expected result :
    Gateway1 should start ringing and call should be established between Gateway1 and 300 upon answering the call on Gateway1

    Actual Result :
    After dialing international number, Gateway1 doesn't get ringing and it sends "416 Unsupported URI Scheme" error message to the sipXproxy ( evident from call ID )

    Call ID :
    ---------
    Made an international call at the local time 5.57PM approx : (ie; Tue Mar 2 12:27:54 UTC 2010 ) : b1025611-bb4433c2-f36a0df3@176.25.2.167

    Attachments :
    a) snapshot : dialplan_with_schedule_not_working.tar.gz
    b)merged log :international_merged.xml

    Observations :
    1. This issue is also observed for emergency, local,long distance, toll free dial plans with schedule added.
        a) Emergency dial plan call ID : cadec6e3-ac631594-ad27e0c5@176.25.2.167
        b) Local dial plan call ID : 8831d503-7041b3b4-19a0ee5@176.25.2.167
        c) Long distance dial plan call ID : acf4431-740cb1e2-8d361c13@176.25.2.167
        d) Toll free dial plan call ID : bf09055f-7fa50210-33507b41@176.25.2.167

    2. This issue is NOT observed when there is no schedule selected for dial plans.

    3. Only voice mail dial plan is working for above mentioned schedule 'Qantom'.
       Call ID (successful case) : dd0d188d-da38a43e-ca172c6f@176.25.2.167
    Show
    Type: Regression The dial plan with schedule was working fine when we did a full round of test against SCS 3.0 Pre conditions : ---------------- 1.Login to the config UI as superadmin . Register one polycom phone with UID 300 ( all permissions are enabled for the user 300) 2.Navigate to Devices--->Gateways and add an unmanaged gateway as follows :   Enabled : checked   Name : Gateway1   Address :176.25.2.184   Location :All   Shared :Check Click on Apply and OK buttons. 3.Restarted the services as per service restart prompt. 4.Navigate to System--->Dial plans --->Schedules and add a schedule as follows :   Name : Qantom  Add a period as : Day :Every day ; From: 11:00AM To : 8:00 PM  Click on Apply and OK buttons. 5.Click on Dialing Rules and enable International dial plan as follows :   Enabled :Checked   Permission :International dialing   PSTN prefix :<blank>  Long distance prefix : 011  Area Codes :<blank>  External Number length : 5 digits Schedule :Qantom From more action drop down menu, select the unmanaged gateway "Gateway1" Click on Apply and OK buttons. 6.Restart the services as per service restart prompt. 7.Verify fallbackrules.xml under etc/sipxpbx directory and ensure that the generated 'sipx-ValidTime' is correct as per schedule. Steps to reproduce : --------------------- From the Polycom phone with user 300, dial an international number within the specified schedule time ( ie; in between 11:00AM and 8:00 PM) Expected result : Gateway1 should start ringing and call should be established between Gateway1 and 300 upon answering the call on Gateway1 Actual Result : After dialing international number, Gateway1 doesn't get ringing and it sends "416 Unsupported URI Scheme" error message to the sipXproxy ( evident from call ID ) Call ID : --------- Made an international call at the local time 5.57PM approx : (ie; Tue Mar 2 12:27:54 UTC 2010 ) : b1025611-bb4433c2-f36a0df3@176.25.2.167 Attachments : a) snapshot : dialplan_with_schedule_not_working.tar.gz b)merged log :international_merged.xml Observations : 1. This issue is also observed for emergency, local,long distance, toll free dial plans with schedule added.     a) Emergency dial plan call ID : cadec6e3-ac631594-ad27e0c5@176.25.2.167     b) Local dial plan call ID : 8831d503-7041b3b4-19a0ee5@176.25.2.167     c) Long distance dial plan call ID : acf4431-740cb1e2-8d361c13@176.25.2.167     d) Toll free dial plan call ID : bf09055f-7fa50210-33507b41@176.25.2.167 2. This issue is NOT observed when there is no schedule selected for dial plans. 3. Only voice mail dial plan is working for above mentioned schedule 'Qantom'.    Call ID (successful case) : dd0d188d-da38a43e-ca172c6f@176.25.2.167
  • Environment:
    sipxconfig 4.1.6-018157 2010-03-02T00:55:58 oem-centos5
    sipxproxy 4.1.6-018157 2010-03-02T01:11:28 oem-centos5

Attachments

  1. Text File
    0001-XX-7793-Dial-plan-with-Schedule-does-not-work-for-vo.patch
    (2 kB)
    xingjun chu
    2010-03-22 10:07
  2. Text File
    0001-XX-7793-Scheduled-Dial-plan-not-working.patch
    (6 kB)
    xingjun chu
    2010-03-12 11:27
  3. Text File
    0002-XX_7793-Dial-plan-with-Schedule-does-not-work-except.patch
    (2 kB)
    xingjun chu
    2010-03-12 11:24
  4. GZip Archive
    dialplan_with_schedule_not_working.tar.gz
    (905 kB)
    Venugopal MS
    2010-03-02 07:40
  5. XML File
    international_merged.xml
    (21 kB)
    Venugopal MS
    2010-03-02 07:40
  6. XML File
    VM_dialing_rule_failed.xml
    (32 kB)
    Venugopal MS
    2010-03-19 02:06
  7. GZip Archive
    VM_dialing_rule_not_working_for_schedule.tar.gz
    (1.22 MB)
    Venugopal MS
    2010-03-19 02:06

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
xingjun chu added a comment - 2010-03-05 13:31 - edited
Discussed with Dale, the format is wrong in fallbackrules.xml for sipx-ValidTime, there should be no double quote around the value.
Show
xingjun chu added a comment - 2010-03-05 13:31 - edited Discussed with Dale, the format is wrong in fallbackrules.xml for sipx-ValidTime, there should be no double quote around the value.
Hide
Permalink
Paul Mossman added a comment - 2010-03-11 13:12
Hi Jason, can you fix the ant precommit tests?

Also in InternalRuleTest.testAppendToGenerationRulesWithSchedule() I notice you drop the last 10 chars from the tvf.getUrl() value before checking it. This might be more robust:
    assertTrue(tvf.getUrl().startsWith("<sip:IVR@192.168.1.1:0;mailbox={vdigits};action=deposit>;q=0.1;sipx-ValidTime="));
Show
Paul Mossman added a comment - 2010-03-11 13:12 Hi Jason, can you fix the ant precommit tests? Also in InternalRuleTest.testAppendToGenerationRulesWithSchedule() I notice you drop the last 10 chars from the tvf.getUrl() value before checking it. This might be more robust:     assertTrue(tvf.getUrl().startsWith("<sip:IVR@192.168.1.1:0;mailbox={vdigits};action=deposit>;q=0.1;sipx-ValidTime="));
Hide
Permalink
xingjun chu added a comment - 2010-03-12 11:24
thanks Paul for your comments
Show
xingjun chu added a comment - 2010-03-12 11:24 thanks Paul for your comments
Hide
Permalink
Venugopal MS added a comment - 2010-03-19 02:05
Verified this issue in the following build :

sipxconfig 4.1.7-018351 2010-03-19T00:34:38 oem-centos5
sipxproxy 4.1.7-018351 2010-03-19T00:52:23 oem-centos5

Now dial plan with schedule is working fine for all dialing rules BUT its not working for voice mail dial rule.

Steps followed :
1.Login to the config UI as superadmin . Register one polycom phone with UID 500
2.Navigate to System--->Dial plans --->Schedules and add a schedule as follows :
  Name : Qantom
 Add a period as : Day :Every day ; From: 11:00AM To : 8:00 PM
 Click on Apply and OK buttons.
3.Click on Dialing Rules and add a new voice mail dialing rule as follows :
    Enabled :Checked
    Name : New_VM
    Voicemail extension :501
    Schedule : Qantom
 (Rest of the fields are set to default)
Click on Apply and OK buttons.
4.Restart the services as per service restart prompt.

Now, dialed new voicemail extension 501 from the user 500 within specified schedule time

Expected : The VM prompt "Welcome.. your call has been..." should be played on the phone 500

Actual : VM prompt is not heard on the phone 500. It is observed from the call ID that, registrar sends "404 Not found" error message to the sipXproxy and sipXproxy sends this to the phone.

Call ID : f6cdf629-108537e0-bb74f07f@176.25.2.167

NOTES :
1.If the schedule for the added VM dialing rule is set to "Always" , then VM prompt is played as expected after dialing VM extension 501
2. For the same schedule 'Qantom', all other dialing rules are working fine.
Call IDs :
a) International :8eef276b-a8a197d2-ec2a8ba1@176.25.2.167
b) Emergency : 62edda59-bc118c90-3c4461af@176.25.2.167
c) Local :6d62f01d-52929db4-613bd733@176.25.2.167
d) Long distance : 3e91b66f-cd59d036-1f76a665@176.25.2.167
e) Toll free : 254d6ad-614dc5c4-4e9ec4c3@176.25.2.167

Attachements :
a) Snapshot :VM_dialing_rule_not_working_for_schedule.tar.gz
b) VM failed merged log : VM_dialing_rule_failed.xml


So, it is observed that, previously, VM dialing rule was working fine but other dialing rules failed to work with schedules. Now, all other dialing rules are working fine but VM dialing rule failed to work with schedule.

Hence reopening this issue by changing the summary from "Dial plan with Schedule does not work except for voice mail dial rule" to new summary as "Dial plan with Schedule does not work for voice mail dial rule"

Thanks,
 Venu
Show
Venugopal MS added a comment - 2010-03-19 02:05 Verified this issue in the following build : sipxconfig 4.1.7-018351 2010-03-19T00:34:38 oem-centos5 sipxproxy 4.1.7-018351 2010-03-19T00:52:23 oem-centos5 Now dial plan with schedule is working fine for all dialing rules BUT its not working for voice mail dial rule. Steps followed : 1.Login to the config UI as superadmin . Register one polycom phone with UID 500 2.Navigate to System--->Dial plans --->Schedules and add a schedule as follows :   Name : Qantom  Add a period as : Day :Every day ; From: 11:00AM To : 8:00 PM  Click on Apply and OK buttons. 3.Click on Dialing Rules and add a new voice mail dialing rule as follows :     Enabled :Checked     Name : New_VM     Voicemail extension :501     Schedule : Qantom  (Rest of the fields are set to default) Click on Apply and OK buttons. 4.Restart the services as per service restart prompt. Now, dialed new voicemail extension 501 from the user 500 within specified schedule time Expected : The VM prompt "Welcome.. your call has been..." should be played on the phone 500 Actual : VM prompt is not heard on the phone 500. It is observed from the call ID that, registrar sends "404 Not found" error message to the sipXproxy and sipXproxy sends this to the phone. Call ID : f6cdf629-108537e0-bb74f07f@176.25.2.167 NOTES : 1.If the schedule for the added VM dialing rule is set to "Always" , then VM prompt is played as expected after dialing VM extension 501 2. For the same schedule 'Qantom', all other dialing rules are working fine. Call IDs : a) International :8eef276b-a8a197d2-ec2a8ba1@176.25.2.167 b) Emergency : 62edda59-bc118c90-3c4461af@176.25.2.167 c) Local :6d62f01d-52929db4-613bd733@176.25.2.167 d) Long distance : 3e91b66f-cd59d036-1f76a665@176.25.2.167 e) Toll free : 254d6ad-614dc5c4-4e9ec4c3@176.25.2.167 Attachements : a) Snapshot :VM_dialing_rule_not_working_for_schedule.tar.gz b) VM failed merged log : VM_dialing_rule_failed.xml So, it is observed that, previously, VM dialing rule was working fine but other dialing rules failed to work with schedules. Now, all other dialing rules are working fine but VM dialing rule failed to work with schedule. Hence reopening this issue by changing the summary from "Dial plan with Schedule does not work except for voice mail dial rule" to new summary as "Dial plan with Schedule does not work for voice mail dial rule" Thanks,  Venu
Hide
Permalink
xingjun chu added a comment - 2010-03-22 10:07
Submit for review
Show
xingjun chu added a comment - 2010-03-22 10:07 Submit for review
Hide
Permalink
Paul Mossman added a comment - 2010-03-23 12:14
Hi Huijun, can you review the updated patch and commit if OK? Thanks.
Show
Paul Mossman added a comment - 2010-03-23 12:14 Hi Huijun, can you review the updated patch and commit if OK? Thanks.
Hide
Permalink
Huijun Yang added a comment - 2010-03-23 12:20
closed by mistake.
Show
Huijun Yang added a comment - 2010-03-23 12:20 closed by mistake.
Hide
Permalink
Venugopal MS added a comment - 2010-03-24 23:19
This issue is fixed. Verified this issue in the following build :

sipxconfig 4.1.7-018406 2010-03-24T00:14:23 oem-centos5
sipxproxy 4.1.7-018406 2010-03-24T00:32:08 oem-centos5

Now dial plan with schedule is working fine for VM dialing rule.

Hence closing this issue.

Thanks,
 Venu
Show
Venugopal MS added a comment - 2010-03-24 23:19 This issue is fixed. Verified this issue in the following build : sipxconfig 4.1.7-018406 2010-03-24T00:14:23 oem-centos5 sipxproxy 4.1.7-018406 2010-03-24T00:32:08 oem-centos5 Now dial plan with schedule is working fine for VM dialing rule. Hence closing this issue. Thanks,  Venu

People

  • Assignee:
    Unassigned
    Reporter:
    Venugopal MS
  • Votes:
    0
    Watchers:
    1

Dates

  • Created:
    2010-03-02 07:39
    Updated:
    2010-04-15 17:17
    Resolved:
    2010-03-23 13:04
Atlassian JIRA (v4.1.1#522) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for SIPfoundry/sipXecs. Try JIRA - bug tracking software for your team.