From: Miles Scruggs <[EMAIL PROTECTED]>

   In this instance there is a PSTN gateway which has provided us with  
   multiple IPs to send calls to.  If their network is congested for that  
   call then they spit back a 503.  We then in turn try to send the call  
   down each on of their IPs and of course keep getting a 503 for each.   
   At first I was a little frustrated that a provider would send a server  
   specific error for a network wide issue. After a laymans reading of  
   the RFC it doesn't appear they have any other option.

   Could someone enlighten me a little in this situation?

IMHO, you should assign one DNS name to all the IPs via multiple A
records for that name.  (I'm assuming that all the IPs go to one
gateway device, or to a cluster of gateway devices that share any
needed SIP state information.)  Then your SIP element should be
directed to send the SIP request to that DNS name.  By RFC 3263, your
SIP element will try all of the IPs if necessary, but an answer from
one IP will prevent attempts to send the request to the other IPs.

That is, the rules for forking a request to multiple destinations are
different from the 3263 rules for sending a request to multiple IPs.

Dale
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors

Reply via email to