Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Cisco: VOIP

DialPeer match failure

 

 

Cisco voip RSS feed   Index | Next | Previous | View Threaded


rbosire at ke

Mar 8, 2006, 7:59 AM

Post #1 of 7 (1386 views)
Permalink
DialPeer match failure

I have AS5300 with an E1/R2 pstn connection.
It is been configured with an outbound voip dial peer which doesnt seem to be
working.

>From debug of dialpeer a match is made and nothing happens thereafter.
What could be wrong?


relevant configs

E1/R2 config

!
controller E1 0
ds0-group 0 timeslots 1-15,17-31 type r2-digital r2-compelled ani


voice-port 0:0
echo-cancel coverage 32
timeouts initial 120
timeouts interdigit 5

dial-peer voice 600 voip
destination-pattern .%
session target ipv4:192.168.199.9




Mar 8 18:51:21.747 EAT: Inside dpMatchCore:
Mar 8 18:51:21.747 EAT: destination pattn: 00254600633 expanded string:
00254600633
Mar 8 18:51:21.747 EAT: Inside dpMatchCore:
Mar 8 18:51:21.747 EAT: destination pattn: 204760002 expanded string:
204760002
Mar 8 18:51:21.747 EAT: Inside dpMatchCore:
Mar 8 18:51:21.747 EAT: destination pattn: 204760002 expanded string:
204760002
Mar 8 18:51:21.747 EAT: MatchNextPeer: Peer 600 matched
Mar 8 18:51:21.747 EAT: dpAssociateIncomingPeer_T null source route label
Mar 8 18:51:21.747 EAT: Inside dpMatchCore:
Mar 8 18:51:21.747 EAT: destination pattn: 00254600633 expanded string:
00254600633
Mar 8 18:51:21.747 EAT: Inside dpMatchCore:
Mar 8 18:51:21.747 EAT: destination pattn: 204760002 expanded string:
204760002
Mar 8 18:51:21.747 EAT: Inside dpMatchCore:
Mar 8 18:51:21.747 EAT: destination pattn: 204760002 expanded string:
204760002
Mar 8 18:51:21.747 EAT: MatchNextPeer: Peer 600 matched
Mar 8 18:51:21.747 EAT: dpAssociateIncomingPeer_T null source route label
Mar 8 18:51:21.747 EAT: Inside dpMatchCore:
Mar 8 18:51:21.747 EAT: Inside dpMatchCore:
Mar 8 18:51:21.747 EAT: Inside dpMatchCore:
Mar 8 18:51:21.751 EAT: dpAssociateIncomingPeer_T null source route label
Mar 8 18:51:37.115 EAT: Inside dpMatchCore:
Mar 8 18:51:37.115 EAT: destination pattn: 00254600633 expanded string:
00254600633
Mar 8 18:51:37.115 EAT: Inside dpMatchCore:
Mar 8 18:51:37.115 EAT: destination pattn: 204760002 expanded string:
204760002
Mar 8 18:51:37.115 EAT: Inside dpMatchCore:
Mar 8 18:51:37.115 EAT: destination pattn: 204760002 expanded string:
204760002
Mar 8 18:51:37.115 EAT: MatchNextPeer: Peer 600 matched
Mar 8 18:51:37.115 EAT: dpAssociateIncomingPeer_T null source route label


cheers

./bosire

_______________________________________________
cisco-voip mailing list
cisco-voip [at] puck
https://puck.nether.net/mailman/listinfo/cisco-voip


pwalenta at wi

Mar 8, 2006, 8:20 AM

Post #2 of 7 (1428 views)
Permalink
Re: DialPeer match failure [In reply to]

>From the debug output below, it looks like the call is matching peer 600.

What sort of issue are you experiencing?

-----Original Message-----
From: cisco-voip-bounces [at] puck
[mailto:cisco-voip-bounces [at] puck] On Behalf Of Richard Bosire
Sent: Wednesday, March 08, 2006 9:59 AM
To: cisco-voip [at] puck
Subject: [cisco-voip] DialPeer match failure



I have AS5300 with an E1/R2 pstn connection.
It is been configured with an outbound voip dial peer which doesnt seem to
be working.

>From debug of dialpeer a match is made and nothing happens thereafter.
What could be wrong?


relevant configs

E1/R2 config

