[SIPForum-discussion] outgoing phone number

[Dave Jacobson]

Dan,

 

Thank you for the input.  The problem I am facing is the subscriber really
only has one number, a toll-free number.  So when you say that I should keep
the FROM field with the BTN and the Remote-Party-ID with the toll-free
number, I really don't know what the BTN should be other than the toll-free
number.

 

Dave

 

From: Broussard, Dan [mailto:Dan.Broussard at Level3.com] 
Sent: Thursday, August 05, 2010 10:14 AM
To: Dave Jacobson; discussion at sipforum.org
Subject: RE: [SIPForum-discussion] outgoing phone number

 

Many times you have to put in a default BTN.

 

The problem however is that putting in a toll free number.if the call does
get routed.the default jurisdiction is IntraState Long distance. So no
chance of local calling. 

 

This is a bad habit that carries over from the TDM world. Where 1 customer
was hooked up to 1 tie line to 1 DMS 500 [local switch]. Thus the switch
knew the true originating telephone number. However in our world this is not
the case. It's a matter of "weeding" out this bad habit and getting bad to
standards. 

 

They could keep the FROM field with the BTN and Remote-Party-ID with the
Tollfree number. This should give the desired caller ID behavior on the far
end of the call.

 

Dan Broussard

 

From: discussion-bounces at sipforum.org
[mailto:discussion-bounces at sipforum.org] On Behalf Of Dave Jacobson
Sent: Wednesday, August 04, 2010 8:50 AM
To: discussion at sipforum.org
Subject: [SIPForum-discussion] outgoing phone number

 

What do I do if I have a subscriber that only has a toll-free number and the
subscriber places a call to the PSTN?  What do I use for the outgoing phone
number if the PSTN will not accept the subscriber's toll-free number as the
outgoing phone number?  How can I set up the headers so that I do not
violate any rules?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20100806/855f6c96/attachment-0002.html>