×
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Jobs

Inbound SIP Call - Routing Offsite instead dials an internal extension
2

Inbound SIP Call - Routing Offsite instead dials an internal extension

Inbound SIP Call - Routing Offsite instead dials an internal extension

(OP)
CM 6.3 with SBC/Verizon SIP

Inbound SIP cal1 handling Trunk l VDN 1234 routes outbound via SIP trunk 2 to 1-123-456-7890
the trace looks normal like it sends the call, but in fact it routes to an internal auto attendant instead.

The trace in both Session Manager and ASA both look like the call routed to the offsite destination.

Dialing the offsite number directly from SIP and a Mobile does route to the right destination.

The vector is simple, wait time, route to v1 which is 91xxx-xxx-xxxx

This works fine if we route the offsite number via ISDN

Any idea where to point on where to start with this? It affects multiple numbers/multiple area codes.

They said it's because SIP does not want to see it's own caller ID's coming in then going out again, even though different trunks?

Thanks
PhonesAllDay

RE: Inbound SIP Call - Routing Offsite instead dials an internal extension

"They said it's because SIP does not want to see it's own caller ID's"

Who is "They"?

Do you have 2 separate SIP trunks supplied by Verizon to your SBC? If not the call is trying to go back out the same trunk to the same carrier. You should capture some packets and look at the call set up information because it's likely Verizon is redirecting back to you that outbound call because the call record matches the other call already in progress. I guess it should be possible to use a sigma script at the SBC to modify the outbound leg but you will probably need your BP to help set that up for you.

RE: Inbound SIP Call - Routing Offsite instead dials an internal extension

traceSM - what does the outbound leg show for "from" and "p asserted identity" and "diversion"?

https://www.devconnectprogram.com/fileMedia/downlo...

Does your SM use the "Verizon Adapter" to massage messaging to them? Does your SBC do any sigma scripting to the carrier?

The devconnect note shows a lot of info about tweaking ec500/forwarded calls and I presume that your VDN/vector forwarding back out would trigger some of the same concepts.

traceSM and traceSBC in/out of SM and the SBC and compare your "direct dial" to "VDN not working" and compare to the app note and I'm sure you'll find something.

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close