Peder @ NetworkOblivion
2007-Apr-09 21:01 UTC
[asterisk-users] Cisco GW, PRI & CallerID Name
Does anybody have callerid name coming in on a Cisco PRI via a Cisco gateway via SIP to *? I've seen a few people ask and a few people that say it should work, but I've never seen an actual working config. I do a debug on our Cisco gateway and I can see the callerid name, however none of the features that should send it via SIP seem to work. Cisco docs say to use the following: voice service voip signaling forward unconditional interface serial 1/0:23 isdn supp-service name calling When I enable either of those features, my calls hangup after about 30 seconds. * gives me a message "[Apr 9 22:52:22] WARNING[14660]: chan_sip.c:1916 retrans_pkt: Hanging up call A94C164B-E64D11DB-80BCE9B9-6C3796E8@192.168.1.9 - no reply to our critical packet." Turning them off makes the calls work fine. "signaling forward unconditional" appears to be the key feature, but * doesn't seem to know what to do with the info that it is sending. There must be some way to set * to decode it, but I can't figure it out. I am running * 1.4.2 (and I've tried it on 1.0.3 and 1.2.10) and 12.4.13a on my Cisco gateway. Any ideas? FYI, my gateway has been running fine with multiple * boxes for 2+ years. I've finally decided to try and get this working, so I upgraded to 12.4.13a to see if it worked there and it still doesn't. Peder
I have a PRI fed into a Cisco AS5300 media gateway and sent to Asterisk via SIP, and caller ID works fine. I can probably help you figure it out, even though I don't have any immediate insights. Feel free to e-mail me off list if you like. In general, however, I don't have "isdn supp-service name calling" enabled, and have my signaling on the voip dial-peer set to "signaling forward conditional." -- Alex On Mon, 9 Apr 2007, Peder @ NetworkOblivion said something to this effect:> Does anybody have callerid name coming in on a Cisco PRI via a Cisco gateway > via SIP to *? I've seen a few people ask and a few people that say it should > work, but I've never seen an actual working config. > > I do a debug on our Cisco gateway and I can see the callerid name, however > none of the features that should send it via SIP seem to work. Cisco docs say > to use the following: > > voice service voip > signaling forward unconditional > > interface serial 1/0:23 > isdn supp-service name calling > > > When I enable either of those features, my calls hangup after about 30 > seconds. * gives me a message "[Apr 9 22:52:22] WARNING[14660]: > chan_sip.c:1916 retrans_pkt: Hanging up call > A94C164B-E64D11DB-80BCE9B9-6C3796E8@192.168.1.9 - no reply to our critical > packet." > > Turning them off makes the calls work fine. "signaling forward > unconditional" appears to be the key feature, but * doesn't seem to know what > to do with the info that it is sending. There must be some way to set * to > decode it, but I can't figure it out. > > I am running * 1.4.2 (and I've tried it on 1.0.3 and 1.2.10) and 12.4.13a on > my Cisco gateway. > > Any ideas? FYI, my gateway has been running fine with multiple * boxes for > 2+ years. I've finally decided to try and get this working, so I upgraded to > 12.4.13a to see if it worked there and it still doesn't. > > > Peder > > _______________________________________________ > --Bandwidth and Colocation provided by Easynews.com -- > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users >-- Alex Balashov <sasha@presidium.org>
Yehavi Bourvine +972-8-9489444
2007-Apr-09 21:11 UTC
[asterisk-users] Cisco GW, PRI & CallerID Name
> Does anybody have callerid name coming in on a Cisco PRI via a Cisco > gateway via SIP to *? I've seen a few people ask and a few people that > say it should work, but I've never seen an actual working config.I have it working, but it depends on the specific configuration. I have it working via PRI/Q.sig to a Nortel TX-1. The key issue here is that the name can be sent in two ways: via the Q.931 and via Q.sig. Nortel supports only Q.sig, and you need to enable it on the Cisco. If this is your case then tell me and I'll send the config. __Yehavi: