Doubt about dial-peers

[Thiago Cella]

I have a doubt about follow dial-peers, are there any mistakes?? i ask because somethimes the transfers to extensions dosent work, the calls down:

dial-peer voice 3 pots
description Local
destination-pattern 0[2-6].......
port 0/0/0:1
!
dial-peer voice 4 pots
description DDD
destination-pattern 00T
port 0/0/0:1
prefix 0
!
dial-peer voice 5 pots
description DDI
destination-pattern 000T
port 0/0/0:1
prefix 00
!
dial-peer voice 6 pots
description Celular
destination-pattern 0[7-9].......
port 0/0/0:1
!
dial-peer voice 7 pots
description Services
destination-pattern 01..
port 0/0/0:1
prefix 1
!
dial-peer voice 8 pots
description Free calls
destination-pattern 00800T
port 0/0/0:1
prefix 0800
!
dial-peer voice 1001 voip
description Extensions

destination-pattern 1..
session target ipv4:192.168.0.10
codec g711ulaw
!
dial-peer voice 2 pots
description Incomming calls
destination-pattern 1..
direct-inward-dial
port 0/0/0:1
!

[Felipe Garrido]

Hi Thiago,

We'll need additional information on the problem in order to comment on the configuration.

What is the call flow?

What are the calling, called, transfer party numbers?

What do the parties involved in the call experience?

What type of call agent handles the transfer?

-Felipe

[Thiago Cella]

Hi Felipe, tks !

The follow scenario works , with no problem :

calls comming from outside goes direct to recepcionist extension, and the recepcionist transfer to any extension, at this point everthing works fine,

OUTSIDE  ------>  CCME (192.168.0.10) ------>  recepcionist extension (400 - ip 192.168.0.X) ----->  another  extension (115 - ip 192.168.0.x)

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

This scenario that problem happens:

when the calls are transfered to a first extension on another site ,works no problem too, but when this first extension transfer to someboy the call down:

OUTSIDE  ------>  CCME (192.168.0.10) ------>  recepcionist extension (400 - ip 192.168.0.X) -----> Call cross  Ponit-To-Point-Cloud--------> Router local another site (ip  192.168.200.x)  --------> another  extension (116 - ip 192.168.200.x) --------------(at this ponit the call down)-------------------> another extension (117 - ip 192.168.200.x)

Obs: The router in the another site isnt Cisco, just a router.

[Felipe Garrido]

Thiago,

Thanks for the additional info. I have some additional questions.

- Are extensions 400, 116 and 117 all registered to CCME?

- Is it extension 116 that tries to transfer to 117 or is it 400 that transfers to 117?

- What do the parties experience when the transfer fails (fast busy, dead air)?

- Are they performing a blind or consult transfer?

-Felipe

[Thiago Cella]

Hi Felipe tks again!

- Are extensions 400, 116 and 117 all registered to CCME?

All are registred to CCME

- Is it extension 116 that tries to transfer to 117 or is it 400 that transfers to 117?

When the 116 recive the call, and after it try transfer to 117 the call down.

- What do the parties experience when the transfer fails (fast busy, dead air)?

Fast busy

- Are they performing a blind or consult transfer?

I believe is consult transfer :

telephony-service
no auto-reg-ephone
em logout 0:0 0:0 0:0
max-ephones 20
max-dn 288
ip source-address 192.168.0.10 port 2000
system message XXXXXXXXX
load 7914 S00104000000
load 7910 P00403020214
load 7960-7940 P00307020200
load 7941 term41.default
load 7961 term61.default
time-zone 17
time-format 24
date-format dd-mm-yy
dialplan-pattern 1 5904.... extension-length 4 extension-pattern ....
max-conferences 8 gain -6
call-forward pattern .T
web admin system name XXXX password XXXX
dn-webedit
time-webedit
transfer-system full-consult
transfer-pattern .T