VoIP Mailing List Archives

[jmr.richardson at gmai...]

Hi All,

I have a Cisco 2600 PRI gateway being hosted on an Asterisk server.
The PRI on the cisco is pointing to a customer legacy PBX, the SIP
VoIP side of the cisco is pointing to an Asterisk server (1.2.X).

In Asterisk, the SIP peer is setup with callerid="some name"<5551212>

In a SIP call from the cisco to asterisk, there is no CID name info in
SIP debug, so Asterisk doesn't seem to inject CID name info for that
SIP Channel on pass through calls. Asterisk does have the CID number
and account number and user info and all other variable associated
with the SIP channel, just no CID name.

When I test with another Asterisk server acting as the PRI gateway,
the CID name is fine.

1. in the cisco, does anyone know what the command is to set a CID
Name for all outbound VoIP calls?

2. is this a bug in Asterisk that will not inject CID name in a
channel if it doesn't have CID name coming in first?

Thanks.

JR
--
JR Richardson
Engineering for the Masses

[peder at networkoblivi...]

Do a "debug isdn q931" on the cisco and see if you are getting cid name
sent to you over the PRI. What kind of PBX is it? I have an issue with
a connection to an ATT 5ESS (not a PBX exactly) and it sends the name
late, so the Cisco sends a SIP UPDATE with the name once it gets it and
* doesn't know what to do with the SIP UPDATE, so we get no name.

JR Richardson wrote:

[sean at datawhale.com]

What ISDN commands do you have under your PRI serial interface?

JR Richardson wrote:

[peder at networkoblivi...]

no ip address
encapsulation hdlc
isdn switch-type primary-ni
isdn incoming-voice voice
isdn supp-service name calling
no cdp enable

Sean Dennis wrote:

[kkielhofner at star2st...]

On 5/28/08, JR Richardson <jmr.richardson at gmail.com> wrote:

[jmr.richardson at gmai...]

[kkielhofner at star2st...]

On 5/29/08, JR Richardson <jmr.richardson at gmail.com> wrote:

[adam at plexicomm.net]

So lemme get this straight:

PBX <-----PRI ------> Cisco2600 <--------SIP--------> Asterisk

Any reason not to eliminate the Cisco?

Either way, as a workaround you could add a Set(Callerid(name)=Your
Name) to the asterisk dialplan

[Alex.Lopez at OpSys.com]

The Cisco gives you some level of flexability like have CallerID name
NOT work!!!

If this is not a production enviorment I would see about setting up the
Asterisk box with a PRI and seeing if the Telco is ACTUALLY sending you
the CID name in the Facility. It is weird that you are not getting it
at the Cisco.

The Wait(1) is only needed if the asterisk box has the PRI on it. As the
SIP invite should have all of the info BEFORE sending it to the Asterisk
box. Kris talked about the Cisco sending it two ways I would tend to
configure it to WAIT for CID Name before placing the SIP call...

Alex

[sean at datawhale.com]

Here is exactly what we have under our serial interface and we get
callerID from our PBX. We had to play around with the settings and we
probably don't need all of this, but I know this passes the name and
number from HARRIS PBX -----T1----Cisco 3640-----SIP-----Asterisk 1.2 & 1.4
interface Serial3/0:23
no ip address
encapsulation hdlc
isdn switch-type primary-ni
isdn not-end-to-end 64
isdn incoming-voice voice
isdn supp-service name calling
isdn outgoing ie facility
isdn outgoing ie connected-number
no cdp enable



JR Richardson wrote:

[peder at networkoblivi...]

Like Kristian said, if you are telnet/ssh'd in, then enable the debug
and do "term mon" and it will echo the debug to your screen. As far as
I know, there is no way to tell the Cisco to "wait 1 second" to get the
CNAM. I have two PRI into the same Cisco with two different providers.
One gets CNAM right away, one gets in in a subsequent facility
message. The second one does not show CNAM on internal phones as the
SIP INFO is not processed by * (the first one does). A debug should
show this.

Kristian Kielhofner wrote:

[joakimsen at gmail.com]

You can not send caller ID name through the outgoing calls. You need
to engage the telco and tell them to set up the number-to-name
associations. Then you just send the right number and basically they
set the caller ID name for you (yes I know technically the name isn't
transmitted end-to-end as part of the call flow, your carrier sets it
in their LIDB ... so on and so forth)

For the inbound calls (from PSTN to your Cisco) have you made sure in
your config you have:

isdn supp-service name calling

Ref: http://www.cisco.com/en/US/docs/ios/12_3/sip/configuration/guide/chapter9.html#wp1063971

Wait() will never affect the caller ID on ISDN channels. That
information is transmitted instantaneously as part of the call setup.
On Thu, May 29, 2008 at 3:25 PM, JR Richardson <jmr.richardson at gmail.com> wrote:

[jmr.richardson at gmai...]

[joakimsen at gmail.com]

On Fri, May 30, 2008 at 5:47 PM, JR Richardson <jmr.richardson at gmail.com> wrote: