Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

CME: where the magic hunt-group pilot number is from

Hi All,

I'm a newbie for VOIP and trying to understand how the IP phone implementation works on my company.

One of my questions is where the magic hunter group pilot number is from.

My company main phone number is 9798-2000. Anyone from outside ring the main number will reach to one broadcast hunt group first, but I reallly don't understand why the pilot number of this group is 7079 rather than 2000. I know there are 2 transferation-rules for incoming calls, I don't think they produce this magic number 7079. Also I notice the extension number 7050--7054 and 7080 are defined in ephone-dn except 7079.

Here is the relevant code from the configuration file:
===========
voice hunt-group 1 parallel
final 7080
list 7054,7050,7051,7052,7053
timeout 45
pilot 7079
  ......
Everyone's tags (3)
2 ACCEPTED SOLUTIONS

Accepted Solutions
Super Bronze

Re: CME: where the magic hunt-group pilot number is from

Can you post up the rest of the config?

Aaron Please remember to rate helpful posts to identify useful responses, and mark 'Answered' if appropriate!
Super Bronze

Re: CME: where the magic hunt-group pilot number is from

Hi

The call will go to wherever the dial-peers say 2000 is -  so the incoming call matches a POTS dial-peer, but the outgoing leg in this case (after being translated to 2000) matches the voip dial-peer 2000. Every call matches both an inbound and an outbound peer...

You can do a debug voip dialpeer to see it happening..

Regards

Aaron

Aaron Please remember to rate helpful posts to identify useful responses, and mark 'Answered' if appropriate!
9 REPLIES
Super Bronze

Re: CME: where the magic hunt-group pilot number is from

Hi

I don't see it either :-)

Maybe post up your whole config, or do a 'debug isdn q931' and dial your main number to verify that the service provider is signalling in the numbers you expect... you may be surprised and see it come in as a 7xxx number.

Aaron

Aaron Please remember to rate helpful posts to identify useful responses, and mark 'Answered' if appropriate!
New Member

Re: CME: where the magic hunt-group pilot number is from

Thank you for your reply!

I'll do the debug and let you know the result on Monday.

New Member

Re: CME: where the magic hunt-group pilot number is from

Here is dubug result, it comes with original main number rather than pilot number 7079!

.Aug 16 17:42:00.813 AEST: ISDN Se0/0/0:15 Q931: RX <- SETUP pd = 8  callref = 0x00ED
        Sending Complete
        Bearer Capability i = 0x9090A3
                Standard = CCITT
                Transfer Capability = 3.1kHz Audio
                Transfer Mode = Circuit
                Transfer Rate = 64 kbit/s
        Channel ID i = 0xA18381
                Preferred, Channel 1
        Progress Ind i = 0x8483 - Origination address is non-ISDN
        Calling Party Number i = 0x00A3, N/A
                Plan:Unknown, Type:Unknown
        Called Party Number i = 0xC1, '97982000'
                Plan:ISDN, Type:Subscriber(local)
.Aug 16 17:42:00.813 AEST: ISDN Se0/0/0:15 Q931: Received SETUP  callref = 0x80ED callID = 0x01FC switch = primary-net5 interface = User
.Aug 16 17:42:00.821 AEST: ISDN Se0/0/0:15 Q931: TX -> CALL_PROC pd = 8  callref = 0x80ED
        Channel ID i = 0xA98381
                Exclusive, Channel 1
.Aug 16 17:42:00.837 AEST: ISDN Se0/0/0:15 Q931: TX -> ALERTING pd = 8  callref = 0x80ED
.Aug 16 17:42:00.853 AEST: ISDN Se0/0/0:15 Q931: TX -> CONNECT pd = 8  callref = 0x80ED
.Aug 16 17:42:00.873 AEST: ISDN Se0/0/0:15 Q931: RX <- CONNECT_ACK pd = 8  callref = 0x00ED
.Aug 16 17:42:00.877 AEST: %ISDN-6-CONNECT: Interface Serial0/0/0:0 is now connected to N/A N/A
.Aug 16 17:42:15.353 AEST: ISDN Se0/0/0:15 Q931: RX <- DISCONNECT pd = 8  callref = 0x00ED
        Cause i = 0x8290 - Normal call clearing
        Progress Ind i = 0x8288 - In-band info or appropriate now available