!
controller E1 0
ds0-group 0 timeslots 1-15,17-31 type r2-digital r2-compelled ani


voice-port 0:0
echo-cancel coverage 32
timeouts initial 120
timeouts interdigit 5

dial-peer voice 600 voip
destination-pattern .%
session target ipv4:192.168.199.9




Mar 8 18:51:21.747 EAT: Inside dpMatchCore:
Mar 8 18:51:21.747 EAT: destination pattn: 00254600633 expanded string:
00254600633
Mar 8 18:51:21.747 EAT: Inside dpMatchCore:
Mar 8 18:51:21.747 EAT: destination pattn: 204760002 expanded string:
204760002
Mar 8 18:51:21.747 EAT: Inside dpMatchCore:
Mar 8 18:51:21.747 EAT: destination pattn: 204760002 expanded string:
204760002
Mar 8 18:51:21.747 EAT: MatchNextPeer: Peer 600 matched Mar 8 18:51:21.747
EAT: dpAssociateIncomingPeer_T null source route label Mar 8 18:51:21.747
EAT: Inside dpMatchCore:
Mar 8 18:51:21.747 EAT: destination pattn: 00254600633 expanded string:
00254600633
Mar 8 18:51:21.747 EAT: Inside dpMatchCore:
Mar 8 18:51:21.747 EAT: destination pattn: 204760002 expanded string:
204760002
Mar 8 18:51:21.747 EAT: Inside dpMatchCore:
Mar 8 18:51:21.747 EAT: destination pattn: 204760002 expanded string:
204760002
Mar 8 18:51:21.747 EAT: MatchNextPeer: Peer 600 matched Mar 8 18:51:21.747
EAT: dpAssociateIncomingPeer_T null source route label Mar 8 18:51:21.747
EAT: Inside dpMatchCore:
Mar 8 18:51:21.747 EAT: Inside dpMatchCore:
Mar 8 18:51:21.747 EAT: Inside dpMatchCore:
Mar 8 18:51:21.751 EAT: dpAssociateIncomingPeer_T null source route label
Mar 8 18:51:37.115 EAT: Inside dpMatchCore:
Mar 8 18:51:37.115 EAT: destination pattn: 00254600633 expanded string:
00254600633
Mar 8 18:51:37.115 EAT: Inside dpMatchCore:
Mar 8 18:51:37.115 EAT: destination pattn: 204760002 expanded string:
204760002
Mar 8 18:51:37.115 EAT: Inside dpMatchCore:
Mar 8 18:51:37.115 EAT: destination pattn: 204760002 expanded string:
204760002
Mar 8 18:51:37.115 EAT: MatchNextPeer: Peer 600 matched
Mar 8 18:51:37.115 EAT: dpAssociateIncomingPeer_T null source route label



cheers

./bosire

_______________________________________________
cisco-voip mailing list
cisco-voip [at] puck
https://puck.nether.net/mailman/listinfo/cisco-voip

_______________________________________________
cisco-voip mailing list
cisco-voip [at] puck
https://puck.nether.net/mailman/listinfo/cisco-voip


rbosire at ke

Mar 8, 2006, 8:27 AM

Post #3 of 7 (1369 views)
Permalink
Re: DialPeer match failure [In reply to]

howdy

I expected once the peer has been matched, the voip leg of the call to be
initiated i.e


Mar 8 19:26:31.161 EAT: MatchNextPeer: Peer 50 matched
Mar 8 19:26:31.161 EAT: dpMatchPeersMoreArg: Result=0 after MATCH_ORIGINATE




On Wednesday 08 March 2006 19:20, Philip Walenta wrote:
> From the debug output below, it looks like the call is matching peer 600.
>
> What sort of issue are you experiencing?
>
> -----Original Message-----
> From: cisco-voip-bounces [at] puck
> [mailto:cisco-voip-bounces [at] puck] On Behalf Of Richard Bosire
> Sent: Wednesday, March 08, 2006 9:59 AM
> To: cisco-voip [at] puck
> Subject: [cisco-voip] DialPeer match failure
>
>
>
> I have AS5300 with an E1/R2 pstn connection.
> It is been configured with an outbound voip dial peer which doesnt seem to
> be working.
>
> >From debug of dialpeer a match is made and nothing happens thereafter.
>
> What could be wrong?
>
>
> relevant configs
>
> E1/R2 config
>
> !
> controller E1 0
> ds0-group 0 timeslots 1-15,17-31 type r2-digital r2-compelled ani
>
>
> voice-port 0:0
> echo-cancel coverage 32
> timeouts initial 120
> timeouts interdigit 5
>
> dial-peer voice 600 voip
> destination-pattern .%
> session target ipv4:192.168.199.9
>
>
>
>
> Mar 8 18:51:21.747 EAT: Inside dpMatchCore:
> Mar 8 18:51:21.747 EAT: destination pattn: 00254600633 expanded string:
> 00254600633
> Mar 8 18:51:21.747 EAT: Inside dpMatchCore:
> Mar 8 18:51:21.747 EAT: destination pattn: 204760002 expanded string:
> 204760002
> Mar 8 18:51:21.747 EAT: Inside dpMatchCore:
> Mar 8 18:51:21.747 EAT: destination pattn: 204760002 expanded string:
> 204760002
> Mar 8 18:51:21.747 EAT: MatchNextPeer: Peer 600 matched Mar 8
> 18:51:21.747 EAT: dpAssociateIncomingPeer_T null source route label Mar 8
> 18:51:21.747 EAT: Inside dpMatchCore:
> Mar 8 18:51:21.747 EAT: destination pattn: 00254600633 expanded string:
> 00254600633
> Mar 8 18:51:21.747 EAT: Inside dpMatchCore:
> Mar 8 18:51:21.747 EAT: destination pattn: 204760002 expanded string:
> 204760002
> Mar 8 18:51:21.747 EAT: Inside dpMatchCore:
> Mar 8 18:51:21.747 EAT: destination pattn: 204760002 expanded string:
> 204760002
> Mar 8 18:51:21.747 EAT: MatchNextPeer: Peer 600 matched Mar 8
> 18:51:21.747 EAT: dpAssociateIncomingPeer_T null source route label Mar 8
> 18:51:21.747 EAT: Inside dpMatchCore:
> Mar 8 18:51:21.747 EAT: Inside dpMatchCore:
> Mar 8 18:51:21.747 EAT: Inside dpMatchCore:
> Mar 8 18:51:21.751 EAT: dpAssociateIncomingPeer_T null source route label
> Mar 8 18:51:37.115 EAT: Inside dpMatchCore:
> Mar 8 18:51:37.115 EAT: destination pattn: 00254600633 expanded string:
> 00254600633
> Mar 8 18:51:37.115 EAT: Inside dpMatchCore:
> Mar 8 18:51:37.115 EAT: destination pattn: 204760002 expanded string:
> 204760002
> Mar 8 18:51:37.115 EAT: Inside dpMatchCore:
> Mar 8 18:51:37.115 EAT: destination pattn: 204760002 expanded string:
> 204760002
> Mar 8 18:51:37.115 EAT: MatchNextPeer: Peer 600 matched
> Mar 8 18:51:37.115 EAT: dpAssociateIncomingPeer_T null source route label
>
>
>
> cheers
>
> ./bosire
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip [at] puck
> https://puck.nether.net/mailman/listinfo/cisco-voip

--
richard bosire
uunet (k) Ltd, tel +254 20 6988000, fax +254 20 6988001, cell 254 722 526063

_______________________________________________
cisco-voip mailing list
cisco-voip [at] puck
https://puck.nether.net/mailman/listinfo/cisco-voip


jonvoip at gmail

Mar 8, 2006, 8:38 AM

Post #4 of 7 (1373 views)
Permalink
Re: DialPeer match failure [In reply to]

Most likely his issue is at 192.168.199.9 he needs to ensure that he is
dealing with those digits meaningfully at the other end.


J

