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

Answering Incoming Calls on FXO ports

2821 H.323 Gateway with VIC2-2FXO card, PVDM2-32.

I can do outbound calls just fine, but inbound calls are not working. It looks like the FXO port answers the calls, but then it is dropped.

From debugging the dial-peers, I see the call come in but it looks like the calling number is getting stripped. What am I missing in my config?

voice-port 0/1/0

trunk-group POTS 1

timing hookflash-out 500

!

voice-port 0/1/1

trunk-group POTS 2

timing hookflash-out 500

!

!

dial-peer voice 1 pots

trunkgroup POTS

incoming called-number .

direct-inward-dial

!

dial-peer voice 100 pots

trunkgroup POTS

destination-pattern ^1[2-9]..[2-9]......$

!

dial-peer voice 400 voip

destination-pattern ^425555....$

codec g711ulaw

session target ipv4:1.2.3.4

dtmf-relay h245-alphanumeric

no vad

!

#debug voip dialpeer all

Apr 19 21:02:17.904: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:

Calling Number=, Called Number=, Voice-Interface=0x4621F068,

Timeout=TRUE, Peer Encap Type=ENCAP_VOICE, Peer Search Type=PEER_TYPE_VOICE,

Peer Info Type=DIALPEER_INFO_SPEECH

Apr 19 21:02:17.904: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:

Match Rule=DP_MATCH_PORT;

Apr 19 21:02:17.904: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:

Result=NO_MATCH(-1) After All Match Rules Attempt

Apr 19 21:02:17.904: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerSPI:exit@593

1 ACCEPTED SOLUTION

Accepted Solutions
Hall of Fame Super Gold

Re: Answering Incoming Calls on FXO ports

Hi Jonny,

when you have FXO without caller-id active, both calling and caller number are empty as you can see. Since you have no DID, called number is also empty and won't match any "incoming calling-number". So you can either give dialtone to calls, or direct all call to a number of your choice using "connection plar".

hope this helps, please rate post if it does!

7 REPLIES
Hall of Fame Super Gold

Re: Answering Incoming Calls on FXO ports

Hi Jonny,

when you have FXO without caller-id active, both calling and caller number are empty as you can see. Since you have no DID, called number is also empty and won't match any "incoming calling-number". So you can either give dialtone to calls, or direct all call to a number of your choice using "connection plar".

hope this helps, please rate post if it does!

Bronze

Re: Answering Incoming Calls on FXO ports

Interesting...so if the POTS line does not have caller ID service, then then called number field will always be empty and I must use PLAR to receive the call?

Hall of Fame Super Gold

Re: Answering Incoming Calls on FXO ports

Hmm.. more exactly, if no caller-id, no calling number, but in any case, never called number.

So you can to override caller-id with "station number", that will give you at least calling number (always the same), that in turn you can use for sophisticated incoming DP setting using "answer-address".

Confused enough ? :)

Bronze

Re: Answering Incoming Calls on FXO ports

Yes, I had played with "station-id number" and saw that actually modified the Calling number, which was weird. I'm just trying to set the Called Number.

Do you have an example of using "answer-address"? That's a new one to me.

Hall of Fame Super Gold

Re: Answering Incoming Calls on FXO ports

Sure. With working caller-id, send calls from certain area codes to hunt-group 100:

voice-port 0/0

cptone US

caller-id enable

dial-peer voice 100 pots

answer-address 805........

translation-profile incoming to100

voice translation-profile to100

translate called 100

voice translation-rule 100

rule 1 // /100/

ephone-hunt 1 sequential

pilot 100

list ...

Attach an application to certain FXS ports:

voice-port x/y

station number 80

dial-peer voice 50 pots

application myapp

answer-address 80

...There are more :)

Bronze

Re: Answering Incoming Calls on FXO ports

> so you can either give dialtone to calls, or direct all call to a number of your choice using "connection plar".

Providing dialtone is bad since the caller can then use it for toll fraud, and unfortunately I've found these lines get about 3X a day each from Telemarketers, so I doubt that PLAR is a good option for us.

Any way I can just reject the call, i.e. send a busy back?

Hall of Fame Super Gold

Re: Answering Incoming Calls on FXO ports

With FXO, when the lines is free, either you take the call, or don't. There is no ptocol to reject.

So if you want to fight telemarketers using FXO, your only option is to get caller-id, and see if you can find a pattern of caller-id or missing thereof to direct their calls to a message. At the same time you will loose the calls from all the people that has blocked caller-id or is calling from out-of area, as often caller-id doesn't work in these cases.

397
Views
5
Helpful
7
Replies
CreatePlease to create content