.Aug 16 17:42:15.353 AEST: %ISDN-6-DISCONNECT: Interface Serial0/0/0:0  disconnected from unknown , call lasted 14 seconds
.Aug 16 17:42:15.353 AEST: ISDN Se0/0/0:15 Q931: call_disc: PI received in disconnect; Postpone sending RELEASE for callid 0x1FC
.Aug 16 17:42:15.389 AEST: ISDN Se0/0/0:15 Q931: TX -> RELEASE pd = 8  callref = 0x80ED
.Aug 16 17:42:15.417 AEST: ISDN Se0/0/0:15 Q931: RX <- RELEASE_COMP pd = 8  callref = 0x00ED

New Member

Re: CME: where the magic hunt-group pilot number is from

do you have a global translation rule for 2000 -> 7079, check it up in the call manager.

Super Bronze

Re: CME: where the magic hunt-group pilot number is from

Can you post up the rest of the config?

Aaron Please remember to rate helpful posts to identify useful responses, and mark 'Answered' if appropriate!
New Member

Re: CME: where the magic hunt-group pilot number is from

Sorry! I hit wrong button. It still has not been solved. Please check my configure file.

Note: I changed user name and some sensitive infomation.

========================

!
voice hunt-group 1 parallel
final 7080
list 7054,7050,7051,7052,7053
timeout 45
pilot 7079
!
dial-peer voice 1 pots
description **Inbound from PSTN**
incoming called-number .
direct-inward-dial
!
dial-peer voice 102 pots
corlist outgoing Local
description **Outbound PSTN to Local**
destination-pattern 0[2-9].......
port 0/0/0:15
forward-digits 8
!

dial-peer voice 2000 voip
description *** Main CUE AA Access Number ***
destination-pattern 2000
session protocol sipv2
session target ipv4:10.9.88.10
dtmf-relay sip-notify
codec g711ulaw
no vad
!
dial-peer voice 7000 voip
description *** Main CUE Voicemail Access Number ***
destination-pattern 7000
session protocol sipv2
session target ipv4:10.9.88.10
dtmf-relay sip-notify
codec g711ulaw
no vad
!

Super Bronze

Re: CME: where the magic hunt-group pilot number is from

Hi


Your main number comes in and is translated to 2000.

2000 is then sent to Unity:

dial-peer voice 2000 voip
description *** Main CUE AA Access Number ***
destination-pattern 2000
session protocol sipv2
session target ipv4:10.9.88.10
dtmf-relay sip-notify
codec g711ulaw
no vad
!

The CUE module will then run a script and may do one of several things - it might play prompts, check opening hours etc, and then will be sending the call back out to the 7079 hunt pilot.

Regards

Aaron

Please rate helpful posts...

Aaron Please remember to rate helpful posts to identify useful responses, and mark 'Answered' if appropriate!
New Member

Re: CME: where the magic hunt-group pilot number is from

Hi Aaron,

Thanks a lot!

You might be right, let me check the script tomorrow.

I always think the "dial-peer voice 2000 voip" is for calling from IP. Incoming call from PSTN is not going through the Dial-peer.

Super Bronze

Re: CME: where the magic hunt-group pilot number is from

Hi

The call will go to wherever the dial-peers say 2000 is -  so the incoming call matches a POTS dial-peer, but the outgoing leg in this case (after being translated to 2000) matches the voip dial-peer 2000. Every call matches both an inbound and an outbound peer...

You can do a debug voip dialpeer to see it happening..

Regards

Aaron

Aaron Please remember to rate helpful posts to identify useful responses, and mark 'Answered' if appropriate!
3042
Views
4
Helpful
9
Replies
CreatePlease login to create content