On 3/8/06, Philip Walenta <pwalenta [at] wi> wrote:
>
> >From the debug output below, it looks like the call is matching peer 600.
>
> What sort of issue are you experiencing?
>
> -----Original Message-----
> From: cisco-voip-bounces [at] puck
> [mailto:cisco-voip-bounces [at] puck] On Behalf Of Richard Bosire
> Sent: Wednesday, March 08, 2006 9:59 AM
> To: cisco-voip [at] puck
> Subject: [cisco-voip] DialPeer match failure
>
>
>
> I have AS5300 with an E1/R2 pstn connection.
> It is been configured with an outbound voip dial peer which doesnt seem
> to
> be working.
>
> >From debug of dialpeer a match is made and nothing happens thereafter.
> What could be wrong?
>
>
> relevant configs
>
> E1/R2 config
>
> !
> controller E1 0
> ds0-group 0 timeslots 1-15,17-31 type r2-digital r2-compelled ani
>
>
> voice-port 0:0
> echo-cancel coverage 32
> timeouts initial 120
> timeouts interdigit 5
>
> dial-peer voice 600 voip
> destination-pattern .%
> session target ipv4:192.168.199.9
>
>
>
>
> Mar 8 18:51:21.747 EAT: Inside dpMatchCore:
> Mar 8 18:51:21.747 EAT: destination pattn: 00254600633 expanded string:
> 00254600633
> Mar 8 18:51:21.747 EAT: Inside dpMatchCore:
> Mar 8 18:51:21.747 EAT: destination pattn: 204760002 expanded string:
> 204760002
> Mar 8 18:51:21.747 EAT: Inside dpMatchCore:
> Mar 8 18:51:21.747 EAT: destination pattn: 204760002 expanded string:
> 204760002
> Mar 8 18:51:21.747 EAT: MatchNextPeer: Peer 600 matched Mar 8 18:51:
> 21.747
> EAT: dpAssociateIncomingPeer_T null source route label Mar 8 18:51:
> 21.747
> EAT: Inside dpMatchCore:
> Mar 8 18:51:21.747 EAT: destination pattn: 00254600633 expanded string:
> 00254600633
> Mar 8 18:51:21.747 EAT: Inside dpMatchCore:
> Mar 8 18:51:21.747 EAT: destination pattn: 204760002 expanded string:
> 204760002
> Mar 8 18:51:21.747 EAT: Inside dpMatchCore:
> Mar 8 18:51:21.747 EAT: destination pattn: 204760002 expanded string:
> 204760002
> Mar 8 18:51:21.747 EAT: MatchNextPeer: Peer 600 matched Mar 8 18:51:
> 21.747
> EAT: dpAssociateIncomingPeer_T null source route label Mar 8 18:51:
> 21.747
> EAT: Inside dpMatchCore:
> Mar 8 18:51:21.747 EAT: Inside dpMatchCore:
> Mar 8 18:51:21.747 EAT: Inside dpMatchCore:
> Mar 8 18:51:21.751 EAT: dpAssociateIncomingPeer_T null source route
> label
> Mar 8 18:51:37.115 EAT: Inside dpMatchCore:
> Mar 8 18:51:37.115 EAT: destination pattn: 00254600633 expanded string:
> 00254600633
> Mar 8 18:51:37.115 EAT: Inside dpMatchCore:
> Mar 8 18:51:37.115 EAT: destination pattn: 204760002 expanded string:
> 204760002
> Mar 8 18:51:37.115 EAT: Inside dpMatchCore:
> Mar 8 18:51:37.115 EAT: destination pattn: 204760002 expanded string:
> 204760002
> Mar 8 18:51:37.115 EAT: MatchNextPeer: Peer 600 matched
> Mar 8 18:51:37.115 EAT: dpAssociateIncomingPeer_T null source route
> label
>
>
>
> cheers
>
> ./bosire
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip [at] puck
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip [at] puck
> https://puck.nether.net/mailman/listinfo/cisco-voip
>


rbosire at ke

Mar 8, 2006, 9:07 AM

Post #5 of 7 (1373 views)
Permalink
Re: DialPeer match failure [In reply to]

Hello's

The voip call never happens

