asterisk users - Feb 2005 - setting caller id number and using sip type=peer for incomming calles.

Just to bug you all (feel free to rant at me),

 

a client wants to set his caller*ID number for outbound calls though us
to PSTN.

the client is using SIP to us, he can set the caller*ID name fine.

 

if he sets his caller*ID number to anything other than his account
number (8440101), the call is dropped into the default context (and then
hung up by our dial plan).

 

To get around this i updated CVS HEAD and changed the sip entity from
type=user to type=peer (yes peer!) (type=friend works too but im making
a point) the client now must register to set his outbound caller*ID
Number.

it works because when a call comes in asterisk checks its list of
registered users connection info and matches against a peer entity.

 

this seems to be working but it hardly seems correct, i mean using a
peer for inbound calls when the docs all say it is for outbound calls.

 

im not up on the sip protocol but wouldn't it be better if, when
receiving an unknown connection (ie when caller*ID number is set to a
pstn number) it first sends an authentication request to the client, on
return it checks that username/secret against its list of users. if it
still doesn't find it then drop it into the guest account.

 

iv posted a bug with a bit more detail but it was closed as a
configuration issue (which i suppose it is...)

http://bugs.digium.com/bug_view_page.php?bug_id=0003621

 

 

Morgan Gilroy,

Telappliant Support

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20050221/ad8a36b9/attachment.htm

Morgan Gilroy wrote:
> To get around this i updated CVS HEAD and changed the sip entity from 
> type=user to type=peer (yes peer!) (type=friend works too but im making 
> a point) the client now must register to set his outbound caller*ID Number.
Yes, that is normal. SIP has difficulty separating the remote party 
identification from the authentication identification (although it can 
be done).
> this seems to be working but it hardly seems correct, i mean using a 
> peer for inbound calls when the docs all say it is for outbound calls.
In CVS HEAD, soon _all_ SIP entries will be type=peer, because it's more 
logical this way.
> im not up on the sip protocol but wouldn?t it be better if, when 
> receiving an unknown connection (ie when caller*ID number is set to a 
> pstn number) it first sends an authentication request to the client, on 
> return it checks that username/secret against its list of users. if it 
> still doesn?t find it then drop it into the guest account.
I believe it can already be configured to work that way, if you disable 
access to "guest" connections (I've not tried it, though).
Remember also
that it works this way because there are number of providers out there 
(Broadvoice being one) that will _not_ authenticate when they send you a 
call, only when they register.