dial peer question

[susim]

Hello 

if incoming is a fax  i want to route the fax server , if it  is a call i want to route to faxserver 

How can i do that please help 

dial-peer voice 201 voip
 preference 9
 destination-pattern ..
 voice-class codec 1
 session target ipv4:CUCM IP ADDRESS
 incoming called-number .
 dtmf-relay h245-alphanumeric
 no vad

dial-peer voice 302 voip
 destination-pattern 3859
 session protocol sipv2
 session target ipv4:FAXSERVERIP:5062
 dtmf-relay rtp-nte
 codec g711ulaw
 fax protocol t38 ls-redundancy 0 hs-redundancy 0 fallback cisco
 no vad
!

Thanks 
 

[Chris Deren]

You have the right concept here, you can route the call to desired destination based on called number which is what "destination-pattern" does for you.  One thing you need to consider is also the incoming dial-peer (which in your example is dial peer 201 as it has incoming called-number .) so for faxing to work properly you should apply fax settings (fax protocol t38 ls-redundancy 0 hs-redundancy 0 fallback cisco) to this dial-peer as well unless you have it defined globally.

Chris

[susim]

Hi

Thanks .  'destination-pattern .. ' ,Does it mean any two digit number ? .

In my case  whether it is  call or fax dial peer 302 is matching ? Any ideas 

Thanks

[Chris Deren]

Yes, this means that routing is based only on 2 digits, which does not sound right (never seen 2 digits received from telco).  Since the other dial-peer uses 4 digits you should change the dial-peer 201 to "destination-pattern ...."

To find out for sure perform debug on the gateway to see what telco send you, if this is a PRI circuit use "debug isdn q931", if SIP "debug ccsip messages", if POTS "debug voice ccapi inout".

Chris

[susim]

Yes sending only two digits, What are the problems may arise telco sending only two digits ?.

 The destination-pattern was wrong, It must be  'destination-pattern 38'.

And it is an E1 line.

Thanks

[Chris Deren]

Please provide the debugs, as I have never seen telco sending you only 2 digits, plus your other dial-peer matches on 4. Unless these arrive on different trunks it would be impossible to receive different digit lengths.

Chris

[susim]

Thanks chris

Below is the output of  'debug isdn q931'

Sep  8 04:57:25.406: ISDN Se1/0:15 Q931: RX <- SETUP pd = 8  callref = 0x00EC 
        Sending Complete 
        Bearer Capability i = 0x8090A3 
                Standard = CCITT 
                Transfer Capability = Speech  
                Transfer Mode = Circuit 
                Transfer Rate = 64 kbit/s 
        Channel ID i = 0xA9839F 
                Exclusive, Channel 31 
        Calling Party Number i = 0x0081, '22253184' 
                Plan:Unknown, Type:Unknown 
        Called Party Number i = 0x81, '99' 
                Plan:ISDN, Type:Unknown
Sep  8 04:57:25.422: ISDN Se1/0:15 Q931: TX -> CALL_PROC pd = 8  callref = 0x80EC 
        Channel ID i = 0xA9839F 
                Exclusive, Channel 31
Sep  8 04:57:25.462: ISDN Se1/0:15 Q931: TX -> CONNECT pd = 8  callref = 0x80EC
Sep  8 04:57:25.522: ISDN Se1/0:15 Q931: RX <- CONNECT_ACK pd = 8  callref = 0x00EC
Sep  8 04:57:25.522: %ISDN-6-CONNECT: Interface Serial1/0:30 is now connected to 22253184 N/A
Sep  8 04:57:36.419: ISDN Se1/0:15 Q931: RX <- DISCONNECT pd = 8  callref = 0x00EC 
        Cause i = 0x8090 - Normal call clearing 
        Progress Ind i = 0x8288 - In-band info or appropriate now available 
Sep  8 04:57:36.419: %ISDN-6-DISCONNECT: Interface Serial1/0:30  disconnected from 22253184, call lasted 10 seconds
Sep  8 04:57:36.419: ISDN Se1/0:15 Q931: call_disc: PI received in disconnect; Postpone sending RELEASE for callid 0xA3
Sep  8 04:57:36.439: ISDN Se1/0:15 Q931: TX -> RELEASE pd = 8  callref = 0x80EC
Sep  8 04:57:36.487: ISDN Se1/0:15 Q931: RX <- RELEASE_COMP pd = 8  callref = 0x00EC

Thanks again

[Chris Deren]

You indeed are receiving only 2 digits per  Called Party Number i = 0x81, '99' , so please define the destination pattern using the 2 digits you want to use.

[susim]

Thanks chris

dial-peer voice 302 voip
 destination-pattern 99
 session protocol sipv2
 session target ipv4:FAXSERVERIP:5062
 dtmf-relay rtp-nte
 codec g711ulaw
 fax protocol t38 ls-redundancy 0 hs-redundancy 0 fallback cisco
 no va

After changing the destination pattern  two digit( destination-pattern 99) 

Any number which starts from '99XXXXXX' disconnects after 6 seconds , and the called party cannot hear anything , Meaning the the outgoing call matches the  dial-peer voice 302 voip and routing the call to the  faxserver ( this works also a pbx ) and fax server sends again to vg or cucm 

Any solution to this ?