Can you route SIP call based on distinctive ring?

Unanswered Question
Apr 20th, 2009

I subscribe to a SIP provider who gives me a primary number of say 555-1000. I have an alternate number they let me use which is 555-2000. Both come across as the same To: line, in fact, all the SIP headers are basically the same, the only difference is the alternate number has:

Alert-Info: <http://127.0.0.1/Bellcore-dr3>

Which is setting a distinctive ring. I was hoping I could match on this, with an inbound dial-peer, and then use a translation pattern to to re-write the destination. I tried to use the "incoming uri request" command, but it doesn't seem to be able to match using that.

Does anyone know of another way to make this work, assuming all headers are the same with the exception of the addition of the Alert-Info?

Brian

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
bfeeny Tue, 04/21/2009 - 07:09

Yes I am sure you are right. I wish I could see a sample TCL script that routed a called to a DN based on some header field, preferably a sip header field, then I could likely modify it.

anyone got one?

Brian

bfeeny Tue, 04/21/2009 - 07:35

Yes I am sure you are right. I wish I could see a sample TCL script that routed a called to a DN based on some header field, preferably a sip header field, then I could likely modify it.

anyone got one?

Brian

Actions

This Discussion