[Spce-user] Rewrite rule works on peer but not subscriber

[Stephen Donovan]

Correction- added improper call.

From: Stephen Donovan
Sent: Wednesday, January 8, 2014 10:15 AM
To: 'spce-user at lists.sipwise.com'
Subject: Rewrite rule works on peer but not subscriber

I have a rewrite rule - outbound for callee that prefixes a code in front of the dialed number.

In this case,  it works on the peer requesting this prefix.

As as test for another carrier, who only wants me to prefix t.38 calls, I applied the same rule to a subscriber and removed from the peer, the rewrite is not taking effect then.

Match pattern = ^([0-9]+)$         Replacement Pattern= 130432*\1

Proper call with rewrite on peer

U 2014/01/08 10:03:33.119524 162.216.200.151:5060 -> 108.166.172.198:5060
INVITE sip:130432*16016385211 at 108.166.172.198:5060;transport=udp SIP/2.0'

Improper call - with rewrite on subscriber.

U 2014/01/08 10:11:33.925055 162.216.200.151:5060 -> 108.166.172.198:5060
INVITE sip:16016385211 at 108.166.172.198:5060;transport=udp SIP/2.0'

What I'm trying to accomplish, once I peer this box with another provider, is to be able to prefix fax subscribers so the call is guaranteed a t.38 route, I don't have this setup yet so I'm just testing the rule with this provider that wants a prefix for all calls by moving the rewrite rule to the subscriber level instead of peer.

I'm also working with another SPCE user that has similar needs and has reproduced the same problem.

Stephen

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140108/c1f1f98d/attachment.html>