On Wednesday 08 March 2006 19:38, Jonathan Charles wrote:
> Most likely his issue is at 192.168.199.9 he needs to ensure that he is
> dealing with those digits meaningfully at the other end.
>
>
> J
>
> On 3/8/06, Philip Walenta <pwalenta [at] wi> wrote:
> > >From the debug output below, it looks like the call is matching peer
> > > 600.
> >
> > What sort of issue are you experiencing?
> >
> > -----Original Message-----
> > From: cisco-voip-bounces [at] puck
> > [mailto:cisco-voip-bounces [at] puck] On Behalf Of Richard Bosire
> > Sent: Wednesday, March 08, 2006 9:59 AM
> > To: cisco-voip [at] puck
> > Subject: [cisco-voip] DialPeer match failure
> >
> >
> >
> > I have AS5300 with an E1/R2 pstn connection.
> > It is been configured with an outbound voip dial peer which doesnt seem
> > to
> > be working.
> >
> > >From debug of dialpeer a match is made and nothing happens thereafter.
> >
> > What could be wrong?
> >
> >
> > relevant configs
> >
> > E1/R2 config
> >
> > !
> > controller E1 0
> > ds0-group 0 timeslots 1-15,17-31 type r2-digital r2-compelled ani
> >
> >
> > voice-port 0:0
> > echo-cancel coverage 32
> > timeouts initial 120
> > timeouts interdigit 5
> >
> > dial-peer voice 600 voip
> > destination-pattern .%
> > session target ipv4:192.168.199.9
> >
> >
> >
> >
> > Mar 8 18:51:21.747 EAT: Inside dpMatchCore:
> > Mar 8 18:51:21.747 EAT: destination pattn: 00254600633 expanded string:
> > 00254600633
> > Mar 8 18:51:21.747 EAT: Inside dpMatchCore:
> > Mar 8 18:51:21.747 EAT: destination pattn: 204760002 expanded string:
> > 204760002
> > Mar 8 18:51:21.747 EAT: Inside dpMatchCore:
> > Mar 8 18:51:21.747 EAT: destination pattn: 204760002 expanded string:
> > 204760002
> > Mar 8 18:51:21.747 EAT: MatchNextPeer: Peer 600 matched Mar 8 18:51:
> > 21.747
> > EAT: dpAssociateIncomingPeer_T null source route label Mar 8 18:51:
> > 21.747
> > EAT: Inside dpMatchCore:
> > Mar 8 18:51:21.747 EAT: destination pattn: 00254600633 expanded string:
> > 00254600633
> > Mar 8 18:51:21.747 EAT: Inside dpMatchCore:
> > Mar 8 18:51:21.747 EAT: destination pattn: 204760002 expanded string:
> > 204760002
> > Mar 8 18:51:21.747 EAT: Inside dpMatchCore:
> > Mar 8 18:51:21.747 EAT: destination pattn: 204760002 expanded string:
> > 204760002
> > Mar 8 18:51:21.747 EAT: MatchNextPeer: Peer 600 matched Mar 8 18:51:
> > 21.747
> > EAT: dpAssociateIncomingPeer_T null source route label Mar 8 18:51:
> > 21.747
> > EAT: Inside dpMatchCore:
> > Mar 8 18:51:21.747 EAT: Inside dpMatchCore:
> > Mar 8 18:51:21.747 EAT: Inside dpMatchCore:
> > Mar 8 18:51:21.751 EAT: dpAssociateIncomingPeer_T null source route
> > label
> > Mar 8 18:51:37.115 EAT: Inside dpMatchCore:
> > Mar 8 18:51:37.115 EAT: destination pattn: 00254600633 expanded string:
> > 00254600633
> > Mar 8 18:51:37.115 EAT: Inside dpMatchCore:
> > Mar 8 18:51:37.115 EAT: destination pattn: 204760002 expanded string:
> > 204760002
> > Mar 8 18:51:37.115 EAT: Inside dpMatchCore:
> > Mar 8 18:51:37.115 EAT: destination pattn: 204760002 expanded string:
> > 204760002
> > Mar 8 18:51:37.115 EAT: MatchNextPeer: Peer 600 matched
> > Mar 8 18:51:37.115 EAT: dpAssociateIncomingPeer_T null source route
> > label
> >
> >
> >
> > cheers
> >
> > ./bosire
> >
> > _______________________________________________
> > cisco-voip mailing list
> > cisco-voip [at] puck
> > https://puck.nether.net/mailman/listinfo/cisco-voip
> >
> > _______________________________________________
> > cisco-voip mailing list
> > cisco-voip [at] puck
> > https://puck.nether.net/mailman/listinfo/cisco-voip

--
richard bosire
uunet (k) Ltd, tel +254 20 6988000, fax +254 20 6988001, cell 254 722 526063

_______________________________________________
cisco-voip mailing list
cisco-voip [at] puck
https://puck.nether.net/mailman/listinfo/cisco-voip


pwalenta at wi

