[SIPForum-discussion] Cisco AS5350 as VOIP g/w to handle redircet responses

Prashanth Patha prashanth.patha at gmail.com
Wed Sep 2 04:36:06 UTC 2009


Pays to use progress indicator as well inside the dial peer.

progress_ind setup enable 3
progress_ind progress enable 8

You can read through more info from here:

http://www.cisco.com/en/US/tech/tk1077/technologies_tech_note09186a0080094c33.shtml


On Wed, Sep 2, 2009 at 3:39 AM, amit salunkhe <amitsalunkhe21 at gmail.com>wrote:

> Hi All
>          I found one article on Cisco as5350 gateway on SIpforum, hence i
> decided to post my reqiuirement on this forum. I want to configure Cisco
> AS5350 SIP-VOIP dial peer which can handle SIP redirect response 300 get
> from carrier gateway.
>
>  My current dial peer config as follows
>
> dial-peer voice 5 voip
> destination-pattern .T
> session protocol sipv2
> session target ipv4:x.x.x.x
> codec transparent
> no vad
>
> what parameters i need add in this which can handle SIP redirect response
> get from carrier g/w & then reroute the call to new IP provided in carrier
> redirect response contcat header.
> Is there any other settings require for this on AS5350. This AS5350 not
> acting as SIP-UA over here . Simply forwarding calls to carrier w.r.t
> dial-peer.
>
> Here is flow-
>                  VOIP users(Caller)------------------->SIP
> Proxy----------------------->AS5350
> g/w--------------------------------------->Carrier g/w-------->
>
> |<--------------SIP response 300 from carrier---|
>
> very few poeple usee AS5350 for carrier or VOIP service level, till i
> hope somebody from thsi from can help me.
>
> Thanks
>  Amit--
>
> _______________________________________________
> This is the SIP Forum discussion mailing list
> TO UNSUBSCRIBE, or edit your delivery options, please visit
> http://sipforum.org/mailman/listinfo/discussion
> Post to the list at discussion at sipforum.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20090902/5e0a44f1/attachment-0002.html>


More information about the discussion mailing list