12-13-2010 09:17 AM - edited 03-16-2019 02:24 AM
Hi Experts,
This is some thing weird problem...whose area code starts with 9 and when they try to call FXO pots line after first ring they get dial tone then ends with fast busy signal...
When I tried with all possibilities I figured out that its hitting SRST dial peers:
dial-peer voice 8 pots
preference 8
destination-pattern 9T
incoming called-number .
port 0/2/3
when I removed or shutdown this dial-peers it works fine..
Check Below debug these captured when we have dial tone..
Line 62: Peer Info Type=DIALPEER_INFO_SPEECH
Line 68: Dial String=, Expanded String=, Calling Number=9018012250T
Line 69: Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_SPEECH
Line 78: Dial String=, Expanded String=, Calling Number=9018012250T
Line 79: Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_SPEECH
Line 81: Result=Success(0); Incoming Dial-peer=1 Is Matched
Line 83: Result=Success(0); Incoming Dial-peer=2 Is Matched
Line 85: Result=Success(0); Incoming Dial-peer=3 Is Matched
Line 87: Result=Success(0); Incoming Dial-peer=4 Is Matched
Line 89: Result=Success(0); Incoming Dial-peer=5 Is Matched
Line 91: Result=Success(0); Incoming Dial-peer=6 Is Matched
Line 93: Result=Success(0); Incoming Dial-peer=7 Is Matched
Line 95: Result=Success(0); Incoming Dial-peer=8 Is Matched
Line 98: Result=Success(0) after DP_MATCH_ORIGINATE; Incoming Dial-peer=1
Line 150: Incoming Dial-peer=1, Progress Indication=ORIGINATING SIDE IS NON ISDN(3), Calling IE Present=TRUE,
Line 183: Stop Tone On Digit=TRUE, Tone=Dial Tone,
Line 205: Fax Relay=TRUE, Dial Tone=TRUE, Digit Collect=TRUE, Overlap=FALSE, DID=FALSE
Line 329: Peer Info Type=DIALPEER_INFO_SPEECH
Line 335: Dial String=, Expanded String=, Calling Number=9TT
Line 336: Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_SPEECH
Line 345: Dial String=, Expanded String=, Calling Number=9TT
Line 346: Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_SPEECH
Line 348: Result=Success(0); Incoming Dial-peer=1 Is Matched
Line 350: Result=Success(0); Incoming Dial-peer=2 Is Matched
Line 352: Result=Success(0); Incoming Dial-peer=3 Is Matched
Line 354: Result=Success(0); Incoming Dial-peer=4 Is Matched
Line 357: SCOTRT002#Result=Success(0); Incoming Dial-peer=5 Is Matched
Line 359: Result=Success(0); Incoming Dial-peer=6 Is Matched
Line 361: Result=Success(0); Incoming Dial-peer=7 Is Matched
Line 363: Result=Success(0); Incoming Dial-peer=8 Is Matched
Solved! Go to Solution.
12-13-2010 02:11 PM
I am sorry...I didn't abused or used any hurting language in these post....what ever I posted it was simple and straight forward that's it....even you think it was abusing language...I apologize...I am sorry for that....Thank you so much...
12-13-2010 02:14 PM
I am glad I could help. Dont forget to rate the posts!
12-13-2010 02:20 PM
Hello,
Would you mind deleting the incomming called number . from the SRST dial peers.
Thanks,
Luis Sandi
05-03-2013 09:29 AM
I ran into this same issue. I tried the recommended steps with no luck. After working with TAC and enabling "answer-address ." to the MGCP dial peers, calls routed correclty. This was applied to all mgcp dial peers.
Example:
dial-peer voice 999000 pots
service mgcpapp
answer-address .
port 0/0/0
I hope this helps someone in the future!
Thanks
Keith
05-30-2013 05:08 AM
Thank you Friend.
When I had the same issue very long back I worked with tac and it was bug with code i was using on gatewasy for MGCP and I guess they added the same command to solved the problem.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide