1 / 7

Intradomain gateway discovery requirements

Intradomain gateway discovery requirements. Henning Schulzrinne Columbia University. Organizational assumptions. Possibly “mutual aid” e.g., gateway calls to local calling area without billing Loosely affiliated, with different administrators different university campuses

margrett
Download Presentation

Intradomain gateway discovery requirements

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Intradomain gateway discovery requirements Henning Schulzrinne Columbia University

  2. Organizational assumptions • Possibly “mutual aid” • e.g., gateway calls to local calling area without billing • Loosely affiliated, with different administrators • different university campuses • different branches of enterprise 52st IETF

  3. G G G G P P P P Example 212 415 Columbia U. ? UCB 52st IETF

  4. Dynamic configuration • New gateways or gateway capacity capacity changes • For university networks (e.g., I2), potentially several hundred participants • Policy changes • new area codes adds additional calling areas • policy changes (time of day, …) 52st IETF

  5. Coordination • May have loose central administrator • avoid manual updates and configuration • reflect changes rapidly (minutes) 52st IETF

  6. Status updates • Want to have reasonably accurate picture • But occasional failure + retry acceptable • SIP INVITE fails, proxy retries • also, may allow grace period (change policy, allow calls for old policy for an hour) • Charging not an issue • may use a “brownie point” system 52st IETF

  7. Additional considerations • Multicast may be available • Not competitors – if anything, GWs are happy not to get a call… 52st IETF

More Related