Application service problem

Unanswered Question


For night service we have created a loopback voip dial-peer to with an application service that prompts a message during after hours.

During working hours the same DP will prompt a waiting message.

So the DP is called by setting up a "call-forward noan 5500 timeout 20" where 5500 is the number associated to the loopback voip DP.

Here is the DP configuration:


dial-peer voice 500 voip

service script1

destination-pattern 5500$

session target ipv4: <-- this is the router ip address (IF Gi0/0)

incoming called-number 5500$

dtmf-relay h245-alphanumeric

codec g711ulaw

no vad


The voice service voip is configured as follows:


voice service voip

allow-connections h323 to h323

allow-connections h323 to sip

allow-connections sip to h323

allow-connections sip to sip

supplementary-service h450.12


h450 h450-2 timeout T4 10000

h450 h450-3 timeout T1 10000

h245 caps mode restricted

modem passthrough nse codec g711alaw



When the call starts from internal ephone or from outside mobile phones, the prompt is regularly played.

But when the call comes from an outside fixed phone, the call is disconnected just after the timeout for call-forward is expired.

We have also tried to configure a number expansion to call directly the DP 500 adding the following command to the configuration:

num-exp 2xxxxxx98 5500

but obviously the behavior does not change.

With "debug q931" we see that the call is disconnected with Disconnect Cause 10 (normal call clearing):

Apr 27 18:45:09.361: ISDN Se0/0/0:15 Q931: RX <- SETUP pd = 8 callref = 0x2500

Bearer Capability i = 0x8090A3

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA18387

Preferred, Channel 7

Progress Ind i = 0x8083 - Origination address is non-ISDN

Calling Party Number i = 0x2183, '2xxxxxxx'

Plan:ISDN, Type:National

Called Party Number i = 0xA1, '2xxxxxx98'

Plan:ISDN, Type:National

Apr 27 18:45:09.365: ISDN Se0/0/0:15 Q931: TX -> SETUP_ACK pd = 8 callref = 0xA500

Channel ID i = 0xA98387

Exclusive, Channel 7

Apr 27 18:45:09.393: ISDN Se0/0/0:15 Q931: TX -> DISCONNECT pd = 8 callref = 0xA500

Cause i = 0x8090 - Normal call clearing

Apr 27 18:45:09.461: ISDN Se0/0/0:15 Q931: RX <- RELEASE pd = 8 callref = 0x2500

Apr 27 18:45:09.461: ISDN Se0/0/0:15 Q931: TX -> RELEASE_COMP pd = 8 callref = 0xA500

Any ideas?

Thanks a lot.


  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
thisisshanky Mon, 04/30/2007 - 10:57
User Badges:
  • Purple, 4500 points or more

Is this a TCL script ? Custom developed or BACD ?

Does the script look at a particular DNIS on the call ? Instead of using 5500 on the dial-peer i have seen with BACD that you have to use the actual DNIS *2XXXXXX98" on the incoming called number statement.

Hi and thanks for your reply.

Yes,it's a TCL script and it's a customization of one script that comes with Stone Voice suite.

The script accept the call

leg setupack leg_incoming

leg proceeding leg_incoming

leg connect leg_incoming

and then recall media play to play the prompt, repeat the prompt another time and after the second play it closes the call with "leg disconnect leg_incoming".

In the test we have done we have enabled the "debug voip app tclcommnads". When a call comes from a mobile phone the script was called and proceed succesfully.

But when the call comes from a fixed phone number, the debug print messages up to the "leg setupack" statement. The call is disconnected with a "clear disconnect cause".

Attached, you can find the debug related to the two tests, from a mobile phone and from a fixed one.

The answer to your second question:

It does not referer at a particular DNIS on the calls.

We already tried to set up the "incoming-called number" and the "destination-pattern" with the complete E.164 number under the loopback voip DP (i.e. 2XXXXXX98) , instead of num-exp parameter at global level.

But we got the same results.

Thanks a lot.



This Discussion