Mar 8, 2006, 9:19 AM

Post #6 of 7 (1364 views)
Permalink
Re: DialPeer match failure [In reply to]

So you are calling from a POTS based line to a Voip peer?

-----Original Message-----
From: Richard Bosire [mailto:rbosire [at] ke]
Sent: Wednesday, March 08, 2006 11:07 AM
To: Jonathan Charles
Cc: Philip Walenta; cisco-voip [at] puck
Subject: Re: [cisco-voip] DialPeer match failure

Hello's

The voip call never happens

On Wednesday 08 March 2006 19:38, Jonathan Charles wrote:
> Most likely his issue is at 192.168.199.9 he needs to ensure that he
> is dealing with those digits meaningfully at the other end.
>
>
> J
>
> On 3/8/06, Philip Walenta <pwalenta [at] wi> wrote:
> > >From the debug output below, it looks like the call is matching
> > >peer 600.
> >
> > What sort of issue are you experiencing?
> >
> > -----Original Message-----
> > From: cisco-voip-bounces [at] puck
> > [mailto:cisco-voip-bounces [at] puck] On Behalf Of Richard
> > Bosire
> > Sent: Wednesday, March 08, 2006 9:59 AM
> > To: cisco-voip [at] puck
> > Subject: [cisco-voip] DialPeer match failure
> >
> >
> >
> > I have AS5300 with an E1/R2 pstn connection.
> > It is been configured with an outbound voip dial peer which doesnt
> > seem to be working.
> >
> > >From debug of dialpeer a match is made and nothing happens thereafter.
> >
> > What could be wrong?
> >
> >
> > relevant configs
> >
> > E1/R2 config
> >
> > !
> > controller E1 0
> > ds0-group 0 timeslots 1-15,17-31 type r2-digital r2-compelled ani
> >
> >
> > voice-port 0:0
> > echo-cancel coverage 32
> > timeouts initial 120
> > timeouts interdigit 5
> >
> > dial-peer voice 600 voip
> > destination-pattern .%
> > session target ipv4:192.168.199.9
> >
> >
> >
> >
> > Mar 8 18:51:21.747 EAT: Inside dpMatchCore:
> > Mar 8 18:51:21.747 EAT: destination pattn: 00254600633 expanded
string:
> > 00254600633
> > Mar 8 18:51:21.747 EAT: Inside dpMatchCore:
> > Mar 8 18:51:21.747 EAT: destination pattn: 204760002 expanded string:
> > 204760002
> > Mar 8 18:51:21.747 EAT: Inside dpMatchCore:
> > Mar 8 18:51:21.747 EAT: destination pattn: 204760002 expanded string:
> > 204760002
> > Mar 8 18:51:21.747 EAT: MatchNextPeer: Peer 600 matched Mar 8 18:51:
> > 21.747
> > EAT: dpAssociateIncomingPeer_T null source route label Mar 8 18:51:
> > 21.747
> > EAT: Inside dpMatchCore:
> > Mar 8 18:51:21.747 EAT: destination pattn: 00254600633 expanded
string:
> > 00254600633
> > Mar 8 18:51:21.747 EAT: Inside dpMatchCore:
> > Mar 8 18:51:21.747 EAT: destination pattn: 204760002 expanded string:
> > 204760002
> > Mar 8 18:51:21.747 EAT: Inside dpMatchCore:
> > Mar 8 18:51:21.747 EAT: destination pattn: 204760002 expanded string:
> > 204760002
> > Mar 8 18:51:21.747 EAT: MatchNextPeer: Peer 600 matched Mar 8 18:51:
> > 21.747
> > EAT: dpAssociateIncomingPeer_T null source route label Mar 8 18:51:
> > 21.747
> > EAT: Inside dpMatchCore:
> > Mar 8 18:51:21.747 EAT: Inside dpMatchCore:
> > Mar 8 18:51:21.747 EAT: Inside dpMatchCore:
> > Mar 8 18:51:21.751 EAT: dpAssociateIncomingPeer_T null source
> > route label Mar 8 18:51:37.115 EAT: Inside dpMatchCore:
> > Mar 8 18:51:37.115 EAT: destination pattn: 00254600633 expanded
string:
> > 00254600633
> > Mar 8 18:51:37.115 EAT: Inside dpMatchCore:
> > Mar 8 18:51:37.115 EAT: destination pattn: 204760002 expanded string:
> > 204760002
> > Mar 8 18:51:37.115 EAT: Inside dpMatchCore:
> > Mar 8 18:51:37.115 EAT: destination pattn: 204760002 expanded string:
> > 204760002
> > Mar 8 18:51:37.115 EAT: MatchNextPeer: Peer 600 matched Mar 8
> > 18:51:37.115 EAT: dpAssociateIncomingPeer_T null source route label
> >
> >
> >
> > cheers
> >
> > ./bosire
> >
> > _______________________________________________
> > cisco-voip mailing list
> > cisco-voip [at] puck
> > https://puck.nether.net/mailman/listinfo/cisco-voip
> >
> > _______________________________________________
> > cisco-voip mailing list
> > cisco-voip [at] puck
> > https://puck.nether.net/mailman/listinfo/cisco-voip

