Internal Causes of Call release in Siemens IN 7b

1 = unallocated (unassigned) number 2 = no route to specified transit network 3 = no route to destination 4 = send special information tone 5 = misdialled trunk prefix 6 = TCAP-Cause: missing customer record 16 = normal call clearing 17 = user busy 18 = no user responding 19 = no answer from user (user alerted) 21 = call rejected 22 = number changed 27 = destination out of order 28 = address incomplete 29 = facility rejected 31 = normal – unspecified 34 = no circuit available 38 = network out of order 41 = temporary failure 42 = switching equipment congestion 44 = requested channel not available 47 = resource unavailable – unspecified 50 = requested facility not subscribed

55 = incoming calls barred within CUG 57 = bearer capability not authorized 58 = bearer capability not presently available 63 = service/option not available – unspecified 65 = bearer capability not implemented 69 = requested facility not implemented 70 = only restricted information bearer capability is available 79 = service or option not implemented – unspecified 87 = called user not member of CUG 88 = incompatible destination 91 = invalid transit network selection 95 = invalid message, unspecified 97 = message type non-existent or not implemented 99 = par. non-existent or not implemented – discarded 103 = par. non-existent or not implemented – passed on 111 = protocol error, unspecified 127 = interworking, unspecified

Swap VoMS Application or Database Cluster

If we want to switch Siemens VoMSXpress application from one machine to another it's use scswitch command. Be informed this configuration uses Sun Cluster technology, in other technology such as Veritas it should be different.

1- chris application should be stopped and when starting the framework should run as last application
(/opt/xpress/SxFramework/scripts/Sx.sh SxFrameWork stop|start)

2- check sun cluster status
scstat
The status of cluster, like which app or db on which cluster, online or offline

Node name Status
--------- ------
Cluster node: voms1 Online
Cluster node: voms2 Online

3- Stop appropriate resource group
scswitch -F -g [rg_sxfwapp|rg_sxfwdb] (-F make offline)

4- Change primary node
scswitch -z -D [appvol|dbvol] -h [voms2|voms1] (-z change primary node)

5- Make resource online
scswitch -Z -g [rg_sxfwapp|rg_sxfwdb] (-Z make resources online)

6- Start chris application as mentioned above

Start & Stop IN Application

In Siemens IN classic 7b, we can stop and start only SCP application with the following commands, without any need to restart SCP machine:
stop: mkup -dtK
start: mkup -rstK

*These command have to be run in instscp user context.
** The first application which comes up will become the master counter manager.

Other useful command in this subject:
Check Up & Down of process on local and remote hosts
mkup -iploc
mkup -iprem

Check master and slave Counter Manager
cmctx_ls -l

Adding New Voucher Printer

To add new voucher printer to VoMSXpress of Siemens, first add voucher in configuration (vomscore->V03->VoucherProviderList->VoucherProvider1->Values->VoucherPrinterList) and then create a directory in voms at /app/voucher/RIC_Iran/VOP/prod_out/ with the same name of the voucher printer in GUI and set owner and mod of the directory to appropriate setting(voms:sx,775).

Finally stop start vomsservice and vomsordermgr in task manager.