Koozali.org: home of the SME Server

Obsolete Releases => SME VoIP (Asterisk, SAIL etc) => Topic started by: SARK devs on August 16, 2009, 03:53:32 PM

Title: sail-2.2.4-9 and sail-2.3.2-11
Post by: SARK devs on August 16, 2009, 03:53:32 PM

Hi

Two new releases for you.  Functionally the same. 2.2.x is Zap and 2.3.x is DAHDI.

Quote

* Sun Aug 16 2009 Aelintra <coco@aelintra.com> -r917/918/919/920/921/922/923/924
- install NANP service code converter
- fix Ramdisk mount error
- update nav code for SARK/VeeGate

Patience rewarded Sophie, we have implemented NANPA vertical service activation codes you requested.  We had hoped we could use the same codes as FPBX but unfortunately, the FPBX implementation of the NANPA codes is just plain wrong and incomplete, which makes our life that much more difficult... So.. we've only implemented the FPBX service codes which are compatible with NANPA.

Quote

*78 — Do Not Disturb activate   
*79 — Do Not Disturb deactivate 

*72 — Call Forward activate
*73 — Call Forward deactivate

*90 — Call Forward on Busy activate
*91 — Call Forward on Busy deactivate

*97 — Check voicemail (for calling extension) 
*98 — Check voicemail (enter extension) 

For completeness... Here are the fpbx supported codes and their validity...

Quote

*78 — Do Not Disturb activate (NANPA compatible)
*79 — Do Not Disturb deactivate (NANPA compatible)
*98 — Check voicemail (enter extension) (NANPA compatible)
*98nnn — Check voicemail (extension nnn) (NANPA compatible)
*97 — Check voicemail (for calling extension) (NANPA compatible)
*70 — Call Waiting activate (Incorrect - in NANPA *70 cancels)
*71 — Call Waiting deactivate  (conflicts with NANPA)
*72 — Call Forward activate (NANPA compatible)
*73 — Call Forward deactivate (NANPA compatible)
*90 — Call Forward on Busy activate (NANPA compatible)
*91 — Call Forward on Busy deactivate (NANPA compatible)
*69 — Call trace (conflicts with NANPA)
*11 — Log in (not used for fixed devices)  (Not a NANP code and no conflict)
*12 — Log out (not used for fixed devices) (Not a NANP code and no conflict)
*77 — Record announcement  (conflicts with NANPA)
*99 — Playback announcement   (NANPA compatible)
*43 — Echo test   (conflicts with NANPA)
*60 — Time   (conflicts with NANPA)
*61 — Weather   (conflicts with NANPA)
*62 — Wakeup call  (conflicts with NANPA)
*65 — Playback extension  (conflicts with NANPA)

The full NANPA codes can be found at

http://www.nanpa.com/number_resource_info/vsc_assignments.html

Kind Regards

S

Title: Re: sail-2.2.4-9 and sail-2.3.2-11
Post by: soprom on August 16, 2009, 04:26:04 PM

Many thanks!

I'll update my PBXs and see how it goes!

Title: Re: sail-2.2.4-9 and sail-2.3.2-11
Post by: soprom on August 16, 2009, 09:14:08 PM

It looks good! Now users can use the same feature codes for a dahdi channel and for selintra...

I would have a comment (keep in mind I'm not a coder):

It could be interesting to have extension.conf using an include after the new lines:

Code: [Select]

;
; NANP Vertical Service Code Compatibility
;
...
exten => *98,1,agi(selintra,*51*)
exten => _*99XXXX,1,agi(selintra,*61*${EXTEN:3})

#include sark_customer_nanpfeatures.conf
Many thanks again for your cooperation with these features.  They will be appreciated!

Title: Re: sail-2.2.4-9 and sail-2.3.2-11
Post by: SARK devs on August 16, 2009, 09:58:45 PM

Hi Sophie,

I understand what you mean with the request for another include but it isn't necessary.  You can add your own NANPA (or any other) feature codes simply by creating a custom app. You could, for example, create an app called My_NANPA_Codes  and then simply write code like this...

Code: [Select]

;
; my *66
;

exten=>*66,1,dosomething
In fact, this is exactly how we prototyped the NANPA codes before we commited them to templates.

Kind Regards

S