--
richard bosire
uunet (k) Ltd, tel +254 20 6988000, fax +254 20 6988001, cell 254 722 526063

_______________________________________________
cisco-voip mailing list
cisco-voip [at] puck
https://puck.nether.net/mailman/listinfo/cisco-voip


jonvoip at gmail

Mar 8, 2006, 11:39 AM

Post #7 of 7 (1389 views)
Permalink
Re: DialPeer match failure [In reply to]

Also, your destination-pattern seems unusual, you do realize you will be
hitting a 10-second interdigit timeout, while the voip leg waits for
additional digits...

What digits is telco sending you? You may want to modify to match the sent
digits.



J

On 3/8/06, Jonathan Charles <jonvoip [at] gmail> wrote:
>
> When you make the call, what does a 'show call active voice' show?
>
> Do a debug voip dialpeer all...
>
>
>
> J
>
>
> On 3/8/06, Richard Bosire < rbosire [at] ke> wrote:
> >
> >
> > The call is being initiated from pstn via the E1/R2
> > and I am trying to it get routed to a voip relay server but the
> > voip call
> > is not happening!
> >
> > regards
> >
> > On Wednesday 08 March 2006 20:19, you wrote:
> > > So you are calling from a POTS based line to a Voip peer?
> > >
> > > -----Original Message-----
> > > From: Richard Bosire [mailto:rbosire [at] ke]
> > > Sent: Wednesday, March 08, 2006 11:07 AM
> > > To: Jonathan Charles
> > > Cc: Philip Walenta; cisco-voip [at] puck
> > > Subject: Re: [cisco-voip] DialPeer match failure
> > >
> > > Hello's
> > >
> > > The voip call never happens
> > >
> > > On Wednesday 08 March 2006 19:38, Jonathan Charles wrote:
> > > > Most likely his issue is at 192.168.199.9 he needs to ensure that he
> > > > is dealing with those digits meaningfully at the other end.
> > > >
> > > >
> > > > J
> > > >
> > > > On 3/8/06, Philip Walenta <pwalenta [at] wi> wrote:
> > > > > >From the debug output below, it looks like the call is matching
> > > > > >peer 600.
> > > > >
> > > > > What sort of issue are you experiencing?
> > > > >
> > > > > -----Original Message-----
> > > > > From: cisco-voip-bounces [at] puck
> > > > > [mailto:cisco-voip-bounces [at] puck] On Behalf Of Richard
> > > > > Bosire
> > > > > Sent: Wednesday, March 08, 2006 9:59 AM
> > > > > To: cisco-voip [at] puck
> > > > > Subject: [cisco-voip] DialPeer match failure
> > > > >
> > > > >
> > > > >
> > > > > I have AS5300 with an E1/R2 pstn connection.
> > > > > It is been configured with an outbound voip dial peer which
> > doesnt
> > > > > seem to be working.
> > > > >
> > > > > >From debug of dialpeer a match is made and nothing happens
> > thereafter.
> > > > >
> > > > > What could be wrong?
> > > > >
> > > > >
> > > > > relevant configs
> > > > >
> > > > > E1/R2 config
> > > > >
> > > > > !
> > > > > controller E1 0
> > > > > ds0-group 0 timeslots 1-15,17-31 type r2-digital r2-compelled ani
> > > > >
> > > > >
> > > > > voice-port 0:0
> > > > > echo-cancel coverage 32
> > > > > timeouts initial 120
> > > > > timeouts interdigit 5
> > > > >
> > > > > dial-peer voice 600 voip
> > > > > destination-pattern .%
> > > > > session target ipv4:192.168.199.9
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > Mar 8 18:51:21.747 EAT: Inside dpMatchCore:
> > > > > Mar 8 18:51:21.747 EAT: destination pattn: 00254600633 expanded
> > >
> > > string:
> > > > > 00254600633
> > > > > Mar 8 18:51:21.747 EAT: Inside dpMatchCore:
> > > > > Mar 8 18:51:21.747 EAT: destination pattn: 204760002 expanded
> > string:
> > > > > 204760002
> > > > > Mar 8 18:51:21.747 EAT: Inside dpMatchCore:
> > > > > Mar 8 18:51:21.747 EAT: destination pattn: 204760002 expanded
> > string:
> > > > > 204760002
> > > > > Mar 8 18:51:21.747 EAT: MatchNextPeer: Peer 600 matched Mar 8
> > 18:51:
> > > > > 21.747
> > > > > EAT: dpAssociateIncomingPeer_T null source route label Mar 8
> > 18:51:
> > > > > 21.747
> > > > > EAT: Inside dpMatchCore:
> > > > > Mar 8 18:51:21.747 EAT: destination pattn: 00254600633 expanded
> > >
> > > string:
> > > > > 00254600633
> > > > > Mar 8 18:51:21.747 EAT: Inside dpMatchCore:
> > > > > Mar 8 18:51:21.747 EAT: destination pattn: 204760002 expanded
> > string:
> > > > > 204760002
> > > > > Mar 8 18:51:21.747 EAT: Inside dpMatchCore:
> > > > > Mar 8 18:51:21.747 EAT: destination pattn: 204760002 expanded
> > string:
> > > > > 204760002
> > > > > Mar 8 18:51:21.747 EAT: MatchNextPeer: Peer 600 matched Mar 8
> > 18:51:
> > > > > 21.747
> > > > > EAT: dpAssociateIncomingPeer_T null source route label Mar 8
> > 18:51:
> > > > > 21.747
> > > > > EAT: Inside dpMatchCore:
> > > > > Mar 8 18:51:21.747 EAT: Inside dpMatchCore:
> > > > > Mar 8 18:51:21.747 EAT: Inside dpMatchCore:
> > > > > Mar 8 18:51:21.751 EAT: dpAssociateIncomingPeer_T null source
> > > > > route label Mar 8 18:51:37.115 EAT: Inside dpMatchCore:
> > > > > Mar 8 18:51:37.115 EAT: destination pattn: 00254600633 expanded
> > >
> > > string:
> > > > > 00254600633
> > > > > Mar 8 18:51:37.115 EAT: Inside dpMatchCore:
> > > > > Mar 8 18:51: 37.115 EAT: destination pattn: 204760002 expanded
> > string:
> > > > > 204760002
> > > > > Mar 8 18:51:37.115 EAT: Inside dpMatchCore:
> > > > > Mar 8 18:51:37.115 EAT: destination pattn: 204760002 expanded
> > string:
> > > > > 204760002
> > > > > Mar 8 18:51:37.115 EAT: MatchNextPeer: Peer 600 matched Mar 8
> > > > > 18:51:37.115 EAT: dpAssociateIncomingPeer_T null source route
> > label
> > > > >
> > > > >
> > > > >
> > > > > cheers
> > > > >
> > > > > ./bosire
> > > > >
> > > > > _______________________________________________
> > > > > cisco-voip mailing list
> > > > > cisco-voip [at] puck
> > > > > https://puck.nether.net/mailman/listinfo/cisco-voip
> > > > >
> > > > > _______________________________________________
> > > > > cisco-voip mailing list
> > > > > cisco-voip [at] puck
> > > > > https://puck.nether.net/mailman/listinfo/cisco-voip
> > >
> > > --
> > > richard bosire
> > > uunet (k) Ltd, tel +254 20 6988000, fax +254 20 6988001, cell 254 722
> > > 526063
> >
> > --
> > richard bosire
> > uunet (k) Ltd, tel +254 20 6988000, fax +254 20 6988001, cell 254 722
> > 526063
> >
> >
>

Cisco voip RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.